Troubleshooting: web push
Web subscriptions failing or the prompt not appearing.
- Why does my scheduled push notification show a different time in the dashboard?
- Why does the Chrome browser logo appear instead of my custom icon on Windows web push notifications?
- Why are new web push subscribers not receiving a push token?
- Why does the Web SDK load the wrong Application Code when navigating between subdomains?
- Why is the Subscription Widget not appearing when using the Web SDK via NPM?
- Why am I not receiving events from the Event Streaming Integration at my webhook endpoint?
- Why isn't the browser's native permission prompt showing after a user accepts my custom web push prompt?
- Why do I see a 'failed to fetch' or 'failed to load' error when accessing the Pushwoosh Control Panel?
- After migrating from another web push provider, why aren't my previous subscribers showing up in Pushwoosh?
- Why am I seeing a `TypeError: Cannot read property 'init' of null` error when using the Pushwoosh React Native plugin in my Expo project?
- I'm getting a connection error (e.g., 401) when setting up the Pushwoosh Web Push SDK
- How do I fix 401 Unauthorized errors when using the Pushwoosh Web SDK?
- How do I fix "Invalid Credentials" errors for Web Push (Chrome/Firefox) notifications?
- Why isn't the Pushwoosh web push subscription prompt showing up after integrating the Web SDK?
- How can I fix Cumulative Layout Shift (CLS) issues caused by the Pushwoosh subscription prompt?
- Cannot get the Chrome subscription pop-up again after dismissing it
- Web SDK is not working and I am getting the "Pushwoosh init failed DOMException" error