Android端通知未接收问题排查：定时日历类应用技术问询

Hey there, I’ve been in a similar boat with scheduled notifications on Android, so I feel your frustration! Let’s break down the possible culprits here since your internal testing checks out but real users are hitting issues.

• Battery Optimization & Manufacturer-Specific Restrictions
  Even though you tested Android 6-8.1, most brands like Samsung, Xiaomi, Huawei, and Oppo add their own aggressive battery saver layers on top of stock Android. These can silently kill your app’s background processes or block scheduled events. Advise affected users to:

  • Go to Settings > Battery > Battery Optimization, find your app, and set it to "Not Optimized"
  • Check manufacturer-specific settings: Xiaomi’s "Auto-start Manager", Samsung’s "App Power Management", or Huawei’s "Protected Apps"—whitelist your app in these menus.

• Notification Channel Configuration (Android 8.0+)
  On Oreo and above, notifications won’t fire if you don’t set up a valid NotificationChannel, or if the user has disabled the channel later. Double-check:

  • You’re creating channels with NotificationChannel and registering them via NotificationManager.createNotificationChannel() on app launch
  • Your scheduled notifications target the correct channel ID
  • Remind users to verify Settings > Apps > [Your App] > Notifications to ensure the channel is enabled and has sound/vibration turned on.

• Scheduling Logic Limitations
  If you’re using AlarmManager, note that on Android 6.0+, setExact() or setExactAndAllowWhileIdle() are required for precise timing—but even these can be delayed in Doze mode. For Android 7.0+, consider switching to WorkManager (or JobScheduler for older versions) since it handles Doze and battery optimizations more reliably, especially if your notifications don’t need millisecond-level precision.

• App Process Being Killed
  Users might force-close the app, or the system might kill it under memory pressure. If you’re relying on a background service, use a Foreground Service (with a persistent notification) on Android 8.0+ to prevent the system from terminating it. Alternatively, trigger notifications directly via a PendingIntent attached to a broadcast receiver—this way, even if the app is killed, the broadcast can still fire and show the notification.

• Time Zone/System Time Mismatches
  Some users might have incorrect system time or time zone settings. Make sure your scheduling logic uses the device’s local time zone (via Calendar.getInstance() or Instant.atZone(ZoneId.systemDefault())) instead of hardcoding UTC without conversion. Also, handle cases where the user changes time zones after scheduling a notification.

To narrow down the issue, ask affected users to share:

• Their exact device model and Android version
• Screenshots of your app’s battery optimization settings
• Whether they use third-party battery saver or security apps
• If notifications fail consistently, only after reboot, or randomly

More often than not, manufacturer-specific battery restrictions are the root cause here. I’ve spent countless hours troubleshooting similar issues, and walking users through whitelisting the app usually fixes most cases. Hang in there!

内容的提问来源于stack exchange，提问作者Yuri