iPhone Client issue: Name could be too long

[BrentMason]

Having problems with iPhone client v: 3.22024.16.  When starting the app we're reading data from SharePoint, then writing to the device storage.  I am getting a "There was a problem saving your data. Name could be too long."  I think it is bug in the iPhone Power App mobile client as we DON'T have the issue when running from the desktop (web) or Android.  There are several other intermittent errors that are occurring too, these are also limited to the iPhone.

Previous versions of our Power App are running without issue.  SharePoint is the data source.

Any advice on how to trap the "Name could be too long" as Errors() and other functions don't seem to play well with SaveData based on my experience?

[RandyHayes]

@BrentMason 

The error you are seeing is related to the use of SaveData in your app.

It is a bug!!  Not your fault!

But, it should have been resolved in the more recent release of the PowerApps authoring version.  What version is your app published in?  I would check that and change to a more recent release.

I hope this is helpful for you.

[BrentMason]

Hi @Randy, thanks for the quick reply.  Current authoring version is: 3.22022.31.  I can retry publishing, it was last published 5 calendar days ago.

[BrentMason]

@RandyHayes, just republished (3.22022.31) and updated iPhone client to 3.22031.24.  Same result.  Doesn't appear to be fixed 😞

[RandyHayes · Accepted solution]

@BrentMason 

Try 3.22031.27 - it is supposedly addressed in that release.

[BrentMason]

@RandyHayes - regarding the 3.22031.27.  Is this the authoring # I'm seeing in the editor?  Or the About -> Version on the iPhone?  I just updated the iPhone app to 3.22031.24 and authoring version is 3.22022.31 with the same poor results.  I'll be patient until something new is released.

[RandyHayes]

@BrentMason 

No, the authoring version is what you see in the app designer under the settings/support.  You'll want to change it there and publish to see if it helps.

[BrentMason]

Thank you @RandyHayes v3.22031.27 did the trick.  Until today I didn't know that editing the version was even a thing 🙂

[BrentMason]

Thank you @RandyHayes v3.22031.27 did the trick.  Until today I didn't know that editing the version was even a thing 🙂

[RandyHayes]

@BrentMason 

Excellent!  Yes, keep in mind though, whenever you return to the editing environment, the editor will revert back to the recommended version.  So, if that version happens to be the one that doesn't work, you will have to change the authoring version each time before publishing.

Kind of wish they would do a little better on the QA!!