Status Update
Comments
lb...@gmail.com <lb...@gmail.com> #2
lb...@gmail.com <lb...@gmail.com> #3
Look like this was introduced by the fix for
lb...@gmail.com <lb...@gmail.com> #4
I can't add the property using gradle.beforeProject
like i've been able to do with other plugins (kapt) that have similar isolation issues. Perhaps because the JetGradlePlugin is added and executed earlier than my own code.
sa...@google.com <sa...@google.com>
lb...@gmail.com <lb...@gmail.com> #6
Thanks for the patch - I'll cherry pick and adapt internally
lb...@gmail.com <lb...@gmail.com> #7
ma...@gmail.com <ma...@gmail.com> #8
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 9
- Android Gradle Plugin 8.8.0-alpha09
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
ma...@gmail.com <ma...@gmail.com> #9
I'm using Ladybug Feature Drop RC02 and the issue is back, did the change get reverted?
te...@gmail.com <te...@gmail.com> #10
I reviewed the details shared and I was unable to reproduce it on my end using the steps on RC1
, RC2
but being able to reproduce it on Canary6
(since fix landed on Canary9
).
I also checked that fix is actually present on the AS Ladybug Feature
release branch, however, this isn’t public yet but you can see those for the beta instead more in particular 2024.2.2-beta01
tag:
Having said that will be great if you can provide more details, since there's no sign so far that those changes got reverted somehow.
As a side note there’s the possibility that even if the fix is present as shown the change might not be taken into consideration in the case that platform artifact embedded in studio isn’t updated properly including it. I would say this is unlikely to happen due to automatic processes.
lb...@gmail.com <lb...@gmail.com> #11
When I commented earlier, I made extra certain that I was indeed using RC02. However since then I've been unable to duplicate again. My suspicion is that somehow the JetGradlePlugin from Ladybug was being used by Ladybug Feature Drop as I have both installed.
vi...@google.com <vi...@google.com> #12
Thanks for the feedback. We have looked into the issue you have reported and would like to inform you that this is working as intended.
Description
1. Install apps that target API that's lower than API 33, and can show notifications yet chooses to show them in the background.
A perfect example Example is this one:
2. Notice that some of such apps don't get to show the notification permission dialog right away, and the reason is the poor backward compatibility that's also documented:
"
If your app targets 12L (API level 32) or lower, the system shows the permission dialog the first time your app starts an activity after you create a notification channel, or when your app starts an activity and then creates its first notification channel. This is usually on app startup.
"
- What happened.
When the time comes to show notifications, because the apps didn't get to show the notification permission dialog, it also won't show the notification itself.
The reason for this, is that some apps don't create the notifications channels right away. Only when it's time to use them.
You can also create your own POC app, that will use an Alarm/Worker to just schedule showing a notification. Just make sure the creation of the notification channel is also there.
- What you think the correct behavior should be.
The dialog should be shown whether the app has created notification channels or not.
Currently it breaks many apps because of it.
- Is this a security related issue? Yes/No
Yes, for apps that are related to security and have this implementation too.