If bluetooth is turned off, sdk crashes

[FRizzonelli]

If you've Bluetooth turned off on your device, sdk crashes with following error it.bz.beacon.beaconsuedtirolsdk.exception.NoBluetoothException: Bluetooth is deactivated or not available on this device.

Probably we'd handle it with a modal to turn it on or something more useful to final user

[Piiit]

@FRizzonelli @raiffeisennet I am not sure if this is intended behavior, because consumers of the SDK should handle deactivated Bluetooth devices. Or is it a real bug, which crashes the SDK nevertheless? We should describe the init process of the SDK and point to possible error handling necessities.

[FRizzonelli]

I think we can fix it "quickly" by updating READ.ME example, because if you follow and run it with bluetooth turned off, app crashes.
Easy fix could be to update the example by mentioning that you need to check yourself that bluetooth is turned on/off and you need to wrap sdk method NearbyBeaconManager.getInstance().startScanning()
inside a try/catch block at least.
I think that would be nice to have some handling inside the sdk, maybe something like a method in the interface dispatched when bluetooth is off?

[FRizzonelli]

@Piiit Basically just add to READ.ME what you're doing in the example project. Also .startScanning() method isn't mentioned, maybe we can point it out?