You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UPDATE: so we submitted a version through EAS Build, and the TestFlight version of the app showed the proper permission string from our config file "NSCameraUsageDescription: 'The app uses the camera to allow you to take photos to share within the app.',"
so that's unexpected, but great, not sure why development builds don't show it
Thanks all, I'll close this …
EDIT: the below string might actually be coming from expo, i'm not 100% sure even with testing both libraries, but if anyone with more experience knows for certain, it would be sincerely appreciated 🙌
Hi all,
Firstly, THANK YOU for an awesome crop picker. It rules. We're going to be using it in Photodare for iOS (not android).
When fetching permissions the user sees a message like the attached:
I found the exact string from someone else's discussion about Expo (which we are also using):
`const CameraDescription =
cameraText || 'Allow $(PRODUCT_NAME) to access your camera'`
we recently got rejected by Apple because of language like this, apparently to them it didn't offer enough of an 'informed consent" that gave the user the option, and we were told to change it to language that was less of a directive, e.g. "ALLOW THIS" and more "TO ENABLE YOU TO DO X, THE APP MUST HAVE ACCESS TO Y" … splitting hairs but nevertheless I'd like to avoid another long back and forth with a reviewer.
Is there any way I can pass along an option that customizes this string? I'm going to try submitting anyways, and we might get lucky, but incase we get rejected I wanted to see if there is any way to expose that.
We have it set in Expo like this, but it gets overridden by the message above "ios": { "infoPlist": { NSCameraUsageDescription: 'The app uses the camera to allow you to take photos to share within the app.', }
Again, thanks to everyone contributing to this library, it's going to make PhotoDare better on iOS and as a tiny 2 person startup we're deeply grateful for it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
UPDATE: so we submitted a version through EAS Build, and the TestFlight version of the app showed the proper permission string from our config file "NSCameraUsageDescription: 'The app uses the camera to allow you to take photos to share within the app.',"
so that's unexpected, but great, not sure why development builds don't show it
Thanks all, I'll close this …
EDIT: the below string might actually be coming from expo, i'm not 100% sure even with testing both libraries, but if anyone with more experience knows for certain, it would be sincerely appreciated 🙌
Hi all,
Firstly, THANK YOU for an awesome crop picker. It rules. We're going to be using it in Photodare
for iOS (not android).
When fetching permissions the user sees a message like the attached:
I found the exact string from someone else's discussion about Expo (which we are also using):
we recently got rejected by Apple because of language like this, apparently to them it didn't offer enough of an 'informed consent" that gave the user the option, and we were told to change it to language that was less of a directive, e.g. "ALLOW THIS" and more "TO ENABLE YOU TO DO X, THE APP MUST HAVE ACCESS TO Y" … splitting hairs but nevertheless I'd like to avoid another long back and forth with a reviewer.
Is there any way I can pass along an option that customizes this string? I'm going to try submitting anyways, and we might get lucky, but incase we get rejected I wanted to see if there is any way to expose that.
We have it set in Expo like this, but it gets overridden by the message above
"ios": { "infoPlist": { NSCameraUsageDescription: 'The app uses the camera to allow you to take photos to share within the app.', }
Again, thanks to everyone contributing to this library, it's going to make PhotoDare better on iOS and as a tiny 2 person startup we're deeply grateful for it.
Beta Was this translation helpful? Give feedback.
All reactions