I’ve created a native module and following the documentation steps and everything outputs that there was a successful build.
I have tested my code against the hardware (this is a bluetooth integration) and get responses just fine when using the inspector.
When I build/upload/deploy the module into my actual app I am not getting any specific errors, but the communication between the Java and JS code via Forge seems to stop after certain BT-related calls are made. The issue seems to be around related to an attempt to begin scanning for Bluetooth devices. The manifests for both inspector and app APKs include the appropriate BT permissions.
I have looked at the Manifests of the 2 APKs that are being generated the only differences seem to be:
android:testOnly=“true” - on inspector only
2 new permissions (fine location and vibrate) - on my app only
names and authorities are different
Another variable in play is that we are using a 3rd party jar. As mentioned before, things are working properly in the inspector app, and I have verified that I can access classes from the jar in both inspector and my app. I can’t seem to find the difference in configuration/deployment that is making it so that the inspector app can do the BT communication, but my app cannot.
Any suggestions on where to look?