Issues with BLE Application Development and Google Play Compliance

[iprimo]

Hi,

I am working on a BLE-based application and found it much easier to bypass the initial configuration requirements using the example provided in your repository. Thank you for making this process more convenient!

However, I encountered a couple of issues that I’d like to highlight:

Issue #1:
When trying to upload the code (not directly your example code but a customized version based on it), I encountered the following errors in Google Play (screenshot attached):

`
Duplicate declarations of element 'android.permission.ACCESS_COARSE_LOCATION' in manifest with different maxSdkVersions.
Duplicate declarations of element 'android.permission.ACCESS_FINE_LOCATION' in manifest with different maxSdkVersions.

`

To temporarily resolve this, I commented out the addLocationPermissionToManifest function in the withBLEAndroidManifest.js file. While this allowed the app to work, it limits the range of targeted devices, which is not ideal for the final solution.

Issue #2:
New app uploads to Google Play require targeting the latest SDK/API. To meet these requirements, I had to execute the following commands and make changes to the app.json file:

npx expo install expo-build-properties

"plugins": [ [ "expo-build-properties", { "android": { "compileSdkVersion": 34, "targetSdkVersion": 34, "buildToolsVersion": "34.0.0" }, "ios": { "deploymentTarget": "13.4" } } ] ],

These changes ensured compliance with Google Play's policies but required additional setup steps.

I’d greatly appreciate your efforts in addressing the issues mentioned above.

e.

[lucaswitch]

I see a lot of people struggling with the permissions but we know it's not a library issue since users find it hard to deal with using an
other libraries/languages.
I wonder if would be interesting to add those runtime permissions safety checks on dev mode?
Something just like the browsers do when server does not emit the cross origin http headers.

For example:

• User tries to scan for the first time the library. -
• The library checks if the scan manifest is right and log a warning if not set.

[iprimo]

Certainly, it does not seem to be library problem.
It would be excellent if you could add such runtime check and\or suggest some corrections (if needed).

[iprimo]

Hi @lucaswitch ,

Regarding the issues above, I am trying to upgrade the example components to the latest versions and everything fails.

I am wondering if the example in the source code could be upgraded to match\compatible to the latest version of expo\react-native.

Thanks