SAP Builders Discussions
Join the discussion -- ask questions and discuss how you and fellow SAP Builders are using SAP Build, SAP Build Apps, SAP Build Process Automation, and SAP Build Work Zone.
cancel
Showing results for 
Search instead for 
Did you mean: 

iOS Usage Strings not updating in build

kentotto
Discoverer
0 Kudos
250

I've tried updating multiple iOS Usage Strings in the Build Service Asset section, but most of the fields are not properly updated in the actual iOS build's Info.plist. I'm using Build Apps Community Edition.

To be sure this wasn't an isolated issue, I created a new app and changed all of the Usage Strings to "TEST UPDATE" in the Assets tab, and only 3 of the strings keys actually updated in the build (screenshots below).

I've figured out how to manually update this with help from this previous post, but is no one else having this issue? Apple required that I updated these strings for camera/image library usage before they'd approve the app.

image.png

image.png

3 REPLIES 3

srose99
Explorer
0 Kudos
174

It seems like this would be a really easy fix for the developers at SAP as it's just replacing text on the output file. Same as the notification for Android, it's using the  Appgyver icon instead of what was uploaded in the assets area.

Jaredn97
Explorer
0 Kudos
130

I'm facing the same issue. My app was rejected by the App Store due to the missing specific string description for photo permissions. I updated it and resubmitted to Apple, but it was rejected again with the claim that the string hadn't been changed. However, I did update it in the SAP Build settings.

It seems the change isn't reflected when the app is built. Any advice on how to resolve this?

I noticed some posts mention a temporary fix, but it could impact app performance, which I'd prefer to avoid. Could you assist with this? @MaiaraEllwanger ?

0 Kudos
105

It's a real pain but I was able to update the strings manually using the steps in this post. You can use TestFlight to verify the strings are accurately updated before you submit to Apple for review. I did not notice any performance issues.

My app was successfully approved after I did all this, but it really is something SAP should fix as it's clearly a bug.