This document details an issue with Spark email push notifications on a Xiaomi MIX 4 running the Android 12 development version. The issue involves the failure of notifications to be delivered even though the app has received the FCM message. I have included relevant details and screenshots to aid in troubleshooting this issue.
### Device
Xiaomi MIX 4 development version (22.8.25) running Android 12
### Related App Versions
- Spark: 2.11.10
- Google Play Services: 22.32.12
### fcmfix
- 0.4.10 or (0.4.11+ PR #76)
- All recommended scopes checked, Spark email checked within the app
- FCM connection appears to be normal
### Spark Email Settings
- Notification permissions are not closed, verified.
- App auto-start permissions are enabled.
- Manual startup to fetch emails works correctly.
### Situation
(Thanox not installed; issue is likely not #51)
Error similar to `xxx returned error code=404 to broadcast` is occurring, likely related to the triggering of self-start upon receiving a message. See screenshot 1 for notification history.
The second screenshot illustrates the log output from Miui Security Center.
I use Spark email (com.readdle.spark) as an example. In the screenshot (screenshot 1), there is no self-start record at 23:00. This could be due to PR #76, as this screenshot was taken after the PR was included in the app. At 23:27, I sent a test email to the configured email address within the app from another email address. According to FCM logs, the message was received around 23:28. However, Spark email did not successfully launch and display the notification.
### LSPosed Logs
https://tmp.link/f/63079a0591590
This article is created by nurl and is licensed under the Creative Commons Attribution 4.0 International License.
All articles on this site, unless otherwise specified as reprints or sources, are either original works or translations by this site. Please ensure proper attribution before reprinting.