Foreground Service restarts and a notification reappears when the App is closed

6.6.X

As Designed

**Root Cause:** Unity calls `Process.killProcess()` from `onDestroy()`, sending a SIGKILL before the Android Activity Manager Service (AMS) can clean up foreground service records. AMS then spawns a new process to honor those records, causing the foreground service notification to reappear. **Engine Fix:** Identified as an engine-level issue. No fix planned in the near term, changing the process cleanup lifecycle is high-risk. Ideally Unity would use `finish()`/`finishAffinity()` instead of `Process.killProcess()`. **Workarounds (neither fully replicates native Android behavior):** - **WA1 (Recommended):** Override `onUnityPlayerQuitted()` in a custom `UnityPlayerActivity` to send a `STOP_FOREGROUND_ONLY` intent to the service before SIGKILL fires. This clears AMS's foreground obligation so the notification doesn't reappear. Service still restarts in a new process/PID. [Sample project](https://drive.google.com/file/d/1GyATaAk-H9866GbE4so27pLFVmRryq77/). **CustomUnityPlayerActivity.java:** ```java @Override public void onUnityPlayerQuitted() { Intent intent = new Intent(this, com.tapp.MyForegroundService.class); intent.setAction("STOP_FOREGROUND_ONLY"); startService(intent); super.onUnityPlayerQuitted(); } ``` **MyForegroundService.java - onStartCommand():** ```java String action = intent != null ? intent.getAction() : null; if ("STOP_FOREGROUND_ONLY".equals(action)) { stopForeground(STOP_FOREGROUND_REMOVE); return START_NOT_STICKY; } ``` - **WA2:** Run the service in a separate Android process (`android:process=":foreground_service"`). Isolates it from Unity's SIGKILL but introduces significant architectural constraints (separate VM, no shared memory, IPC required, unreliable SharedPreferences across processes).