---
title: "#push-notifications articles | Hashnode"
description: "Explore 284 articles tagged #push-notifications on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/push-notifications"
---

Tag

# #push-notifications

284 posts · 20 followers

[Primocys - IT Company](https://hashnode.com/@Primocys) · [15h ago](https://hashnode.com/posts/automated-push-notifications-an-eligibility-first-architecture/6afd998344fc5b9914151483)

### [Automated Push Notifications: An Eligibility-First Architecture](https://whatsapp-clone-app-development.hashnode.dev/automated-push-notifications-an-eligibility-first-architecture?utm_source=hashnode&utm_medium=feed)

See push notification automation for apps: events, subscription checks, Firebase and a cancellable queue. Get a free estimate for your app idea today.

5 min read · [whatsapp-clone-app-development.hashnode.dev](https://whatsapp-clone-app-development.hashnode.dev/automated-push-notifications-an-eligibility-first-architecture?utm_source=hashnode&utm_medium=feed)

[Sandeep Joshi](https://hashnode.com/@notifysphere) · [2d ago](https://hashnode.com/posts/apns-baddevicetoken-400-causes-and-fix-including-sandbox-vs-production/6afa90a30405dcfe9b6661d3)

### [APNs BadDeviceToken (400): Causes and Fix, Including Sandbox vs Production](https://notifysphere.hashnode.dev/apns-baddevicetoken-400-causes-and-fix-including-sandbox-vs-production?utm_source=hashnode&utm_medium=feed)

Your iOS push fails with 400 and "reason": "BadDeviceToken". Before you delete that token, check one thing: is it going to the right APNs environment? Most of the time it's a sandbox token sent to pro

6 min read · [notifysphere.hashnode.dev](https://notifysphere.hashnode.dev/apns-baddevicetoken-400-causes-and-fix-including-sandbox-vs-production?utm_source=hashnode&utm_medium=feed)

[Parminder singh](https://hashnode.com/@param007) · [6d ago](https://hashnode.com/posts/flash-sale-push-notifications-fcm-topics/6af6762a23037bb26d250a7e)

### [How to notify 50 million users about a flash sale: pull, push and FCM topics](https://systemdesignwithparam.hashnode.dev/flash-sale-push-notifications-fcm-topics?utm_source=hashnode&utm_medium=feed)

The sale starts at 12:00. Marketing wants all 50 million users to know, and most of them have the app closed. Your server can't call a phone, and 50 million is a lot of phones to reach in one minute.

7 min read · [systemdesignwithparam.hashnode.dev](https://systemdesignwithparam.hashnode.dev/flash-sale-push-notifications-fcm-topics?utm_source=hashnode&utm_medium=feed)

[Sandeep Joshi](https://hashnode.com/@notifysphere) · [Nov 7](https://hashnode.com/posts/fcm-unregistered-error-requested-entity-was-not-found-and-how-to-fix-it/6aeeb68a36508ac8f8003281)

### [FCM UNREGISTERED Error: Requested Entity Was Not Found, and How to Fix It](https://notifysphere.hashnode.dev/fcm-unregistered-error-requested-entity-was-not-found-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

FCM 404 UNREGISTERED means the device token no longer works. Why it happens, how to clean up tokens, and when it's a different error.

6 min read · [notifysphere.hashnode.dev](https://notifysphere.hashnode.dev/fcm-unregistered-error-requested-entity-was-not-found-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

[Sandeep Joshi](https://hashnode.com/@notifysphere) · [Nov 7](https://hashnode.com/posts/fcm-sender-id-mismatch-403-and-messaging-mismatched-credential-how-to-fix-it/6aeeb5c136508ac8f8fe0b85)

### [FCM SENDER\_ID\_MISMATCH (403) and messaging/mismatched-credential: How to Fix It](https://notifysphere.hashnode.dev/fcm-sender-id-mismatch-403-and-messaging-mismatched-credential-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

FCM 403 SENDER\_ID\_MISMATCH means your server sends from a different Firebase project than the app's token. How to find and fix it.

5 min read · [notifysphere.hashnode.dev](https://notifysphere.hashnode.dev/fcm-sender-id-mismatch-403-and-messaging-mismatched-credential-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

[SignOps](https://hashnode.com/@signops) · [Nov 5](https://hashnode.com/posts/web-push-not-showing-this-site-has-been-updated-in-the-background/6aeca67b7fd7e5dd698f2d55)

### [Web push not showing: "This site has been updated in the background"](https://signops.hashnode.dev/web-push-not-showing-this-site-has-been-updated-in-the-background?utm_source=hashnode&utm_medium=feed)

Your server got 201 Created, the push reached the browser, and still nothing useful appeared, or Chrome showed its generic "This site has been updated in the background". From here the problem is in t

1 min read · [signops.hashnode.dev](https://signops.hashnode.dev/web-push-not-showing-this-site-has-been-updated-in-the-background?utm_source=hashnode&utm_medium=feed)

[SignOps](https://hashnode.com/@signops) · [Nov 2](https://hashnode.com/posts/web-push-errors-410-gone-404-403-vapid-413-and-429/6ae8aeeae086577b90eb81fc)

### [Web push errors: 410 Gone, 404, 403 VAPID, 413 and 429](https://signops.hashnode.dev/web-push-errors-410-gone-404-403-vapid-413-and-429?utm_source=hashnode&utm_medium=feed)

A web push goes from your server to a push service run by the browser maker: FCM for Chrome and Edge, Mozilla's autopush for Firefox, Apple's service for Safari. They follow the same protocol, RFC 803

2 min read · [signops.hashnode.dev](https://signops.hashnode.dev/web-push-errors-410-gone-404-403-vapid-413-and-429?utm_source=hashnode&utm_medium=feed)

[SignOps](https://hashnode.com/@signops) · [Oct 28](https://hashnode.com/posts/is-firebase-push-notification-free-fcm-pricing-quotas-and-rate-limits/6ae16cb2d0084f4b4b1c4b4d)

### [Is Firebase push notification free? FCM pricing, quotas and rate limits](https://signops.hashnode.dev/is-firebase-push-notification-free-fcm-pricing-quotas-and-rate-limits?utm_source=hashnode&utm_medium=feed)

FCM is free on every Firebase plan, with no message limit. The quotas that do exist, how to raise them, and what costs money around sending.

1 min read · [signops.hashnode.dev](https://signops.hashnode.dev/is-firebase-push-notification-free-fcm-pricing-quotas-and-rate-limits?utm_source=hashnode&utm_medium=feed)

[Alok Singh](https://hashnode.com/@aryansbtloe) · [Oct 22](https://hashnode.com/posts/the-device-side-of-apns-building-a-push-notification-test-client-in-swift/6ad9ec9cc8462159891e1685)

### [The Device Side of APNs: Building a Push Notification Test Client in Swift](https://aryansbtloe.hashnode.dev/the-device-side-of-apns-building-a-push-notification-test-client-in-swift?utm_source=hashnode&utm_medium=feed)

Permission, registration, device tokens, foreground presentation and payload inspection, plus the exact HTTP/2 request your backend needs to send Every backend developer who has implemented Apple pus

13 min read · [aryansbtloe.hashnode.dev](https://aryansbtloe.hashnode.dev/the-device-side-of-apns-building-a-push-notification-test-client-in-swift?utm_source=hashnode&utm_medium=feed)

[Alok Singh](https://hashnode.com/@aryansbtloe) · [Oct 22](https://hashnode.com/posts/the-sending-side-of-apns-a-mac-push-tester-with-keychain-certificates-urlsession-client-auth-and-http-2/6ad9ec638bc27beca883580d)

### [The Sending Side of APNs: A Mac Push Tester with Keychain Certificates, URLSession Client Auth and HTTP/2](https://aryansbtloe.hashnode.dev/the-sending-side-of-apns-a-mac-push-tester-with-keychain-certificates-urlsession-client-auth-and-http-2?utm_source=hashnode&utm_medium=feed)

Finding push certificates in the Keychain, importing .p12 files, answering APNs's client-certificate challenge in URLSession, building the exact request (path, headers, payload), sandbox vs production

12 min read · [aryansbtloe.hashnode.dev](https://aryansbtloe.hashnode.dev/the-sending-side-of-apns-a-mac-push-tester-with-keychain-certificates-urlsession-client-auth-and-http-2?utm_source=hashnode&utm_medium=feed)
