What iOS background permissions are required by the Gimbal SDK and what are best practices when submitting an app for approval to iTunes?

If using Gimbal Proximity, you only need to enable the “Uses Bluetooth LE accessories” background mode (this can be found in Xcode by clicking on the root of your project - > Capabilities tab -> Background modes). Note, this will update the application’s plist accordingly.

If using Gimbal Geofencing, no background modes are required (e.g. “Location updates” is not required).

If your app uses Gimbal Proximity via a version 1.x Gimbal SDK, when submitting it for review, include in your explanation that your app uses Bluetooth LE beacons that transmit both iBeacon technology packets as well as other, non-iBeacon technology, Bluetooth LE packets. Therefore, you require the startMonitoringForRegion and startRangingBeaconsInRegion services as well as the “bluetooth-central” background mode to detect the non-iBeacon technology Bluetooth LE packets.

If your app uses Gimbal Proximity via a version 2.x Gimbal SDK, when submitting it for review, include in your explanation that your app uses Bluetooth LE beacons that transmit both iBeacon technology packets as well as other, non-iBeacon technology, Bluetooth LE packets. Therefore, you require the startMonitoringForRegion service as well as the “bluetooth-central” background mode to detect the non-iBeacon technology Bluetooth LE packets.

It is also helpful to record a video demonstration to show how your app uses the beacons to make it clear to the Apple reviewer. In a few cases, Apple reviewers have also requested the developer to then mail a beacon to test the app with. Therefore, just in case, please be sure have a spare Gimbal beacon setup in your Gimbal Manager account that can trigger the app use case ready to ship in order to quickly complete the approval.