expo: Android internal distribution build fail for sdk45

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)

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

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 2
Comments: 25 (16 by maintainers)

Most upvoted comments

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.

lukmccall on May 4, 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.

wodin on May 15, 2022

expo doctor is what caught it, expo upgrade did not.

I haven’t got the expo doctor output any more right now sorry - we went back to Expo 44 for now due to the Android crash with https://github.com/expo/expo/issues/17478 once it had finally built 😃

nikodunk on May 13, 2022

Ack. I removed an old version of expo-screen-capture (3.2.0) which relied on @unimodules/core@~7.1.1 which was probably causing the above error and it’s now building fine on Android for Managed SDK 45. Probably the newer version of expo-screen-capture would work fine too, but expo upgrade didn’t catch this. I can reproducibly get it to fail/succeed by putting back in and taking it out.

Thank you for the awesome work and sorry to hijack the thread. Good luck everyone!

nikodunk on May 11, 2022

@nikodunk - the update is out - what version of expo-dev-client is installed in your project? the latest is 0.9.5

brentvatne on May 10, 2022

@ramiel1999 as a temporary workaround until a new version of expo-dev-menu is released you can use patch-package.

Basically, put the following file in a patches directory:

patches/expo-dev-menu+0.10.4.patch:

diff --git a/node_modules/expo-dev-menu/CHANGELOG.md b/node_modules/expo-dev-menu/CHANGELOG.md
index c520c5b..f99c169 100644
--- a/node_modules/expo-dev-menu/CHANGELOG.md
+++ b/node_modules/expo-dev-menu/CHANGELOG.md
@@ -8,6 +8,8 @@
 
 ### 🐛 Bug fixes
 
+- Fix `unresolved reference: loadFonts` in the release build on Android. ([#17241](https://github.com/expo/expo/pull/17241) by [@lukmccall](https://github.com/lukmccall))
+
 ### 💡 Others
 
 ## 0.10.4 — 2022-04-26
diff --git a/node_modules/expo-dev-menu/android/src/release/java/expo/modules/devmenu/DevMenuManager.kt b/node_modules/expo-dev-menu/android/src/release/java/expo/modules/devmenu/DevMenuManager.kt
index 6ed5309..1eb2a06 100644
--- a/node_modules/expo-dev-menu/android/src/release/java/expo/modules/devmenu/DevMenuManager.kt
+++ b/node_modules/expo-dev-menu/android/src/release/java/expo/modules/devmenu/DevMenuManager.kt
@@ -7,6 +7,7 @@ import android.view.MotionEvent
 import com.facebook.react.ReactInstanceManager
 import com.facebook.react.ReactNativeHost
 import com.facebook.react.bridge.ReadableMap
+import com.facebook.react.bridge.ReactApplicationContext
 import expo.interfaces.devmenu.DevMenuDelegateInterface
 import expo.interfaces.devmenu.DevMenuManagerInterface
 import expo.interfaces.devmenu.DevMenuPreferencesInterface
@@ -114,6 +115,10 @@ object DevMenuManager : DevMenuManagerInterface {
     throw IllegalStateException(DEV_MENU_IS_NOT_AVAILABLE)
   }
 
+  fun loadFonts(applicationContext: ReactApplicationContext) {
+    throw IllegalStateException(DEV_MENU_IS_NOT_AVAILABLE)
+  }
+
   override val coroutineScope: CoroutineScope
     get() = throw IllegalStateException(DEV_MENU_IS_NOT_AVAILABLE)
 }

Add a post-install script to package.json:

"scripts": {
  "postinstall": "patch-package"
}

Then install patch-package and if you’re using yarn, also install postinstall-postinstall. I’d install these as dev dependencies.

Then you should be able to build.

wodin on May 2, 2022

It gets installed automatically when you install expo-dev-client:

% yarn why expo-dev-menu
yarn why v1.22.18
[1/4] 🤔  Why do we have the module "expo-dev-menu"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "expo-dev-menu@0.10.4"
info Reasons this module exists
   - "expo-dev-client" depends on it
   - Hoisted from "expo-dev-client#expo-dev-menu"
   - Hoisted from "expo-dev-client#expo-dev-launcher#expo-dev-menu"
info Disk size without dependencies: "83.99MB"
info Disk size with unique dependencies: "86.94MB"
info Disk size with transitive dependencies: "92.75MB"
info Number of shared dependencies: 53
✨  Done in 0.30s.

% npm why expo-dev-menu
expo-dev-menu@0.10.4
node_modules/expo-dev-menu
  expo-dev-menu@"0.10.4" from expo-dev-client@0.9.3
  node_modules/expo-dev-client
    expo-dev-client@"~0.9.3" from the root project
  expo-dev-menu@"0.10.4" from expo-dev-launcher@0.11.3
  node_modules/expo-dev-launcher
    expo-dev-launcher@"0.11.3" from expo-dev-client@0.9.3
    node_modules/expo-dev-client
      expo-dev-client@"~0.9.3" from the root project