Skip to content
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

Android 15 edge-to-edge support on 3DSecure screen #1236

Open
francescocervone opened this issue Dec 10, 2024 · 3 comments
Open

Android 15 edge-to-edge support on 3DSecure screen #1236

francescocervone opened this issue Dec 10, 2024 · 3 comments

Comments

@francescocervone
Copy link

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

  • 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

Screenshot_20241210_122321

@tdchow
Copy link
Collaborator

tdchow commented Dec 10, 2024

Thanks again for reporting! We're tracking this internally.

@francescocervone
Copy link
Author

Hi, just a message to help you understand the priority of this issue from our point of view.

Please keep in mind that apps have 1 year to be compliant with the Target API level requirements for Google Play apps).

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).

Thanks.

@tdchow
Copy link
Collaborator

tdchow commented Dec 18, 2024

Hi @francescocervone - Understood! We'll try to prioritize as soon as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants