Open Ventis opened 7 years ago
Hey,
I understand that the issue is that, when you are inside a beacon, and stop monitoring, that the timeout (to trigger the exit callback) encounters a nullpointer exception as you stopped the service.
I'll have to fix the behavior. When you stop, the exit timeouts should be removed.
This is part of our next release, https://github.com/inthepocket/ibeacon-scanner-android/projects/1, however the problem is that I don't now exactly when this release is going to happen :/.
Yes, that is correct. Unfortunately it seems to trigger every time on the Android Emulator, causing a crash. Even though we don't start monitoring if EmulatorUtils.isEmulator()
is true.
hello , I will product special I beacon, I need to virtual I beacon connect with android app . please help me !
Two years later...
The problem is a simple null pointer exception that only occurs on emulators or more recent Android versions (9+ I suppose) when bluetooth is turned off.
BluetoothAdapter.getDefaultAdapter();
I will fix this bug (pr coming soon).
Hi,
I'm using your library in a react-native project where on user logout we want to stop the ibeaconscanner. We do this by sending a broadcast which we catch in a service called BeaconService:
However, not long after logout this crashes the app with the follow error:
This is how we init the iBeaconScanner in the service:
After a logout the timedOutHandler seems to be called and this triggers a null pointer exception because bluetoothAdapter is null.