On iOS 7.1 or newer, can Gimbal beacons wake up an app that was force closed (e.g. end-user went to the “app-switcher” and closed the app)?

Yes. Please note this is true regardless if the Gimbal hardware is configured with a Gimbal type or iBeacon type configuration. Also, please note the following requirements:

1)    The iOS device needs to be running iOS 7.1 or newer

2)    The Gimbal hardware should be configured with either:

                a.  Type Gimbal with “foreground or background” detection setting. Note, the default configuration for Series 10 beacons is “Series 10 Recommended” which is a “foreground-only” configuration. Therefore, you will need to assign and apply a new configuration to Series 10 beacons to test waking up an app.

              b.  Type iBeacon

3)      After you force close the app on the iOS device, the iOS device needs to depart from proximity of the beacon hardware. The next time the iOS device comes in proximity to the beacon the SDK will detect it and wake up the app in the background

            a. Note for Gimbal type you need to depart from proximity from all the Gimbal type beacons you are nearby. For iBeacon type you need to depart from proximity from all the iBeacon type beacons that have the same UUID you are nearby.

           b. If you are testing this functionality in your lab, it may be easiest to simulate a departure by removing the battery of the beacon. If you do so please note that when you re-insert a battery to a beacon it goes through a boot sequence for a few seconds prior to starting to transmit so you will experience a little longer delay in detecting the beacon than if you exited proximity and re-entered proximity

For more information regarding waking an app, please reference https://docs.gimbal.com/proximity_overview.html#wakeup_app

Please note on iOS, running in the background and seeing your app listed in the “app-switcher” are different states:

• Detecting the beacon and waking the app in the background does not mean you will see the app it in the “app-switcher” screen but it is running in the background
• Detecting the beacon, waking the app in the background and presenting a notification via the Communicate feature (see further below) does not mean you will see the app it in the “app-switcher” screen but it is running in the background
• Detecting the beacon, waking the app in the background, presenting a notification via the Communicate feature targeted to cause the app to open in the foreground (see further below) and the user clicking on the notification does mean you will see the app it in the “app-switcher” screen and your app will be  running in the foreground

* For iOS 8 and newer, please have additional settings as referred in FAQ :

https://support.gimbal.com/hc/en-us/articles/203536293-What-do-I-need-to-change-to-compile-an-app-with-the-Gimbal-SDK-for-iOS-8-