LinkedIn
Twitter
1 ACCEPTED SOLUTION
I ended up resolving the issue and it is a very tedious one. I am also able to recreate it which I imagine will help the dev team fix it:
It appears that the issue was stemming from the ios app permission settings, particularly this one:
When the update was first downloaded, appsheet asked for all necessary permissions. Given what is shown in the above screenshot you would think that everything related to the device camera and photos would be functioning normally. This was not the case as described in my post. In addition to what I already described, we also saw more and more app crashes right after taking a photo in the app.
Here is how we solved and it has worked for all users we have helped so far:
1. Open Whitelabel app
2. press home/exit app, leave running in background
3. open iOS settings and navigate to the apps settings
4. Select Photos and change permissions to "none"
5. Turn off "save photos to camera roll" (circled setting in above screenshot)
6. Navigate back to whitelabel app. since security permissions changed it will auto refresh (at least this is the case with ours)
7. Go back to settings and set Photo Permissions to "All Photos" and turn back on "save photos to camera roll"
8. Go back to your app and let it refresh again
9. In app camera functionality should be working
To recreate the bug:
1. Open whitelabel app
2. press home, leave app running in background
3. go to your app settings
4. turn off "Save photos to camera roll"
5. go back to your app and refresh manually
6. go back to settings and toggle "save photos to camera roll back on"
7. Go back to your app and refresh manually
8. now (for us), even though all permissions are granted, the in app camera will not work again. can be fixed the same way described above each time. I've recreated and fixed it many times to confirm the process so we can tell users.
my guess is that the appsheet "save photos to camera roll" and iOS photo gallery permissions are conflicting with eachother somehow and thats why turning them both on and off in unison fixes it. Leaves me wondering if the appsheet editor having the option "save photos to camera roll" in 2 separate places (security options and view options) is part of the problem.
tagging some staff so they are aware. let me know any thoughts on this.
@Aleksi
@devingu
I ended up resolving the issue and it is a very tedious one. I am also able to recreate it which I imagine will help the dev team fix it:
It appears that the issue was stemming from the ios app permission settings, particularly this one:
When the update was first downloaded, appsheet asked for all necessary permissions. Given what is shown in the above screenshot you would think that everything related to the device camera and photos would be functioning normally. This was not the case as described in my post. In addition to what I already described, we also saw more and more app crashes right after taking a photo in the app.
Here is how we solved and it has worked for all users we have helped so far:
1. Open Whitelabel app
2. press home/exit app, leave running in background
3. open iOS settings and navigate to the apps settings
4. Select Photos and change permissions to "none"
5. Turn off "save photos to camera roll" (circled setting in above screenshot)
6. Navigate back to whitelabel app. since security permissions changed it will auto refresh (at least this is the case with ours)
7. Go back to settings and set Photo Permissions to "All Photos" and turn back on "save photos to camera roll"
8. Go back to your app and let it refresh again
9. In app camera functionality should be working
To recreate the bug:
1. Open whitelabel app
2. press home, leave app running in background
3. go to your app settings
4. turn off "Save photos to camera roll"
5. go back to your app and refresh manually
6. go back to settings and toggle "save photos to camera roll back on"
7. Go back to your app and refresh manually
8. now (for us), even though all permissions are granted, the in app camera will not work again. can be fixed the same way described above each time. I've recreated and fixed it many times to confirm the process so we can tell users.
my guess is that the appsheet "save photos to camera roll" and iOS photo gallery permissions are conflicting with eachother somehow and thats why turning them both on and off in unison fixes it. Leaves me wondering if the appsheet editor having the option "save photos to camera roll" in 2 separate places (security options and view options) is part of the problem.
tagging some staff so they are aware. let me know any thoughts on this.
@Aleksi
@devingu
