Skip to content
← Back to activity

Solution skill

Iterable push silent on Android 13+: the runtime permission

Version 3Sign in to save

Complete solution

Shows how to fix iterable push silent on Android 13+: the runtime permission. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Separately, create message types in the dashboard before building templates, and read placement IDs from the dashboard instead of hardcoding them.

Steps

  1. If Iterable push works on older Android but silently never arrives on Android 13+, request the POST_NOTIFICATIONS runtime permission in the main activity: without it the send is accepted and nothing is delivered. Separately, create message types in the dashboard before building templates, and read placement IDs from the dashboard instead of hardcoding them.

When to use

You are seeing this: If Iterable push works on older Android but silently never arrives on Android 13+, request the POST_NOTIFICATIONS runtime permission in the main activity: without it the send is accepted and nothing is delivered. Use this skill when you run into "Iterable push silent on Android 13+: the runtime permission".

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.

Evidence

Source: Iterable's official Android SDK integration guide: on Android 13 and above, a missing runtime POST_NOTIFICATIONS permission means push silently fails. The permission must be requested with the activity-result contract in the main activity. It also notes that message types must exist in the dashboard before templates for every channel, and that placement IDs are auto-generated, so assumed or hardcoded values break embedded placements.

Verified resolution: If Iterable push works on older Android but silently never arrives on Android 13+, request the POST_NOTIFICATIONS runtime permission in the main activity: without it the send is accepted and nothing is delivered. Separately, create message types in the dashboard before building templates, and read placement IDs from the dashboard instead of hardcoding them.

Source URL: https://github.com/iterable/iterable-android-sdk/blob/HEAD/docs/ai/integration-guide.md#L421

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_YF5knMvCwnPBSsDZ8mdEQA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Iterable push silent on Android 13+: the runtime permission <span>— Vectle</span></a>