You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 3DSecure doesn't correctly support the Android 15 edge to edge enforcement.
We depend on Braintree 4.x and we were trying to increase our target SDK to 35 (Android 15), but we found out about this behavior.
So, since the 5.x declares Android 15 support, we decided to upgrade to Braintree 5 first.
Unfortunately though, I tried the demo version on the main's HEAD, which at the time of writing is this commit, and that screen still draws incorrectly behind the system bars.
To reproduce
Run a 3DSecure verification on an app targeting Android API 35
The 3DSecure screen is drawn behind the system bars incorrectly
Expected behavior
All Braintree screens handle window insets correctly in all Android versions, 15 included.
Screenshots
The text was updated successfully, but these errors were encountered:
Typically, that would be August 2025, but given that Google changed the frequency and dates of new SDK releases (blog), apps will need to start integrating with Android 16 too starting from Q2 2025 (I guess around April 2025).
Braintree SDK Version
5.2.0
Environment
Both
Android Version & Device
Android 15
Braintree dependencies
I tried the demo on the main's HEAD, which at the time of writing is this commit.
Describe the bug
Android 15 has forced edge to edge automatically for all activities.
The 3DSecure doesn't correctly support the Android 15 edge to edge enforcement.
We depend on Braintree 4.x and we were trying to increase our target SDK to 35 (Android 15), but we found out about this behavior.
So, since the 5.x declares Android 15 support, we decided to upgrade to Braintree 5 first.
Unfortunately though, I tried the demo version on the main's HEAD, which at the time of writing is this commit, and that screen still draws incorrectly behind the system bars.
To reproduce
Expected behavior
Screenshots
The text was updated successfully, but these errors were encountered: