feat: add push notifications for web and android

[Linhead]

feat: Implement FCM Push Notifications infrastructure for Android and Web

• Add Firebase Cloud Messaging integration with unified PushService interface
• Create three notification options: "No Notifications", "Background Fetch", "Push"
• Preserve existing Background Fetch functionality for backward compatibility
• Implement message decryption and chat navigation logic for push notifications
• Integrate with ADAMANT Notification Service (ANS) for device token management
• Add Android permissions and Firebase configuration
• Support foreground/background notification handling

Implements [Feat, Enhancement] Push notifications for Web/Android, Desktop #881

Addressed review comments

• Redirect to chat page after login feat: add push notifications for web and android #802 (comment)
• Question about "The 2-second delay prevents race conditions" feat: add push notifications for web and android #802 (comment)
• Security review feat: add push notifications for web and android #802

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
adamant-im	Ready	Preview, Comment	Apr 2, 2026 1:25pm

[github-actions]

Deployed to https://msg-adamant-pr-802.surge.sh 🚀

[Linhead]

Feat: Push notifications for Web/Android, Desktop

[adamantmm]

@Linhead
Please add short pr description and a link to a Trello card

[Linhead]

The task is finished. All review comments and requested changes have been implemented

Test app:
Web - https://adamant-d2hzie3dy-adamant-team.vercel.app/
Android - https://github.com/Adamant-im/adamant-im/actions/runs/23915116300

Testing Summary
The implementation was tested using 4 different accounts across multiple devices and operating systems.

Results:
Windows:
Google Chrome: ✅ OK
Mozilla Firefox: ✅ OK

Android (Phone 1):
Native App: ✅ OK

Android (Phone 2):
Native App: ✅ OK
Mobile Chrome: ✅ OK
Mobile Firefox: ✅ OK

Linux (Ubuntu):
Google Chrome: ✅ OK
Mozilla Firefox: ❌ FAILED (Note: This is a platform-specific issue related to how Firefox Snap/Ubuntu handles background WebPush sockets. It is not an application-level bug.)

Important: Requirements for Push Delivery
Please note that push notifications will only be delivered if the following conditions are met:

The browser tab must be minimized or closed.

The user must be authenticated (logged in via password) with the "Stay logged in" option enabled.

Guidelines for Future Testers:
Before reporting an issue with notifications, please ensure you have performed the following "Self-Audit":

System Notifications: Check that notifications are allowed for your browser/app in the OS settings.

Browser Permissions: Ensure the site has "Allow" permission for notifications.

Focus Mode: Verify that "Do Not Disturb" or "Focus" mode is disabled on your device.

Local Environment: Disable any aggressive ad-blockers or VPNs that might interfere with Firebase/Mozilla Push Service.

Requirement for Bug Reports:
If you have verified the above and still encounter issues, please provide:

Browser Console Logs.
Service Worker Logs (from about:debugging or Chrome's Application tab).