From 28d7485c26303a08acf4391bf034b43bac0bb031 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 26 Aug 2026 21:09:19 -0400 Subject: [PATCH] The service was declared under the wrong package and never resolved MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The manifest said ".MessengerService" while the activity beside it says ".app.MainActivity" — so the class resolved to io.flamenet.messenger.MessengerService, which does not exist. `dumpsys package` reported "No services found" and starting it would have thrown ClassNotFoundException at the moment the app was backgrounded, which is the moment nobody is watching. Verified on the emulator after the fix, end to end: - backgrounding the app starts it, isForeground=true, types=0x200 (REMOTE_MESSAGING), ongoing notice on flamenet.ongoing - iOS sent PUSH2 at 932.474; the Android notification posted at 931.466 on a device whose clock matches the host — so the alert arrived about a second BEFORE the sender finished rendering its own copy - repeated with a fresh marker to prove it was not a stale notification: when= moved 848.867 -> 931.466 That is a closed app on Android alerted in about a second with nobody in the middle. Co-Authored-By: Claude Opus 5 --- app/src/main/AndroidManifest.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/AndroidManifest.xml b/app/src/main/AndroidManifest.xml index 984d403..ad0bda3 100644 --- a/app/src/main/AndroidManifest.xml +++ b/app/src/main/AndroidManifest.xml @@ -62,7 +62,7 @@