What to Do If Stitch Notifications Are Not Working

Start with the setting closest to the problem

Missing notifications almost always trace back to one of a small number of places: a global toggle inside Stitch, a mute on the specific chat, a permission the operating system or browser is blocking, or a battery-saving setting quietly stopping background activity. Working through them in order — Stitch settings first, then device settings — finds the cause faster than guessing.

Check the chat itself

Before anything else, confirm the specific chat is not muted — open it, tap the name, and check whether Mute is turned on. A muted chat still delivers messages and updates your unread count, it simply does not alert you, which can look identical to "notifications are broken" if you have forgotten you muted it.

Check the global notification toggle

Go to Settings → Privacy & Security → Notifications and confirm notifications are turned on at the account level. This is the master switch — if it is off, no chat will notify you regardless of its individual mute state.

On iPhone and Android

1. Open your device Settings, find Stitch under Notifications (or Apps → Stitch → Notifications), and confirm notifications are allowed and set to show alerts, not just badges.
2. Check that Stitch is excluded from any aggressive battery-saving or "sleeping apps" feature — on some Android phones, this can stop background notifications even when the in-app setting is on.
3. Confirm Do Not Disturb or Focus modes are not silently filtering Stitch notifications during certain hours.
4. If you recently reinstalled the app or restored your phone, reopen Stitch and make sure you are fully signed in — a signed-out or freshly installed app cannot register for notifications until you sign back in.

On the web

1. Browser notifications require explicit permission — check your browser's site settings for stitchmessaging.com and confirm Notifications are set to Allow, not Block or Ask.
2. If you previously denied the permission, you generally need to reset it manually from your browser's site settings rather than being asked again automatically.
3. Web notifications only work while your browser is capable of running in the background — closing the browser entirely, or using aggressive tab-suspension extensions, can prevent them from arriving.

Still not working after all of the above

If notifications remain silent after confirming the chat is not muted, the global toggle is on, and device or browser permissions are allowed, try fully signing out and back in — this re-registers your device for push notifications, which resolves most remaining cases caused by a stale registration (common after an OS update or a long period without opening the app).

If the problem persists after that, contact Stitch support with your platform (iPhone, Android, or web) and what you have already checked, so the issue can be looked into directly rather than repeating the same steps.

A note on notification content and privacy settings

If notifications are arriving but showing less detail than you expect — a generic alert instead of the sender's name and message preview — check whether that chat is locked under Chat Lock, or whether your notification preview setting has been turned down under Settings → Privacy & Security. Both are deliberate privacy behaviors, not a bug: a locked chat always shows a generic notification by design, and disabling message previews does the same thing across every chat. Neither of these is what "notifications not working" usually means, but it is a common enough point of confusion to rule out before assuming something is actually broken.

A pattern worth recognizing: notifications for one chat but not others

If some chats notify you normally and only specific ones do not, the cause is almost always local to those chats rather than a device-wide problem — most commonly, a mute you forgot about, or (in a group) a per-member mute an admin applied. A device or permission problem, by contrast, tends to affect every chat at once, since it blocks notifications at a level above any individual conversation. Narrowing down whether the problem is "everything" or "just this one chat" is usually the fastest way to skip straight to the right fix.

Notifications after switching phones or reinstalling

Moving to a new phone, restoring from a backup, or reinstalling Stitch after deleting it are all situations where notifications commonly need a moment to catch up. Signing in fully (not just leaving the app open in the background) is what actually registers your new device for push notifications — simply having the app installed is not enough. If you have recently done any of these and notifications have not started working within a short time of signing in, signing out and back in again is the most reliable way to force a fresh registration.