DODROID-884
Expected
Google Play Protect service runs stably in the background while editing notes, without interruption.
Observed
Every few minutes while editing a note, a pop-up appears stating "Google Play Protect service has stopped" or "Google Play Protect service keeps stopping." Occasionally, Google Play Services or the Simplenote app itself crashes. The pop-ups appear mid-session (sometimes mid-word), disrupting the writing flow. No data loss or other functional effects have been observed beyond the disruptive notifications. The issue occurs consistently during note editing sessions and has been reported across multiple devices over the course of several days. It does not appear to affect other apps.
Reproduced
The bug reproduces consistently during active note editing sessions:
- Open the Simplenote app on Android.
- Open or create a note and begin editing.
- Continue editing for 3–4 minutes.
- Observe a pop-up notification: "Google Play Protect service has stopped" or "Google Play Protect service keeps stopping."
- Dismiss the pop-up and continue editing.
- Observe the pop-up reappearing every few minutes.
Device 1
- Device Make: Google
- Device Model: Pixel 10 Pro
- Android Version: 17 (beta)
Device 2
- Device Make: Google
- Device Model: Pixel 6 Pro
- Android Version: Not specified
DODROID-884
Expected
Google Play Protect service runs stably in the background while editing notes, without interruption.
Observed
Every few minutes while editing a note, a pop-up appears stating "Google Play Protect service has stopped" or "Google Play Protect service keeps stopping." Occasionally, Google Play Services or the Simplenote app itself crashes. The pop-ups appear mid-session (sometimes mid-word), disrupting the writing flow. No data loss or other functional effects have been observed beyond the disruptive notifications. The issue occurs consistently during note editing sessions and has been reported across multiple devices over the course of several days. It does not appear to affect other apps.
Reproduced
The bug reproduces consistently during active note editing sessions:
Device 1
Device 2