Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working on Android 10+ (permission issue?) #162

Open
phatpaul opened this issue Dec 23, 2020 · 1 comment
Open

Not working on Android 10+ (permission issue?) #162

phatpaul opened this issue Dec 23, 2020 · 1 comment

Comments

@phatpaul
Copy link

I know this project is not active, so this probably won't be fixed. But it's worth pointing out that this plugin is not working for me anymore when compiled for Android SDK 29. There are no runtime errors in console, and no BLE devices are discovered.

A quick search brings up new permission requirements for Android 10+:

android.permission.ACCESS_FINE_LOCATION,
android.permission.ACCESS_COARSE_LOCATION,
android.permission.ACCESS_BACKGROUND_LOCATION.

https://stackoverflow.com/questions/58428763/android-10-not-working-with-ble-bluetooth-scanning

I tried adding those to the AndroidManifest.xml with no luck.

It's interesting that older versions of my App which were compiled previously with older SDK continues to work and discover BLE devices on Android 10+. And seems google won't let me submit a newly build app to the app store unless SDK >= 29.

WTF does google require FINE and BACKGROUND location just to use BLE? I'm not trying to spy on users of my app and I don't use location at all. IMO by requiring these in every BLE app, they are desensitizing people to the requirement of location permission. So when a spyware app asks for LOCATION permission it just seems normal. Anyway... Rant over.

Has anyone got this working on Android 10+?

@jb-72
Copy link

jb-72 commented Jan 8, 2021

Yes, @phatpaul it does work on Android 10+. Had the same issue months ago.

It seems it's fine for new installers of the app but is an issue is for users updating (which I assume you are too). The only solution we have found is for users to turn off their location permissions and then turn them straight back on again which seems to make Android set the correct settings internally. Changing the android.permissions made no difference, seems it is a bug between Android SDK versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants