Obsolete
Status Update
No update yet.
Comments
ar...@google.com
Thank you for reporting this issue. We have shared this with our engineering team and will update this issue with more information as it becomes available.
ma...@gmail.com
@2 This bug occurs even if the check is inside onActivityResult, yet I've tested it on Android 7.1.2 and below, and it doesn't occur there.
I've also noticed that the check works fine if I change the orientation after returning from the settings screen (meaning the activity was re-created)
I've also noticed that the check works fine if I change the orientation after returning from the settings screen (meaning the activity was re-created)
is...@google.com
[Deleted User] <[Deleted User]>
For resolving "draw-on-top feature cannot be toggled", you need to add "android.permission.SYSTEM_ALERT_WINDOW" permission in Android Manifest file.
ub...@gmail.com
@4 Then the bug is different for this case: why open this screen, if this permission isn't even available for this app... It should do something else. Maybe throw an exception that tells that the permission is missing from the manifest.
Also, the main isssue does exist: the check of the permission always returns false in the case I've shown.
Also, the main isssue does exist: the check of the permission always returns false in the case I've shown.
ad...@google.com
@4 Bug exists on DP3 too (OPP3.170518.006)
mo...@gmail.com
I can confirm the Settings.canDrawOverlays() always returns false when called from within Activity.onActivityResult() (latest Android O Emulator x86). And no such problems on earlier versions of Android.
However, in onActivityResult(), if instead I post a Runnable to the main thread handler, and call canDrawOverlays() in that, then it returns true. So I guess onActivityResult() is being called a little too early.
However, in onActivityResult(), if instead I post a Runnable to the main thread handler, and call canDrawOverlays() in that, then it returns true. So I guess onActivityResult() is being called a little too early.
st...@gmail.com
On further inspection, you need to wait about a second (in my few tests, between 900ms and 1300ms running the Android O DP3 emulator on a Late 2013 MBP) before canDrawOverlays() begins to return true.
Description
"This constant was deprecated in API level 23. Use headerTextColor instead."
I'm trying to apply that attribute to a DatePicker style following way:
<style name="MyDatePickerStyle" parent="@android:style/Widget.Material.DatePicker">
<item name="android:headerTextColor">@color/red</item>
</style>
But AAPT responds with following error ouput:
> AAPT: No resource found that matches the given name: attr 'android:headerTextColor'.
By documentation, `headerTextColor` attribute should be accessible, but unfortunately it is being stripped out of android.jar thus not being accessible.
Running on an empty project with minSdkVersion=targetSdkVersion=compileSdkVersion=23, buildToolsVersion=25.0.3, Android Studio 2.3, android gradle plugin 2.3.0.
See corresponding question at stackoverflow: