André Kovac

> Go to `Build Settings` > Find `Preprocessor Macros` > To `Debug` add new value: > `FB_SONARKIT_ENABLED=1` This should be added to https://react-native-community.github.io/upgrade-helper/

This lib is not well tested with Eddystone beacons. So pull-requests for Eddystone beacons are very welcome in case you find a fix.

Hi! There are not current plans for this. Feel free to give it a go. PRs are very welcome!

It's not on the agenda right now but will be considered in case there's a growing number of people requesting it.

Thanks @hl2000 for sharing this! Would you mind updating the Android docs and the Minimal Example to reflect this new requirement for Android 10+?

Such a virtual beacon would be a great thing. It would also be very useful for unit tests so that the beacon response could be mocked. However I didn't think...

@nzhenry I asked the creator of the fork which @yhanssens linked for more information about his additions (see [this question in his commit](https://github.com/Driversnote-Dev/react-native-kontaktio/commit/8fd546af74be2b1de9f80cc0bd6434c6991ffe9e#r83090667) We are not using react-native-kontaktio with Expo...

Is this still the case?

Did you use the code from the minimal example in the README?: https://github.com/Driversnote-Dev/react-native-kontaktio#minimal-example The example app is unfortunately outdated.

Just tested. In the current version [v3.1.0](https://github.com/Driversnote-Dev/react-native-kontaktio/releases/tag/v3.1.0) beacon scanning works on Android. Closing this issue.