iOS6 Guided Access Malfunctioning... Unity3D issue or iOS itself?

We have created iOS iPad applications for 2 separate clients, and both are experiencing the same issue when running the application in Guided Access.

These applications are Augmented Reality experiences utilizing the following utilities:

  • Built in Unity3D 4.x
  • Using Vuforia 2.6.7 Plugin

The iPads are running 6.1 as a version – at this point, they do not have the capabilities to upgrade to iOS 7.

Each application is housed in a case, where the visitors do not have access to any of the hardware buttons and the iPads are running Guided Access.

After continuous running (the applications are on exhibit at museums), the Guided Access malfunctions, and it results in going back to the icon screen - yet the passcode prompt is visible.

Visitors cannot cancel out of the prompt – everytime they hit cancel the prompt comes up again. If the passcode is entered, the visitor now finds themselves on the icon screen and are able to access whatever they would like on the iPad.

In some instances, the only way to get out of the passcode screen is to restart the iPad.

It’s almost like the application crashes, but instead of Guided Access restarting it, the iPad sits on the icon screen, and the bug presents itself.

I’ve already submitted a bug report with Apple, as this is most definitely a bug that deals with the iOS6 Guided Access function.

I’m also posting here, as the actual application code itself is coming directly from Unity3D, and I’m not sure if anyone else has ever encountered such an issue - I’m sure we are in the minority.

Any thoughts or suggestions are most appreciated.

Can you get the crash logs from those devices?

Hi There, did you ever find out the problem with this specific Guided access crashing and not relaunching the app (getting stuck at icon screen with guided access code prompt). I’m experiencing same issue. Not that I’m not a Unity user currently, but experience exact same problem you are reporting. Thanks.

We actually dealt directly with Apple on this issue, and they had no real suggestions or fixes except recommending an upgrade to iOS 7.

Once we upgraded, the issue resolved itself.

Is your device running iOS6 or iOS7?

Yes, I’ve been using iOS6.1. I take it you don’t see the issue occuring anymore on iOS7, great.

That is correct. We had this issue happening to us with two different clients, and each scenario was resolved by an iOS7 update.