Bug 495146 - kdeconnect android 1.32.7 cannot receive OTP notifications after upgrading to Android 15
Summary: kdeconnect android 1.32.7 cannot receive OTP notifications after upgrading to...
Status: RESOLVED UPSTREAM
Alias: None
Product: kdeconnect
Classification: Applications
Component: messaging-application (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Redman
URL:
Keywords:
: 497676 498862 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-10-21 15:20 UTC by David Korth
Modified: 2025-01-19 13:27 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Korth 2024-10-21 15:20:40 UTC
After upgrading to Android 15, whenever an SMS OTP message is received, kdeconnect shows "Sensitive notification content hidden". This is caused by an undocumented new feature where the Android application requires a new permission, RECEIVE_SENSITIVE_NOTIFICATIONS.

https://www.reddit.com/r/androiddev/comments/1g7tdld/android_15_breaks_notification_listeners/

SUMMARY


STEPS TO REPRODUCE
1. Install KDE Connect on an Android 15 device (or upgrade an existing device with KDE Connect to Android 15).
2. Receive an SMS OTP message.

OBSERVED RESULT
KDE Connect on connected devices shows "Sensitive notification content hidden".

EXPECTED RESULT
KDE Connect on connected devices shows the actual message.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel 6.11.4, KDE Plasma 6.2.1
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Comment 1 David Korth 2024-10-21 15:23:20 UTC
A workaround for now is to manually run this adb command:

adb shell cmd appops set --user 0 org.kde.kdeconnect_tp RECEIVE_SENSITIVE_NOTIFICATIONS allow
Comment 2 Bug Janitor Service 2024-10-21 21:06:37 UTC
A possibly relevant merge request was started @ https://invent.kde.org/network/kdeconnect-android/-/merge_requests/492
Comment 3 Simon Redman 2024-10-21 21:34:04 UTC
Thanks for reporting this. Given the sensitivity level Android has assigned this permission, I don't think we will be able to use this permission. We can give it a try.

You should still be able to access the OTP using the KDE Connect SMS app, since that does not use the notifications path.
Comment 4 David Korth 2024-10-21 22:39:45 UTC
It might be worth adding the workaround command to the documentation. (Also note that a device reboot might be needed after running the command.)
Comment 5 Simon Redman 2024-11-04 22:04:23 UTC
Updated documentation: https://userbase.kde.org/KDEConnect#Sensitive_Notification_Content_(Android_15+)
Comment 6 FeRD (Frank Dana) 2024-11-15 16:26:56 UTC
(In reply to Simon Redman from comment #5)
> Updated documentation:
> https://userbase.kde.org/
> KDEConnect#Sensitive_Notification_Content_(Android_15+)

Part of the added content is this subsection:

Disable Enhanced Notifications
In the notification settings, disable "Enhanced notifications" which will remove this restriction.

...But that's it, full stop. It seems like a discussion of the consequences/tradeoffs of doing that would be warranted — I assume there must be SOME, removing the sensitive-notifications restriction can't be the only effect it has?
Comment 7 FeRD (Frank Dana) 2024-12-01 22:48:05 UTC
(In reply to FeRD (Frank Dana) from comment #6)
> Disable Enhanced Notifications
>
> It seems like a discussion of the
> consequences/tradeoffs of doing that would be warranted — I assume there
> must be SOME, removing the sensitive-notifications restriction can't be the
> only effect it has?

Addressing my own concern, it appears from this Reddit conversation[1] that disabling Enhanced Notifications (which is a Messages app setting, turns out — I thought it was systemwide) will turn off all smart replies, response suggestions, notification reply actions, etc. So, it's pretty drastic.

[1]: https://www.reddit.com/r/GooglePixel/comments/1gls85v/enhanced_notifications_keep_turning_on_after/
Comment 8 Simon Redman 2025-01-19 13:27:36 UTC
*** Bug 497676 has been marked as a duplicate of this bug. ***
Comment 9 Simon Redman 2025-01-19 13:27:52 UTC
*** Bug 498862 has been marked as a duplicate of this bug. ***