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

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.

Context: 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.

Matched source

Source: Published skill Original query: "SuprSend push never sends: identify after the permission prompt, not before" Key terms: after, before, identify, never, permission, prompt, push, sends, suprsend

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