iOS SDK 15.6.5,
Android SDK 15.5.1,
Hello Screen Dynamic States,
Bluedot Cordova plugin 4.0.1,
Bluedot Xamarin Android Wrapper 15.4.1,
Bluedot Xamarin iOS Wrapper 15.6.0,
Bluedot React Native wrapper 2.2.0,
An app may optionally disable (and later re-enable) Zone which it receives from Canvas.
setZone:disableByApplication: on the shared instance of BDLocationManager, a Zone can be disabled and re-enabled by an app. Note that this will not over-ride any excluding conditions entered via the Canvas web interface.
As an example; if you define a Zone in Canvas as active between 1 pm and 3 pm, calls to
setZone:disableByApplication: would have no apparent effect outside these times. During the Zone’s active period (e.g. at 2.30 pm), the Zone will be active unless disabled by
The enable and disable Zone methods return YES if a valid Zone Id has been provided.
Retrieve the shared instance of BDLocationManager to call the following methods:
- (void)setZone: (NSString *)zoneId disableByApplication:(BOOL)disable - (void)applicationContainsDisabledZone:(NSString *)zoneId completion:(void (^)(BOOL))completion;
To determine the Zones available to your app, you should implement the
BDPGeoTriggeringEventDelegate, which handles the callback:
// The zoneInfos parameter contains a set of all available Zone and their associated Ids, names, descriptions and Geofences. - (void)onZoneInfoUpdate: (NSSet<BDZoneInfo *> *)zoneInfos;
Zone Information will be updated after a successful Geo-triggering Start and/or after the next Rule Download :
Point SDK reference documentation can be accessed here.
Interaction with the Exit feature
Note that if a Zone has already been entered and is awaiting an exit event, then disabling the Zone at this point will not prevent the exit callback from occurring.
If it is important to suppress exit behaviours while a Zone is disabled by your application, we advise that you make use of the
applicationContainsDisabledZone:completion: method as part of your exit callback.