fix: ensure handleNextActionForSetup passes returnURL parameter on Android #2021
Conversation
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
…droid Resolves parameter mismatch where Android native expects 2 arguments but only received 1, causing "got 3 arguments, expected 4" error. The issue was in handleNextActionForSetup which had platform-specific conditional logic that omitted the returnURL parameter for Android, while both iOS and Android native implementations expect the same parameters. Changes: - Remove platform-specific logic in handleNextActionForSetup - Always pass both setupIntentClientSecret and returnURL parameters - Add NoWebhookSetupScreen example for testing setup flows - Add /setup-without-webhooks server endpoint for setup testing Fixes #1960 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
davidme-stripe
requested review from
charliecruzan-stripe and
a team
as code owners
jaynewstrom-stripe
approved these changes
Jul 29, 2025
Appchoose-GitHub-Bot
pushed a commit
to appchoose/stripe-react-native
that referenced
this pull request
Aug 20, 2025
# [0.51.0](v0.50.0...v0.51.0) (2025-08-20) ### Bug Fixes * ensure handleNextActionForSetup passes returnURL parameter on Android ([stripe#2021](https://github.com/appchoose/stripe-react-native/issues/2021)) ([1593381](1593381)), closes [stripe#1960](https://github.com/appchoose/stripe-react-native/issues/1960) * Make currencyCode optional for setup mode on Android to match iOS behavior ([stripe#2018](https://github.com/appchoose/stripe-react-native/issues/2018)) ([b6bacff](b6bacff)) ### Features * add support for Billie ([stripe#1956](https://github.com/appchoose/stripe-react-native/issues/1956)) ([a644bcb](a644bcb)) * **minor:** release version ([ffca8b0](ffca8b0))
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.
Summary
Fixes parameter mismatch where Android native expects 2 arguments but only received 1, causing "got 3 arguments, expected 4" error.
The issue was in
handleNextActionForSetupwhich had platform-specific conditional logic that omitted thereturnURLparameter for Android, while both iOS and Android native implementations expect the same parameters.Changes
handleNextActionForSetupto consistently pass bothsetupIntentClientSecretandreturnURLparametersNoWebhookSetupScreenexample (under "Finalize setup on the server") for testing setup flows that require next action handling/setup-without-webhooksserver endpoint for setup testingTest plan
handleNextActionForSetupflowsFixes #1960
🤖 Generated with Claude Code