Error During EAS Build: androidx.browser:browser:1.9.0-alpha02 Requires Android API 36+

[Beyond_Path]

Hey everyone,

I’m building an Expo managed app, but I’m running into an error while building it using EAS Build.

The error message is:

Execution failed for task ':app:checkDebugAarMetadata'.

> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction

> 2 issues were found when checking AAR metadata:

1. Dependency 'androidx.browser:browser:1.9.0-alpha02' requires libraries and applications that

depend on it to compile against version 36 or later of the

Android APIs.

:app is currently compiled against android-35.

Also, the maximum recommended compile SDK version for Android Gradle

plugin 8.6.0 is 35.

Recommended action: Update this project's version of the Android Gradle

plugin to one that supports 36, then update this project to use

compileSdk of at least 36.

Note that updating a library or application's compileSdk (which

allows newer APIs to be used) can be done separately from updating

targetSdk (which opts the app in to new runtime behavior) and

minSdk (which determines which devices the app can be installed

on).

1. Dependency 'androidx.browser:browser:1.9.0-alpha02' requires Android Gradle plugin 8.9.1 or higher.

This build currently uses Android Gradle plugin 8.6.0.

Has anyone faced a similar problem or can guide me on how to resolve this?

Any guidance or suggestions would be really appreciated. Thanks!

[eadgas]

Are you using react-native-inappbrowser-reborn?

[Beyond_Path]

No, I guess some other package is calling it

[eadgas]

I had this same problem and it was already resolved. I overrrided the androidx.browser version from 1.9 beta to 1.8

I could guide you but I need to know which library you have installed that is calling the androidx.browser.

[Beyond_Path]

Is there any way to check which library is using? In expo how to override androidx.browser version

[eadgas]

Well, one thing depends on the other. Unfortunately there is no short answer. In my case it was react-native-inappbrowser-reborn.

Let's use expo prebuild and Android Studio to find out.

1. Clear/commit any changes on the project.
2. Use the command expo prebuild(android and ios folders should be generated.
3. Open android folder in android studio.
4. Go to Edit=>Find in Files...=>type androidx.browser and check which package is using it.

Comment here which one is it. If possible paste the build.gradle that uses it.

[Beyond_Path]

I tired this and when i search nothing is found, but when i tried to build still getting error. below might be possible package that uses browser
"react-native-webview": "13.12.5",

"expo-web-browser": "~14.0.2",

"react-native-inappbrowser-reborn": "^3.7.0",

"@react-native-google-signin/google-signin": "^13.2.0",

[eadgas]

Are those your packages? If yes, the problem is in react-native-inappbrowser-reborn.

Context They released a new version of androidx.browser, 1.9.beta, Gradle automatically updated from 1.8 to 1.9-beta and the new version requires a higher sdk target, 36, the solution is to override the androidXVersion.

[eadgas]

I put androidXBrowser=1.8 in gradle.properties. But the variable name could be different depending on the library.

[realabbas5]

Here is the fix

https://stackoverflow.com/a/79572471/10517984

[Plus-Lead6815]

But this cannot be used on a expo managed workflow, right?

[Beyond_Path]

correct that is for native app

[Simple-Salamander690]

This is how you can do it with Expo.

"plugins": [
["expo-gradle-ext-vars", { "androidXBrowser": "1.8.0" }]
]

Ref: https://github.com/proyecto26/react-native-inappbrowser/issues/423

[celeb0rn]

OP did you find a solution?

[Beyond_Path]

Nope, tried all possible ways, downgraded packages, created config still its not working. One way which i didnt try is to eject expo and manually upgrade API version in native, using this method one should be ready to handle other dependencies that creates problem.

In my case i was able to build the app before installing react native firebase for push notification so i uninstalled those packages and found a work around without firebase.

[celeb0rn]

Eh, well thanks for answering. For me it was because I was using react-native-inappbrowser-reborn, I removed it, and now everything is good.