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
Now google requires deveoper to submit the "Location permission declaration form" for the app which requests the LOCATION permission ( android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION ). These 2 permissions are added by sumup SDK.
There is very high requirement to comply for the apps which access to location in background as you see in the above link.
Could you clarify if the library access to location in the background?
To be honest, I hope that the requirement of LOCATION permission would be removed,
as we are adding these permission only for this library and many users are not comfortable to it. Also now Google is very sensitive about this permission now.
The text was updated successfully, but these errors were encountered:
Since ACCESS_BACKGROUND_LOCATION is not declared in the manifest of the SumUp SDK I would assume that it does not access the device's location in background and thus filling the Google Play Background Location Request form is probably not necessary.
Also from looking at the SDK's source code, the location is fetched during login, payment and on every RPC request - but never when the app is in background.
Now google requires deveoper to submit the "Location permission declaration form" for the app which requests the LOCATION permission ( android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION ). These 2 permissions are added by sumup SDK.
https://support.google.com/googleplay/android-developer/answer/9799150?hl=en
There is very high requirement to comply for the apps which access to location in background as you see in the above link.
Could you clarify if the library access to location in the background?
To be honest, I hope that the requirement of LOCATION permission would be removed,
as we are adding these permission only for this library and many users are not comfortable to it. Also now Google is very sensitive about this permission now.
The text was updated successfully, but these errors were encountered: