Skip to content

Fix #6680: Bump Target SDK to API Level 36#6712

Open
MohamedMBG wants to merge 1 commit intocommons-app:mainfrom
MohamedMBG:main
Open

Fix #6680: Bump Target SDK to API Level 36#6712
MohamedMBG wants to merge 1 commit intocommons-app:mainfrom
MohamedMBG:main

Conversation

@MohamedMBG
Copy link

Description

This PR addresses issue #6680 by updating the project to compile and target Android API Level 36 doing only the minimal necessary changes.

Changes Made:

  • SDK Bump: Updated compileSdk and targetSdk to 36 in app/build.gradle.kts.
  • Back Navigation Compatibility: Added android:enableOnBackInvokedCallback="false" back-navigation opt-out to AndroidManifest.xml. Since the app relies heavily on legacy onBackPressed() for navigation, this temporarily opts out of the predictive back behavior introduced/enforced in newer SDKs, allowing the app to compile and run normally on SDK 36 without undergoing an immediate, full-scale navigation rewrite.

Scope Confirmation:

  • No unrelated dependencies were upgraded.
  • No unrelated refactoring or code cleanup was performed.
  • No Jetpack Compose migrations were included.
  • Only targeted required fixes for targeting API 36.

Fixes #6680

- Updated `compileSdk` and `targetSdk` to 36 in [app/build.gradle.kts](cci:7://file:///c:/Users/pc/projectw/apps-android-commons/app/build.gradle.kts:0:0-0:0) to meet the new API level requirements.
- Added `android:enableOnBackInvokedCallback="false"` to the `<application>` tag in [AndroidManifest.xml](cci:7://file:///c:/Users/pc/projectw/apps-android-commons/app/src/main/AndroidManifest.xml:0:0-0:0) as a minimal, temporary opt-out for predictive back navigation. This ensures the app's existing legacy `onBackPressed()` handling continues to function correctly without requiring a broad migration at this time.
@RitikaPahwa4444
Copy link
Collaborator

RitikaPahwa4444 commented Mar 7, 2026

#6680 (comment)

Hi @MohamedMBG, @rohit9625 had already expressed his interest to work on this issue. We suggest asking to be assigned instead of raising PRs directly to prevent redundant effort. Although it was a miss on our part to agree but not assign it officially, it was implicit from the discussion that Rohit was working on it. Kindly refrain from skipping the process and comment once to confirm if the issue is up for grab. Thanks for your understanding! 🙂

@neeldoshii
Copy link
Collaborator

Hi @MohamedMBG,

Thanks for contributing, seems like some unit tests are failing. Can you have a look at it once?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bump Target SDK to API Level 36

3 participants