question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Android internal distribution build fail for sdk45

See original GitHub issue

Summary

I am trying to build an android preview using eas build -p android --profile preview, however, the build fails. The build fails in “run gradlew”. Here is the last thing that was outputted:

> Task :expo-manifests:compileReleaseKotlin

w: /home/expo/workingdir/build/node_modules/expo-manifests/android/src/main/java/expo/modules/manifests/core/BaseLegacyManifest.kt: (10, 86): 'getLegacyID(): String' is deprecated. Prefer scopeKey or projectId depending on use case

w: /home/expo/workingdir/build/node_modules/expo-manifests/android/src/main/java/expo/modules/manifests/core/BaseLegacyManifest.kt: (12, 72): 'getStableLegacyID(): String?' is deprecated. Overrides deprecated member in 'expo.modules.manifests.core.Manifest'. Prefer scopeKey or projectId depending on use case

w: /home/expo/workingdir/build/node_modules/expo-manifests/android/src/main/java/expo/modules/manifests/core/Manifest.kt: (28, 12): 'getRawJson(): JSONObject' is deprecated. Prefer to use specific field getters

> Task :expo-manifests:javaPreCompileRelease

> Task :expo-manifests:compileReleaseJavaWithJavac

> Task :expo-manifests:bundleLibCompileToJarRelease

> Task :expo-dev-menu:compileReleaseKotlin

[stderr] e: /home/expo/workingdir/build/node_modules/expo-dev-menu/android/src/main/java/expo/modules/devmenu/modules/internals/DevMenuInternalFontManagerModule.kt: (11, 20): Unresolved reference: loadFonts

> Task :expo-dev-menu:compileReleaseKotlin FAILED

[stderr] FAILURE: Build failed with an exception.

[stderr] * What went wrong:

[stderr] Execution failed for task ':expo-dev-menu:compileReleaseKotlin'.

[stderr] > A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction

[stderr] > Compilation error. See log for more details

[stderr] * Try:

[stderr] > Run with --stacktrace option to get the stack trace.

[stderr] > Run with --info or --debug option to get more log output.

[stderr] > Run with --scan to get full insights.

[stderr] * Get more help at https://help.gradle.org

[stderr] BUILD FAILED in 12m 17s

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

45

Environment

expo-env-info 1.0.3 environment info: System: OS: Windows 10 10.0.19044 Binaries: Node: 16.14.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD npmPackages: expo: ^45.0.0-beta.8 => 45.0.0-beta.8 react: 17.0.2 => 17.0.2 react-dom: 17.0.2 => 17.0.2 react-native: 0.68.1 => 0.68.1 react-native-web: 0.17.1 => 0.17.1 Expo Workflow: managed

Reproducible demo

It is a full on project. I am not sure I am able to provide a small reproducible. I hope the log from “run gradlew” is enough

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:25 (16 by maintainers)

github_iconTop GitHub Comments

3reactions
lukmccallcommented, May 4, 2022

A new version of the dev menu should be available today or tomorrow. I’m really sorry that you have to wait for that patch.

1reaction
wodincommented, May 15, 2022

Maybe in that case, expo upgrade does not also upgrade the dependencies?

No, it does update Expo dependencies when you upgrade to a new SDK and prints out a list of the upgraded dependencies. But I think there were some things that were updated after the initial SDK 45 release to fix bugs, so if you ran the upgrade again after those fixes it would have updated to the fixed versions. I suspect that’s what happened.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expo 45 build fail on Android with EAS
I'm desperate to get this build out since upgrading to SDK 45 finally fixed flat list bugs which caused my app unusable. Any...
Read more >
EAS build error when doing internal distribution build Android
I can't locate the issue of why my build is failing. The project is fairly empty for now as I'm just trying to...
Read more >
gradle build failed with unknown error. see logs for the "run ...
1277 [stderr] > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2ProcessResourcesRunnable 1278 [stderr] > Android resource ...
Read more >
expo sdk 43
Run expo build:ios or expo build:android when you are ready to submit ... (internal distribution) and this integrity message appears.
Read more >
Expo - Datadog Docs
Datadog recommends using Expo SDK 45 as a minimum version; previous versions may require manual steps. Setup. To install with NPM, run: npm...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found