KTKBeaconManager Monitoring Delegate methods are not triggering about kontakt-ios-sdk HOT 8 CLOSED

Can you be a little bit more specific at what is working when launched for the first time and what is not working after ?

@adrianz Can you have a look please :)

from kontakt-ios-sdk.

Hi @stoprocent

For the first time I have launched the app it is entering into "beaconScan()" method and alerting your permission okay approved it is entering into monitoring and then after ranging.

From the second time it is entering till switchcase kCLAuthorizationStatusAuthorizedAlways and printing NSLog(@"kCLAuthorizationStatusAuthorizedAlways");
there it stops.

It is not entering into

• (void)beaconManager:(KTKBeaconManager *)manager didStartMonitoringForRegion:(__kindof KTKBeaconRegion *)region {
  // Do something when monitoring for a particular
  // region is successfully initiated
  NSLog(@"didStartMonitoringForRegion %@",region);
  [manager startRangingBeaconsInRegion:region];
  }

or

• (void)beaconManager:(KTKBeaconManager *)manager monitoringDidFailForRegion:(__kindof KTKBeaconRegion *)region withError:(NSError *)error {
  NSLog(@"monitoringDidFailForRegion %@ %@error ",region,error);
  }

from kontakt-ios-sdk.

@Sea-Eagle Region monitoring is something that persists between app relaunches. Once you start monitoring one region and then ask your app to start monitoring the same region (e.g. during the second launch), iOS will ignore it, because it's already monitoring it, so you won't see notification about starting monitoring or monitoring failing to start.

To verify that, check you manager's monitoredRegions property as the first thing after instantiating the KTKBeaconManager – you will see that after a first launch of a new app, it will be empty, and then, on the second launch, it will already have your region.

from kontakt-ios-sdk.

@adrianz

yes in monitoredRegions I'm able to see my region. But now how i can able to range beacons now. I mean from second launch onwards how can i range beacons

from kontakt-ios-sdk.

@Sea-Eagle I don't believe this problem constitute an issue with our SDK. If you need help with learning how to build beacon-based iOS apps, please consider subscribing to our Premium Support plans.

Right now I can only suggest checking the documentation for KTKBeaconManager's method requestStateForRegion: and its corresponding delegate method beaconManager:didDetermineState:forRegion: – you can use it e.g. to determine at launch whether you are inside a region, and you can start ranging if indeed you are.

from kontakt-ios-sdk.

@adrianz It is the issue with SDK only I'm doing same with core location library its working perfectly.

But with Kontakt SDK only I'm facing this issue. I have tried requestStateForRegion as well it is not calling conManager:didDetermineState:forRegion:

from kontakt-ios-sdk.

@Sea-Eagle Sorry for a late reply. Our SDK verifies whether an app has already started monitoring a certain region, so it won't trigger the start monitoring event. We don't consider this a bug, but a feature.

As for the requestStateForRegion:, please check the latest version (1.3.3) of our SDK, that was released few days ago.

from kontakt-ios-sdk.

@adrianz I'm using the latest 1.3.3 SDK with cocoa-pods, requestStateForRegion: is not calling in updated one as well

from kontakt-ios-sdk.