You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Push notification priority is changed to PRIORITY_UNKNOWN.
During the discussion regarding a push notification issue signalapp/Signal-Android#12325 for Signal (which has been fixed) a Signal developer noted that their push notification priority signalapp/Signal-Android#12325 (comment) is changed from high-priority to PRIORITY_UNKNOWN. Also a developer of ShiftOS stated that with the ShiftOS-L flavor there are no GMS available and they are not changing any priority signalapp/Signal-Android#12325 (comment) the question arose if this might be an issue with microG.
I noticed that there was this issue #338 requesting to put the app into a temporary whitelist when a high-priority push message is retrieved which might be related. However the pull request #732 for the implementation was already resolved long ago in commit 6002388.
Would be great if you could share any insight regarding this behaviour.
System
Android Version: [10]
Custom ROM: [ShiftOS-L 3.7 (20220511)]
In this case, microG does not have privileged access to the device idle controller and can't wake up apps that are not exempted from battery optimizations. Did you exempt Signal from battery optimizations?
Affected app
Name: [Signal]
Package id: [org.thoughtcrime.securesms]
Describe the bug
Push notification priority is changed to PRIORITY_UNKNOWN.
During the discussion regarding a push notification issue signalapp/Signal-Android#12325 for Signal (which has been fixed) a Signal developer noted that their push notification priority signalapp/Signal-Android#12325 (comment) is changed from high-priority to PRIORITY_UNKNOWN. Also a developer of ShiftOS stated that with the ShiftOS-L flavor there are no GMS available and they are not changing any priority signalapp/Signal-Android#12325 (comment) the question arose if this might be an issue with microG.
I noticed that there was this issue #338 requesting to put the app into a temporary whitelist when a high-priority push message is retrieved which might be related. However the pull request #732 for the implementation was already resolved long ago in commit 6002388.
Would be great if you could share any insight regarding this behaviour.
System
Android Version: [10]
Custom ROM: [ShiftOS-L 3.7 (20220511)]
microG
microG Core version: [v0.2.24.214816]
microG Self-Check results: [All ticked]
The text was updated successfully, but these errors were encountered: