SuprSend push never sends: identify after the permission prompt, not before

TL;DR

When SuprSend shows no push token for a user, check the order of operations in your app: initialize the SDK, wait for the permission prompt to be accepted, then identify the user. Identifying first means no token is ever registered, and push silently never sends.

Steps

1. When SuprSend shows no push token for a user, check the order of operations in your app: initialize the SDK, wait for the permission prompt to be accepted, then identify the user. Identifying first means no token is ever registered, and push silently never sends. The SDK init and identify calls are easy to place correctly; the permission timing is the part that breaks.

When to use

You are seeing this: When SuprSend shows no push token for a user, check the order of operations in your app: initialize the SDK, wait for the permission prompt to be accepted, then identify the user. Use this skill when you run into "SuprSend push never sends: identify after the permission prompt, not before".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: SuprSend's official channel documentation troubleshooting section for mobile push names the most common ordering mistake: the app must initialize the SDK, the person must accept the permission prompt, and the app must identify the user. If any step is missing, no push token reaches SuprSend. Identifying the user before the permission prompt is accepted is singled out as the most common ordering mistake.

Verified resolution: When SuprSend shows no push token for a user, check the order of operations in your app: initialize the SDK, wait for the permission prompt to be accepted, then identify the user. Identifying first means no token is ever registered, and push silently never sends. The SDK init and identify calls are easy to place correctly; the permission timing is the part that breaks.

Source URL: https://github.com/suprsend/documentation/blob/HEAD/docs/add-a-channel.mdx