Repository navigation
Conversation
Flows can now ask users to allow push notifications with the Request permission action. Each SDK gets an article on answering the request from the app (iOS, Android, Flutter, React Native, Unity, KMP, Capacitor), linked from Respond to actions and the sidebars. The notes saying flows don't trigger permission requests are replaced on the actions, events and v4 migration pages. The iOS getFlowConfiguration parameter table follows the signature order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add a Request permission section to Actions: the triggers it is offered on, the After response section, when the request is sent again, and a warning that names, per Adapty SDK, what the flow does when the app doesn't answer, with links to the seven SDK guides. The Action order list and the custom-action use cases now point to it, and purchase outcomes list it among the actions an outcome can't hold. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The seven SDK guides now share one outline: before you start, how the flow requests a permission, implement the handler, register it, test. Each states what happens without a handler and when the handler throws, as the SDK code does it. Minimum versions are KMP and Capacitor 4.1.0, Unity 4.1.0 and 4.3.0 on Android. Handlers only ask for the permission, the Android dialog needs targetSdk 33, the KMP example asks from the resumed activity, and the metadata titles fit 60 characters. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each Respond to actions page gets a Handle permission requests section that says where the request goes and what happens without a handler, plus a pointer under the intro. The events pages and v4 migration guides no longer call the handler reserved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e permission request Assign the seven handle-permissions guides to sdk-flows-display, record the per-SDK no-handler and throw behavior with evidence, the open Android modal-activity question, and the ripple of the builder section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flows get a Request permission action that asks users to allow push notifications. The Adapty SDK doesn't show the system dialog: it passes the request to the app, which shows the dialog and returns the answer to the flow. This PR documents both sides.
Important
These articles describe a Flow & Paywall Builder action that isn't released yet. Merge this PR only after the action ships in the builder.
Rollout order: the builder ships the action with a "Your app must handle this request" warning that has no links; then this PR is published; then the builder warning gets links to the seven
*-handle-permissionsguides.What changed
New: Handle permission requests in flows, one guide per SDK (
*-handle-permissions, added to each platform sidebar after Respond to actions). All seven share one outline: Before you start, How the flow requests a permission, Implement the handler, Register the handler (iOS: pass it to the flow configuration; Android: pass the listener), Test the permission request.AdaptySystemRequestsHandler, passed toAdaptyUI.getFlowConfiguration(systemRequestsHandler:)onShowRequestPermissionon the flow event listenerAdaptyFlowDefaultEventListeneranswersfalse: no dialog, After response runs at onceonRequestPermissionhandler on each flow viewdeniedwith a log warning: no dialog, After response runs at once (iOS and Android)deniedAdaptyUISystemRequestsHandlerviaAdaptyUI().setSystemRequestsHandler()IAdaptyUISystemRequestsHandlerviaAdapty.SetSystemRequestsHandler()AdaptyUISystemRequestsHandlerviaAdaptyUI.setSystemRequestsHandler()onRequestPermissionhandler on each flow viewdeniedUnity needs 4.3.0 on Android because in 4.1.x an answer sent from an OS permission callback reaches the flow only after the flow closes (Unity SDK changelog, 4.3.0-beta.1).
Builder side: Actions (
onboarding-actions) gets a Request permission section: the On Tap / On Screen Appear triggers, the After response section, when the request is sent again, advice on which trigger to use, and a warning that lists, per Adapty SDK, what the flow does when the app doesn't answer, and how to keep the flow away from app versions without the handler (an audience on App version (current)). The Action order list and the custom-action use cases now point to it. Respond to purchase outcomes lists Request permission among the actions an outcome can't hold.Ripple:
*-handle-paywall-actions, iOShandle-paywall-actions) gets the same## Handle permission requestssection, plus a one-line pointer under the intro.get-pb-paywalls: thesystemRequestsHandlerrow is rewritten and moved to the end of the table, so that the table follows the Swift argument order ofgetFlowConfiguration.sdk-flows-display(familyhandle-permissions), and thesdk-flows-displayandflow-logicbriefs record the verified per-SDK behavior and the ripple.Review and verification
@adapty/core4.3.3, Flutter to 4.3.1, Unity to 4.3.0-beta.1, KMP to 4.3.0-beta.1, Capacitor to 4.3.0 with@adapty/core4.3.4).dart analyzepassed. The code has changed only in one comment since.tsc --strictagainstreact-native-adapty4.3.10 and@adapty/capacitor4.3.0.node scripts/lint-mdx.mjs: all files OK.node scripts/lint-prose.mjs: candidates reviewed, nothing left that the editor rules flag.npm run check-links-diff: 0 broken. 2 stale anchors, both GitHub README anchors the checker can't see (one on an unchanged line).npm run dev: all seven guides, Actions, Respond to purchase outcomes and the Respond to actions pages render, with the expected headings, callouts and the#request-permissionanchor.Before merge
request-permission-action.webp(the Edit action window of Request permission) and replace the placeholder note inonboarding-actions.createFlowView+present()), Unity and React Native 4.2.x on an Android 13+ device with a clean install. If the flow stays on the screen after the user answers, add a warning to those guides.After publishing
*-handle-permissionsguides (a builder change that follows this PR).🤖 Generated with Claude Code