refreshAfterSelection no longer working on iPhone

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

After the latest iphone update I’ve found that refreshAfterSelection: true no longer work on Dynamic pages in the smart apps. It used to work before the update.

Anyone else seeing this issue?

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

Okay to answer my own question - I spoke with ST Support and they escalated to Dev.
Dev confirmed that it’s a known bug. Don’t have an ETA from them yet, pretty serious and basic bug IMHO. Wonder how it got past QA!

@April is there any way to get a list of known bugs for the platform and apps? Some Sticky thread? If not can you please pass that feedback on internally to the leadership team.

[April (April Wong)]

Hey RBoy,

I’m currently actively looking at a way to do some known bugs list, however - I do not have the capacity to do a manual update, therefore, we are reviewing our best options for what we need. It’s been heard, it’s been requested - now I just need to pull the trigger…

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

If I may suggest, there could be a running sticky thread, and your dev team could do a webservices integration with the sticky to post the release notes/known issues straight from the release build / source control.

[rayzurbock (Brian S. Lowrance)]

Thanks for the heads up. I just noticed this myself and searched the community to see if anyone else was seeing it. I hope it is fixed soon, kind of breaks a few things.

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

Well here’s the kicker, looks like ST made that refreshAfterSelection obsolete. Instead they put a new option submitOnChange. That works fine, although I can’t understand why they would change the name? If it was broken, fix it instead of changing the variable name.

@Jim any thoughts?

[MichaelS (Micheal)]

Here is the article on it…doesn’t seem that refereshAfterSelection is gone…it still works on the android…but so does this new ‘submitOnChange’

Docs Updates - submitOnChange and other changes

A couple relatively minor docs updates to share - We’ve added documentation around the submitOnChange attribute for input elements. This should be used in place of refreshOnSelection in your SmartApps. Read about it here and see a brief example here. We also made some tweaks to the Cloud and LAN-connected device guide. These are mainly minor organizational and and high-level changes and bugs fixes (we know there’s so much more to document in this particular area), but wanted to clean up some bugs found and add clarity during @unixbeast’s review of this documentation set. It includes some nice diagrams for understanding the LAN and Cloud-connected patterns (see here for cloud-connected devices, and here for LAN-connected devices). Since @unixbeast made these changes, it’s only fair tha…

[Jim (Jim Anderson)]

@RBoy

Well here’s the kicker, looks like ST made that refreshAfterSelection obsolete. Instead they put a new option submitOnChange. That works fine, although I can’t understand why they would change the name? If it was broken, fix it instead of changing the variable name.

There were some changes internally in how the pages are persisted using submitOnChange. The name change was done to better reflect what’s actually happening - the page will be submitted and re-rendered when the input is filled in.

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

I understand the logic @Jim, IMHO when that’s something that should be transparent to the devs. Reason I say so is that from a dev’s perspective both achieve the same functionality, so when I used refreshAfterSelected I expected it to do exactly what submitOnChange does, however changing it and deprecating refreshAfterSelection now makes me have to recode all my apps. Hence I expected the change to be transparent.

[Jim (Jim Anderson)]

@RBoy

I understand the logic @Jim, IMHO when that’s something that should be transparent to the devs. Reason I say so is that from a dev’s perspective both achieve the same functionality, so when I used refreshAfterSelected I expected it to do exactly what submitOnChange does, however changing it and deprecating refreshAfterSelection now makes me have to recode all my apps. Hence I expected the change to be transparent.

I agree and understand the frustration. We should have communicated that this change was coming, and given developers lead time and transparency here.