iPad appears to have crashed - how can I find out what happened?

In iOS 12, Apple added a new behavior to Guided Access, which causes devices to sleep after 20 minutes of inactivity, regardless of Auto-Lock settings.  To prevent this, you need to be running iOS 12.1.1 or later, then open iOS Settings > General > Accessibility > Guided Access > Set Mirror Display Auto-Lock = On.

Other issues that might be causing the device to sleep or Auto-Lock unexpectedly: 

  • Low battery - if the device's battery is dead and it's not plugged in, it will shut down. Does your device have a regular power supply or is it without power at times?  We'd also recommend ruling out a problem with your power supply by testing with a different power supply, preferably one made by Apple. 
  • Overheating - if the enclosure you are using does not have adequate ventilation or if the iPad is in direct sunlight for an extended period, the device may overheat and shut down automatically to prevent further damage.
  • Magnetic key - iPads are designed to work with smart covers that use magnets to lock and unlock the device, which can make it possible for a kiosk enclosure or a visitor to sleep the device. This can be turned off under iOS Settings > Display & Brightness > Lock/Unlock and will only be shown if your device has been used with a smart cover at some point in the past.
  • Access to the Power Button - some kiosks have microchannels that allow you to access this button even if the device is in an enclosure. Pressing it will put the device to sleep regardless of iOS settings.

If the app appears to have crashed to the Home screen, you can send us the device’s crash logs to investigate further.

Syncing Crash Logs Off a Device

When an iOS device is synced to iTunes on a computer, crash logs are downloaded automatically. To do this:

  1. Connect the device to your computer with the standard white USB cable that came with your device.
  2. Open iTunes (if it has not already opened automatically).
  3. Click the ‘iPad’ or ‘iPhone’ button in the top right corner of the screen, which will take you to the summary page for the device. This page shows the device’s name beside the device picture at the top right of the screen.
  4. Once the device name has been noted, click the sync button in the bottom right to sync the crash logs.

The next step is finding these logs, which depends on the operating system your computer uses:


  1. Open the Finder application.
  2. Find the ‘Go to folder...’ option by either selecting the ‘Go’ menu at the top of the screen and then ‘Go to folder..’ or by using the keyboard shortcut (shift-command-G).
  3. Copy and paste ~/Library/Logs/CrashReporter/MobileDevice into the field and click the ‘Go’ button, which will open a Finder window with logs from every device that has been synced with your computer.
  4. Open the sub-folder whose name matches that of your iOS device.
  5. Find any crash logs  that have "Kiosk Pro", "JetsamEvents" or "LowBatteryLog" in the filename or just zip the entire folder and attach to an email to us at support@kioskproapp.com.


  1. Open a new Window Explorer panel either by clicking the ‘Start’ menu and then ‘Computer’ or by pressing the "Windows" key and the "e" key at the same time on your keyboard.
  2. Focus on the bar showing the current folder location at the top of the window by clicking in it.
  3. Copy and paste %HOMEPATH%\Application Data\Apple Computer\Logs\CrashReporter\MobileDevice into the field and hit the ‘Enter’ key on your keyboard.
  4. Open the sub-folder whose name matches that of your iOS device.
  5. Find any crash logs that have "Kiosk Pro", "JetsamEvents" or "LowBatteryLog" in the filename or just zip the entire folder and attach to an email to us at support@kioskproapp.com.

Video walkthrough

Actual crashing of the iOS operating system itself is relatively rare, but does occur - these logs are often shown as 'JetsamEvents'. 

We also often hear about situations where power to the device is interrupted and the battery drains to 0, effectively shutting off the iPad. Crashes caused by low battery are also logged in the same folder and are generally identifiable by a ‘LowBatteryLog’ filename.

Still stuck? How can we help? How can we help?