Android manifest api key parsing issue

[Cassio90]

Describe the bug

[DEBUG] Reading data from AndroidManifest.xml
[DEBUG] Using https://api-eu.mixpanel.com/engage?ip=1 as API key from AndroidManifest.xml
[DEBUG] Using app.staging as application ID from AndroidManifest.xml
[DEBUG] Using  as build UUID from AndroidManifest.xml
[DEBUG] Using 3603 as version code from AndroidManifest.xml
[DEBUG] Using 3.0-staging as version name from AndroidManifest.xml
[DEBUG] (dryrun) Upload payload:
[DEBUG] {
    "apiKey": "https://api-eu.mixpanel.com/engage?ip=1",
    "appId": "app.staging",
    "versionCode": "3603",
    "versionName": "3.0-staging"
}

Here is the relevant excerpt from the manifest:

        <meta-data
            android:name="com.google.firebase.messaging.default_notification_icon"
            android:resource="@drawable/ic_notification_small" />
        <meta-data
            android:name="com.google.firebase.messaging.default_notification_color"
            android:resource="@color/apricot_500" />
        <meta-data
            android:name="firebase_analytics_collection_deactivated"
            android:value="true" />
        <meta-data
            android:name="firebase_analytics_collection_enabled"
            android:value="false" />
        <meta-data
            android:name="firebase_crashlytics_collection_deactivated"
            android:value="true" />
        <meta-data
            android:name="firebase_crashlytics_collection_enabled"
            android:value="false" />
        <meta-data
            android:name="firebase_performance_collection_deactivated"
            android:value="true" />
        <meta-data
            android:name="firebase_performance_collection_enabled"
            android:value="false" />
        <meta-data
            android:name="com.bugsnag.android.API_KEY"
            android:value="your-api-key" />
        <meta-data
            android:name="com.mixpanel.android.MPConfig.EventsEndpoint"
            android:value="https://api-eu.mixpanel.com/track?ip=1" />
        <meta-data
            android:name="com.mixpanel.android.MPConfig.PeopleEndpoint"
            android:value="https://api-eu.mixpanel.com/engage?ip=1" />
        <meta-data
            android:name="com.mixpanel.android.MPConfig.GroupsEndpoint"
            android:value="https://api-eu.mixpanel.com/groups" />
        <meta-data
            android:name="com.mixpanel.android.MPConfig.DecideEndpoint"
            android:value="https://api-eu.mixpanel.com/decide" />

Replacing the meta data section in the test manifest reproduces the issue for me.

The CLI picks up a different manifest meta data value than the expected one for the key.

Steps

• ./gradlew assembleStagingRelease
• bugsnag-cli upload android-proguard --dry-run

Environment

• bugsnag-cli version:3.9.0
• Platform: MacOS 26.3.1

[hannah-smartbear]

Hi @Cassio90,

Thanks for raising this. We’ve passed this on to our engineers, and we will be sure to let you know here of any updates.
In the meantime, if you're using the BugSnag Gradle Plugin, you can specify the correct API key as a configuration option by adding the following to your gradle script:

bugsnag {
    apiKey = "your-api-key-here"
}