{{ message }}
Repository navigation
fix(ios): add missing closing backtick in customerSessionClientSecret error message - #2750
Merged
jaynewstrom-stripe merged 1 commit intoOct 19, 2026
Conversation
… error message Signed-off-by: reginaldalfret <reginaldalfret@gmail.com>
jaynewstrom-stripe
approved these changes
Oct 19, 2026
Collaborator
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.

Summary
Fix a missing closing backtick on
`customerSessionClientSecret`in iOS error messages acrossStripeSdkImpl+PaymentSheet.swiftandStripeSdkImpl+Embedded.swift.Motivation
Resolves #2677. In iOS, when both
customerEphemeralKeySecretandcustomerSessionClientSecretare provided, the error string was missing the closing backtick oncustomerSessionClientSecret, resulting in:This caused mismatched markdown formatting, log warnings, and syntax parsing discrepancies. This fix aligns the iOS implementation with Android (
PaymentElementConfig.kt), where the backtick was already correctly placed:Testing
Documentation