Hello, I ran into an error while using eas build --platform android. I was able to build an apk using expo build android --type apk but eas fails with an error. Build failed: Gradle build failed with unknown error.
Please help me to identify the exact issue. Thanks.
Note: Some input files use unchecked or unsafe operations.
Note: /build/workingdir/build/node_modules/expo-app-auth/android/src/main/java/expo/modules/appauth/AppAuthModule.java uses unchecked or unsafe operations.
[stderr] Note: /build/workingdir/build/node_modules/expo-application/android/src/main/java/expo/modules/application/ApplicationModule.java uses or overrides a deprecated API.
[stderr] `Note: /build/workingdir/build/node_modules/expo-constants/android/src/main/java/expo/modules/constants/ConstantsService.java uses or overrides a deprecated API.`
[stderr] Note: /build/workingdir/build/node_modules/expo-file-system/android/src/main/java/expo/modules/filesystem/FileSystemModule.java uses or overrides a deprecated API.
Hey @charliecruzan I did some digging and it appears as more native dependencies are added to a project, it may bump it over the 64k method limit on the Android build system. The firebase in my project might be putting my methods right over the 64k. Also, I found out that this can be potentially solved by Enabling Multidex (to be true).
That being said, is there a way to Enable Multidex in Expo without ejecting to bare workflow?
Yeah this could be done with a config plugin for sure- there’s a mod for each of these in the default mods list. As for examples- the expo/expo repo is a great place to search for those mod names (like projectBuildGradle) to find existing plugins for our expo libraries
Editing MainApplication is pretty tough I think…and we’re currently trying to make it so that you don’t need to directly edit this file but instead just extend some interface in your MainApplication. However- the expo-dev-client does this now: expo/withDevLauncher.ts at master · expo/expo · GitHub