I keep getting this email from Apple after deploying my app via Bubble. Does anyone know how to fix it?
Please correct the following issues and upload a new binary to App Store Connect.
ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “UserApp.app” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources.
Evidently you have enabled either the use of the camera, geolocation or something that requires the explicit consent of the user in order to work.
Apple is simply asking you to describe why the app needs to access that something, such as the gallery or the camera. You must fill in the appropriate fields present in the mobile settings of the bubble app. I recommend a thorough reading of the documentation, everything is explained very well.
I got this error too even though I don’t use the camera or have that setting enabled. You need to go into your bubble mobile app settings and switch camera and mic permission on, then go into app language and change the [insert reason] on the camera and mic access language to some kind of general reason. It doesn’t matter that you don’t use it, there must be something in the bubble build file that references it. There’s no downside to switching it to ‘on’. That should sort the issue.
Same issue here. The support team replied to me today: “Thank you for patiently waiting, we just received an update from our internal team. We’ve confirmed that the issue you reported is part of a known problem currently being tracked under a master task. We’ve updated your status to “impacted user,” and our team is actively working toward a resolution. We’ll make sure to notify you as soon as there’s an update. We appreciate your understanding."
That’s a good workaround for getting past the build issue. Just one thing to keep in mind: any permissions you request will show up on the App Store page. If the app doesn’t actually use camera or mic, users might hesitate to download. Could be worth fixing the root cause before release to real users.
