-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Question on permissions #86
Comments
As far as I remember it was a workaround for restriction on launching the app from background 🤔 I'd probably achieve this in a different way now, but I don't have the motivation to rewrite everything just for that while it works like it is.
I'll make a PR |
Thanks!
So what shall I put as "justification" to the "green list" then? To see what I mean, here's the "green list" from Capod: android.permission.ACCESS_COARSE_LOCATION: needed to access BLE broadcasts in earlier Android versions
android.permission.ACCESS_FINE_LOCATION: needed to access BLE broadcasts in earlier Android versions
android.permission.ACCESS_BACKGROUND_LOCATION: needed to scan for BLE while the app is in background
android.permission.BLUETOOTH_SCAN: needed to access BLE broadcasts in newer Android versions
android.permission.SYSTEM_ALERT_WINDOW: needed to display the pop-up window with battery infos when the airpods case is opened |
|
Thanks! Updated and deployed. |
The scanners at IzzyOnDroid just reported:
Could you please clarify what
SYSTEM_ALERT_WINDOW
is needed for? As forDEPENDENCY_INFO_BLOCK
, that can easily be avoided with a minor change to yourbuild.gradle
:For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.
Thanks in advance!
The text was updated successfully, but these errors were encountered: