Expo client: undefined is not an object about react-native-beacons-manager

[utsav-dholakia]

I'm having the same issue, although my node and npm versions are different(I don't think it matters anyway with the issue). While debugging it seems that somehow the component "BeaconsAndroidModule" which should have been registered with NativeModules is not happening which is causing it to be undefined. It would be helpful if someone can help with the issue.

[ddresch]

Did the whole setup process with plain react-native init which is working normally.

Found this page about Expo and native code linking:
https://docs.expo.io/versions/v17.0.0/guides/expokit.html

What does using ExpoKit mean for a CRNA user?

If you want to add custom native code to your Expo app, you will need to use ExpoKit. With CRNA, you have two options: you can either eject to a normal React Native project, without any dependencies on Expo, or you can eject to use ExpoKit, which will allow you to continue using the Expo APIs. Read more about ejecting with CRNA here.

You probably need to follow this guide and use ExpoKit.

[MacKentoch]

I don't use Expo but this PR should be related.

This PR should be fixed first to avoid breaking existing (if not using Expo, library should work too).

[utsav-dholakia]

I tried and built the app using react-native and not using Expo and made it work. It seems Expo is not allowing me to do react-native link react-native-beacons-manager even after I detached the project from it where I should have been able to link the project to the app just like any other react-native init app.

[leocavalcante]

The problem here was that link didn't add new BeaconsAndroidPackage() to getPackages.

[MacKentoch]

@leocavalcante thank your helpful feedback.

Is that ok @haaslukas ?

[haaslukas]

@MacKentoch jep. thanks for the support