Latest authoring version(s) causing existing SaveData/LoadData functionlity to break. 3.24023.11 / 3.24024.7

[ENVPA]

The recent authoring versions 3.24023.11 / 3.24024.7 are causing an existing solution for our client to break. The app in question is used exclusively on devices and relies heavily on SaveData and LoadData operations to cache information when internet connectivity cannot be guaranteed.

I have set up a very basic app to demonstrate the issue... please note that the behaviour differs depending on whether you are using the app in a browser or a device (with no connectivity).

On device:

• On the OnSelect of a button, a collection named MyItems is created
• On the OnSelect of a further button, the MyItems collection is stored using SaveData 
  • The bug is evident at this point when an error notification is received stating "There was a problem saving your data. Name could be too long."
  • 
• Any subsequent attempt to LoadData using the stored name will fail i.e no data will be loaded into MyItems. 
• Any further attempts to SaveData will fail, displaying the same error message as originally received.

In browser (note, in order to achieve this the Preview feature Enable SaveData, LoadData, ClearData on web player must be activated, however this setting has no impact on the device experience) :

• On the OnSelect of a button, a collection named MyItems is created
• On the OnSelect of a further button, the MyItems collection is stored using SaveData 
  • The bug is initially evident here when an error notification is received stating "There was a problem saving your data. Name could be too long."
  • 
• LoadData then appears to work, successfully loading into MyItems. 
• Any subsequent invocations of SaveData and LoadData complete with no error.

I just want to reiterate that although the preview feature is used here to illustrate the difference between the experience on a device and in-browser we do not have the preview feature turned on in our app and do not need this feature.

Hope this reaches the right people and makes sense, 

Kind regards

Dan

[Will2]

Having exactly this issue with a mobile app that had been working perfectly until I published a version using 3.24023.11, at which point any savedata event on the device fails with the error described above. This is completely breaking the offline capabilities of the app. I can also make a very simple app from scratch to demonstrate the issue - any savedata event fails.

[bgrgic1 · Accepted solution]

I can confirm the same thing happening in our app. Updateing the app to authoring version 3.24024.10 seems to resolved the problem

[danielreid]

Hi @bgrgic1 thanks for the heads up - 3.24024.10 also seems to have fixed the issues with my basic app used to demonstrate the issue, so we will check our client's app now. Thanks!

[Will2]

How are people publishing using 3.24024.10? According to my IT department it isn't being deployed until 18th March?

[bgrgic1]

You can change the authoring version under settings of the app under Support

And then republish the app.

[Will2]

Amazing! Thank you!