-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Postcode field entry issues when using SwiftKey keyboard #8586
Comments
I'm seeing the same issue with SwiftKey and the CustomerSheet with Stripe React Native 0.38.1 (Stripe Android v20.47.3, tested on Samsung S22 Ultra, Android 14.) |
I have the same issue with SwiftKey and the AddressElementActivity (via rememberAddressLauncher). I'm happy to make a new issue, but here are my dependencies. |
We are also receiving customer reports of not being able to enter their UK postcode when adding a card via the CustomerSheet. It seems to be happening to users on various keyboards including the default Gboard but we have only been able to replicate the issue using the Microsoft SwiftKey keyboard, on the CustomerSheet with the postcode text field specifically. With Microsoft SwiftKey behaviours we have seen are when typing a postcode are:
Both of these were observed on a physical Google Pixel 4a 5g device and a Google Pixel 8 pro emulator. Our dependencies are: |
I'm having the same problem with gboard with Android 11 |
Hey @jvanderwee, thanks for reporting this. We're currently investigating a fix. |
hey @tjclawson-stripe , is there any update for this? I didnt see bugfix note on your relase notes yet |
Summary
Postcode field entry does not work as expected when using SwiftKey keyboard - some characters are entered correctly, others are not.
Android version
12+
Impacted devices
Android Pixel 7a
Huawei P30
Installation method
Gradle
Dependency Versions
kotlin: 2.0.0
stripe-android: 20.44.2
Android Gradle Plugin: 8.4.1
Gradle: 8.6
SDK classes
PaymentSheet
Video
SVID_20240605_093257_1.mp4
Other information
The text was updated successfully, but these errors were encountered: