App doesn't work since Android 15

[splattergamesextended]

I don't know what happened, but the app doesn't do anything anymore. Sending a test notification works, but codes don't get copied or recognized anymore. There have also been no new codes in the history for about a week now.
I'm running GrapheneOS on the newest build (2024102400).
All permissions are set, I tried to deactivate the app, cleared cache, force quit and it changed nothing.

[jd1378]

duplicate of #140

in short, google broke the notification listeners without documenting the change

the simple solution for now is to disable the new "Enhanced Notifications" from notification settings

the other solution that I have not tested but was suggested by MishaalRahman if you know what adb is:

adb shell cmd appops set --user 0 io.github.jd1378.otphelper RECEIVE_SENSITIVE_NOTIFICATIONS allow 

I'm pinning this since other people will be coming here to report the same issue probably.

[splattergamesextended]

Oh yeah, sorry that I missed that. Should have looked in the closed issues first. A permanent fix for other users would be amazing though! Thanks for the workaround, it finally works again!

[jd1378]

sadly this is not something I can fix, google decided to break this for all apps from android 15 going forward. this supposedly increases security in general, but I don't get it when the user's permission is already explicitly needed for reading the notifications.

[splattergamesextended]

Aww man, I just found an article stating this:

"While digging through the Android 14 QPR3 Beta 1 update, I discovered the addition of a new permission named RECEIVE_SENSITIVE_NOTIFICATIONS. This permission has a protectionLevel of role|signature, which means it can only be granted to applications with the requisite role or to applications that the OEM signs. While the exact role that grants this permission hasn’t been defined yet, it’s likely that Google doesn’t intend to open this permission up to third-party apps."

So I can see how there will be no fix for it. Damn Google for this nonsense. If they just included reading OTP codes in AOSP, all of this wouldn't be an issue in the first place.

I guess the only "fix" is to notify users of this change within the app :( Thanks for your great work, it's of course Google that is to blame here, as always...

[jd1378]

yeah, I think telling the users about it inside the app is a good idea, I'll open this issue and close it after I get some time to implement it

thank you for the suggestion

If they just included reading OTP codes in AOSP, all of this wouldn't be an issue in the first place

Exactly my thoughts.