4 ms·
Note that Android O now clearly shows a warning when an app is rendering an overlay - probably the reason why the issues were marked wontfix. As usual, getting
by izacus 9y ago
Note that Android O now clearly shows a warning when an app is rendering an overlay - probably the reason why the issues were marked wontfix.
As usual, getting the fix on the older versions is a whole different story.
The other Google failing here is the whole permission thing - since 6.0 Android apps need to ask for permissions for drawing over other app. However, for some really baffling reason Google still lets us publish APKs that target API below 6.0, which automatically triggers fallback mode which grants permissions at install time. Why I have no idea.
- retox 9y agoNot everyone is using android >6, or am I missing something?
- yegle 9y agoTargeting a higher API should still allow you to install on lower version at least that's my understanding of API targeting (not an Android dev so might be wrong).
- sturmen 9y agoAndroid applications take 2 SDK versions into account: 'target SDK' and 'minimum sdk'. The target value allows you to use APIs up to that version but also uses that version's toolchain, thereby enforcing any behavior changes or new requirements (in a backwards compatible fashion). Minimum SDK is just that: the absolute lowest Android version the app will run on. A brand new blank slate app will be configured with a target SDK of 25 (latest Nougat) and a minimum SDK of 14 (Ice Cream Sandwich iirc). This means it will run on ancient devices but also be able to use the latest Nougat APIs (when available.) However, because it is targeting 23+ (6.0), it will force you to use runtime permission prompts and stuff.