fix: Resolve fine location max sdk to app version's sdk - cp-7.72.0#28384
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
The only functional area this could theoretically affect is Ledger hardware wallet Bluetooth connectivity on Android (since react-native-ble-plx is used by LedgerBluetoothAdapter). SmokeAccounts covers hardware wallet account flows (QR-based hardware wallet accounts) and is the most relevant tag to validate that the Bluetooth permission declaration still works correctly after the manifest merge fix. No performance tests are needed as this is a manifest declaration change with no impact on rendering, data loading, or app performance. Performance Test Selection: |
Description
This PR attempts to resolve the Android APK upload error for Playstore where it complains about duplicate ACCESS_FINE_LOCATION declarations (WRT to the bluetooth library)
Changelog
CHANGELOG entry:
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Low risk manifest-only change; adjusts permission merge behavior to satisfy Play Store validation, with limited runtime impact beyond how the permission is declared/merged.
Overview
Resolves a Play Store upload failure caused by duplicate
ACCESS_FINE_LOCATIONdeclarations when merging manifests (e.g., fromreact-native-ble-plx).Updates
AndroidManifest.xmlto explicitlytools:replacetheandroid:maxSdkVersionattribute onACCESS_FINE_LOCATION, ensuring a single consistent declaration for Android < 12 Bluetooth-related location usage.Written by Cursor Bugbot for commit ecb94e2. This will update automatically on new commits. Configure here.