Why Does Google Play Keep Asking About Wispr Flow Permissions?
Last updated: October 31, 2026
Available on: Android
Google Play periodically asks you to review apps with accessibility access. Wispr Flow uses that access to insert dictated text into the field you are typing in. A reminder does not mean anything is broken.
First, check whether Flow still works
Open a notes app.
Tap an empty, normal text field.
Dictate a short phrase with the Flow Bubble.
If the text appears, your permissions are working and you can ignore the reminder. If it works here but not in another app, the problem is specific to that app; in chat apps, give the text a moment to appear.
Note: Flow does not insert into password, numeric or phone fields. URL bars are excluded from content reading, not insertion.
Notification quick-reply boxes support insertion. Flow attempts insertion into Chrome's address bar, but Chrome can reject it, sending the text to the clipboard. Some Chrome-hosted fields may offer no copy-button fallback even when text is missing.
When Flow detects an insertion failure, it copies the transcript to the clipboard, posts a notification that text was copied, offers a copy button and saves it in History. Paste manually; the copy button disappears after about 5 seconds, so tap promptly or re-copy from History.
If normal insertion fails, Flow leaves nonempty or unreadable fields untouched. In split-screen, it refuses fields belonging to neither the starting app nor the current foreground app.
Silence the reminder
These reminders come from Google Play, not Flow, and Flow cannot turn them off. Use Settings → Notifications → App notifications → Google Play Store to turn off its notifications or a specific category. Settings vary by phone.
Flow's own accessibility alerts indicate a problem, unlike the Play reminder. Flow also asks for Google Play reviews through Enjoying Flow? and notifications in App Feedback; mute that category in Flow's notification settings to silence review notifications.
Re-enable accessibility
Restarts, updates and battery management can interrupt accessibility. Flow tries to reconnect while access remains on; only you can restore access if it is off.
The Wispr Flow needs attention notification and Home's Flow can't insert text → Go to Settings open Flow's recovery screen, not Android Settings. Signed-in users who completed setup also reach it when opening or returning to Flow with access off.
Note: Accessibility access lets an app read screen content and interact with apps on your behalf. If Android restricts access, you may need Allow restricted settings; review Android's restricted-settings guidance. For installs outside Google Play, Android can block re-enabling access or revoke it after a force stop; Play Store installs are not subject to these restrictions.
The instructions advance automatically; tap anywhere to advance faster. Open settings appears after the final instruction.
Important: Enable the main Wispr Flow accessibility service, not Wispr Flow shortcut. Leave the shortcut off; Flow cannot finish permission setup while it is on.
Select Open settings on Flow's recovery screen.
Read the accessibility notice, if shown, before choosing Agree.
Open Accessibility → Downloaded apps → Wispr Flow. Samsung: Installed apps; Vivo/Motorola: Wispr Flow directly under Accessibility.
Turn on the main Wispr Flow accessibility toggle, confirming with OK on Xiaomi devices.
Not now returns to setup. Open settings reopens the notice only until you agree; afterwards, it opens Android Accessibility settings directly. If Oops, something isn't right appears, use its Open settings button to turn off the shortcut; this bypasses the notice.
After you agree, Flow can return automatically when access is enabled within five minutes, provided its recovery screen remains open in the background. Otherwise, switch back manually.
While Flow is running, restoring revoked access can reconnect it in about one second. Once Flow reconnects, the Home alert and the notification clear on their own — including when you re-enable access directly in Android Settings — so you do not need to open the Home screen, and no dictation is required to reconnect. The notification also dismisses when tapped. Repeat the notes-app test to verify insertion.
What the bubble is telling you
Note: Bubble recovery and automatic restarts require sign-in, completed setup and permission to display over other apps. Without that permission, no bubble appears; restore it and reopen Flow.
What you see | What to do |
Pulsing loader | Wait while Flow reconnects; dictation is paused and tapping does nothing. |
Retry icon | Permission remains granted; tap to restart the connection without opening Settings. |
Warning triangle | Access is off; tap to open Flow's recovery screen and follow the steps above. |
The repair bubble appears only while a text field is focused, with the keyboard open; it hides when focus leaves and returns on the next focus. Password, numeric and phone fields suppress it; URL bars and notification replies can show it. It waits until dictation finishes and cancels snooze when shown.
After 60 seconds of continued reconnecting, an eligible bubble changes to a retry icon. With access still on, repair alerts can take up to 60 seconds after opening Flow or 15 seconds after an update; no notification appears during the reconnecting wait. Turning access off triggers the triangle as soon as detected, at the next eligible focused field.
Recovery clears the prompt. Flow Bubble reconnected. appears only if the repair bubble was visible, and not on the session's first connection unless Flow had already shown a delayed startup or post-update repair prompt.
If Flow isn't responding while accessibility is on
The Flow isn't responding / Tap to restart Wispr Flow. notification opens Home. Neither it nor the Home card requires a focused text field.
Select Restart Flow on Home.
Repeat the notes-app test.
If it still fails, Android can be stuck despite showing access as on; Flow cannot always detect this.
Xiaomi, Huawei/Honor and Tecno/Infinix/itel may need autostart or app launch re-enabled before accessibility recovery.
Where available, Wispr Flow stopped replaces the restart card. Fix in Settings opens a floating guide over Accessibility settings; its notification also offers Open app. Use Open autostart settings first if offered.
Allow Wispr Flow to autostart in your device settings if required, before toggling access.
Open Wispr Flow's Accessibility settings using the path above.
Turn off Wispr Flow.
Turn on Wispr Flow again.
Repeat the notes-app test. A phone restart or app update can also clear this stuck state, but cannot replace restoring lost permission.
If no repair notification appears
With all Flow notifications disabled, access-loss and restart prompts use brief on-screen messages instead. The stuck-state message, Wispr Flow stopped. Turn it off and on again in Accessibility settings., appears only where that recovery prompt is available.
Blocking only Accessibility Status (under Settings → Notifications → Wispr Flow) or filtering it with Do Not Disturb does not trigger these messages. New accessibility alerts replace earlier ones rather than stacking.
After a reboot or app update, Flow can restart if the prerequisites above are met and Android allows it. With access off, it starts to show Wispr Flow needs attention / Accessibility service was turned off. Tap to re-enable.; access must still be restored for insertion. These boot/update alerts have no on-screen-message fallback.
After a force stop, no automatic restart, notification, bubble or background recovery occurs until you reopen Flow or reboot. An update that leaves Flow unable to start also prevents alerts. Re-enabling accessibility alone does not restore the bubble while Flow is stopped: reopen Flow, then repeat the notes-app test.
For repeated interruptions, follow Setup Wispr Flow on Android to allow background use without battery optimization. Some phones also need autostart or a Recent Apps lock.
Still stuck?
If accessibility is enabled but text still does not appear, see Flow Bubble troubleshooting. Contact support if the notes-app test still fails after recovery; include your device model, Android version, the message or icon you see, and the steps you tried.