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
When guided access is enabled on iPad, e.g., for a kiosk application, it would be great if the in-app update mechanism is disabled since it won't work. The system will kill the app to install the update but as soon as the app is killed, guided access relaunches it, and it will present the “Update available” alert again.
I know I could disable the update check for that specific use case but the developer has to think about that, and that particular situation might not arise during development. Would be great if that is handled on the SDK level. There is official API to check if guided access is enabled.
Thanks 🙏
The text was updated successfully, but these errors were encountered:
PR is opened up @florianbuerger. Should get merged fairly soon, but will be a little while until we ship a new SDK with all the work going on right now.
HI @florianbuerger, going to move this to next month. Before merging the PR change to disable in-app updates in guided access mode we'd like to investigate a possible fix for it.
@florianbuerger - this has been merged into our master branch and should be shipped in the next SDK release early May. Thanks for submitting the issue!
Hi AppCenter team,
When guided access is enabled on iPad, e.g., for a kiosk application, it would be great if the in-app update mechanism is disabled since it won't work. The system will kill the app to install the update but as soon as the app is killed, guided access relaunches it, and it will present the “Update available” alert again.
I know I could disable the update check for that specific use case but the developer has to think about that, and that particular situation might not arise during development. Would be great if that is handled on the SDK level. There is official API to check if guided access is enabled.
Thanks 🙏
The text was updated successfully, but these errors were encountered: