[1.1.9] [Android] Doesn't work anymore

[antoinerousseau]

While this new release seems to work on iOS, it does not on Android: bridgefy.start() successfully resolves without errors, but BridgefyEvents.BRIDGEFY_DID_START never happens.

React-Native 0.81.5
Expo 54.0.33
Device: Google Pixel 10 Pro
Permissions seem fine (they worked with bridgefy-react-native 1.1.8)

[julian-bridgefy]

@antoinerousseau Thanks for the detailed report on the Android-specific issue.

We've detected this as an Android service startup problem tied to missing permissions and incomplete manifest declarations. It prevents the full service initialization despite the promise resolving.
A comprehensive step-by-step integration guide is being prepared, covering all required Android permissions (e.g., Bluetooth, location), manifest entries, and service declarations.

The fix and full documentation will be included in the next release. We'll notify you when it's available, along with tested code samples.

Appreciate the cross-platform testing—this helps us deliver a robust SDK!

[antoinerousseau]

I was able to resolve this by adding that new <service> tag in AndroidManifest.xml.
This should be documented!!

With Expo, I added this to my AndroidManifest plugin:

manifest["application"]![0]["service"] = [
  {
    $: {
      "android:name":
        "me.bridgefy.plugin.react_native.service.BridgefyService",
      "android:enabled": "true",
      "android:exported": "false",
      "android:foregroundServiceType": "connectedDevice",
    },
  },
];

[antoinerousseau]

Also:

• Do I also need to add <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
• Why add <uses-permission android:name="android.permission.FOREGROUND_SERVICE_DATA_SYNC" /> instead of FOREGROUND_SERVICE_CONNECTED_DEVICE since the android:foregroundServiceType is "connectedDevice"