I have a web-to-app project that already uses Firebase Cloud Messaging. Tokens generate correctly and a manual test from the Firebase console lands on the intended Android device, yet the automatic notifications that should fire from our back-end never reach either the web version or the Android web-app wrapper. Here’s the current setup: • Original website relied on Firebase Web Push. • Site was converted into a WebView-based Android app. • I added native FCM to regain push support—tokens look fine. • Cloud Functions (Node.js) create the notification payloads, log “message sent,” but nothing shows up on devices unless I issue a direct console test. What I need: 1. Diagnose why production events are not triggering visible notifications in the Android app or the browser. 2. Patch any service-worker, manifest, or FCM payload issues so both surfaces display the push automatically. 3. Leave concise notes or Git comments so I can replicate the fix on staging. Acceptance criteria: • An event generated by the back-end produces a notification on at least one Android device and one desktop browser within 10 seconds. • No token loss or repeated permission prompts after the fix. • All changes compile cleanly in Android Studio and pass existing automated tests. Tech stack involved: Firebase Cloud Messaging, Cloud Functions (Node.js), Service Worker, WebView, Android Studio, Java/Kotlin. Access to the Git repo and Firebase project will be provided immediately after kickoff.