iOS 2.2.0 - Release Notes

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

So if I’m reading your code and comments correctly it’s an issue with atomicState in the preferences block not working as expected (i.e not saving the parameters). I would also urge you to look into this, the scope of state and atomicState in the preferences block is questionable. Anything you save to them in the preferences block isnt’ available in the initialize() and other methods of the SmartApp

State and atomicState broken in preferences of a SmartApp

@Jim @bflorian From an earlier thread I had posted here Bug in Parent Child Devices There is one thing still broken with state and atomicState. When some data is saved in state/atomicState in the preferences section, that data isn’t committed/saved to the DB so when initialize() runs that data is missing. That’s still a problem with parent child device like the blink camera or MyQ handlers. This is because it authenticates with the server and saves the authentication token in the state/atomicState when the user is configuring the SmartApp. When initialize() run that data is missing to it ends up authentication over again leaving the server with an “extra” login token which is never closed out (logged out). Anyways, the point being this is still an open bug and would be nice to have it …