You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of that I think I was able to cover (please check if it's correct), but why is background location needed?
PS: If you wonder about the DEPENDENCY_INFO_BLOCK, that's easy to get rid of:
android {
dependenciesInfo {
// Disables dependency metadata when building APKs.
includeInApk =false// Disables dependency metadata when building Android App Bundles.
includeInBundle =false
}
}
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.
The text was updated successfully, but these errors were encountered:
Hello, thank you for filling this issue! ACCESS_BACKGROUND_LOCATION permission is completely optional (user is given a dialog on first app launch stating so while also including an explanation what this permission is used for), it's only used to display the SSID, BSSID and Network ID in the notification while the app is in the background or is not running.
My scanner just got a few additional features in January, and now on today's update reported:
Some of that I think I was able to cover (please check if it's correct), but why is background location needed?
PS: If you wonder about the
DEPENDENCY_INFO_BLOCK
, that's easy to get rid of: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.
The text was updated successfully, but these errors were encountered: