fix(push): only expedite FCM NotificationWorker on Android 12+ - #6784
Conversation
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
|
/backport to stable-25.0.x |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe Firebase messaging service now uses Priority: ➖ Normal Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The reported Huawei Android 10 case used the gplay build, and the change keeps its notification work non-expedited on older Android versions. No material merge blocker is evident. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to Notification work uses ordinary scheduling on older Android versions and retains expedited scheduling with a fallback on Android 12 and later. The push-data checks remain in place. No security issue introduced by this change was identified, though platform failure behavior was not fully verified. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📱 QA build
The QA build installs alongside a released Nextcloud app, so you can keep Downloading the file requires a GitHub account, so open this link on the |
|
/backport to stable-25.0.x |
fix #6738
Thank you @hamars
🏁 Checklist
/backport to stable-xx.x🤖 AI (if applicable)