expo: expo-splash-screen 0.20.5 android dev build fails

Summary

Installing the latest expo-splash-screen, 0.20.5, gives the following error when running:

eas build --profile development --platform android --clear-cache

Managed or bare workflow?

managed

What platform(s) does this occur on?

Android

Package versions

“expo”: “49.0.0”, “expo-dev-client”: “~2.4.6”, “expo-splash-screen”: “~0.20.5”

Environment

expo-env-info 1.0.5 environment info: System: OS: Windows 10 10.0.22621 Binaries: Node: 18.15.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD npm: 9.6.1 - C:\Program Files\nodejs\npm.CMD npmPackages: expo: 49.0.0 => 49.0.0 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.72.3 => 0.72.3 react-native-web: ~0.19.6 => 0.19.7 Expo Workflow: managed

Reproducible demo

import * as logger from '../helpers/logger'
import * as SplashScreen from 'expo-splash-screen'
import useAsyncEffect from 'use-async-effect'

const useSplashScreen = () => {
  const hideSplashScreen = async () => {
    try {
      await SplashScreen.hideAsync()
    } catch (err) {
      logger.error('use splash screen hide error', err)
    }
  }

  useAsyncEffect(async () => {
    try {
      await SplashScreen.preventAutoHideAsync()
    } catch (err) {
      logger.error('use splash screen prevent auto hide error', err)
    }
  }, [])

  return { hideSplashScreen }
}

export default useSplashScreen

Stacktrace (if a crash is involved)

Not full stacktrace (There was an error creating your Issue: body is too long (maximum is 65536 characters).)

Task :expo-splash-screen:compileDebugKotlin FAILED

[stderr]

e: file:///home/expo/workingdir/build/node_modules/expo-splash-screen/android/src/main/java/expo/modules/splashscreen/SplashScreenReactActivityLifecycleListener.kt:16:3 ‘onContentChanged’ overrides nothing

[stderr]

FAILURE: Build failed with an exception.

[stderr]

What went wrong:

[stderr]

Execution failed for task ‘:expo-splash-screen:compileDebugKotlin’.

[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 7m 7s

710 actionable tasks: 710 executed

Error: Gradle build failed with unknown error. See logs for the “Run gradlew” phase for more information.

About this issue

Original URL
State: closed
Created a year ago
Reactions: 8
Comments: 31 (5 by maintainers)

Commits related to this issue

Try to fix expo-splash-screen gradlew error See https://github.com/expo/expo/issues/23801 — committed to BloomBooks/BloomReader-Lite by jsubloom 10 months ago

Most upvoted comments

closing this because the solution is to update the expo package to ^49.0.6

brentvatne on Aug 11, 2023

@burhanyilmaz you should upgrade to 49.0.6 this way:

yarn add expo@49.0.6
npx expo install --fix

The second command ensures that you have the right versions of other expo modules. For the splash screen to work, you should have

expo@49.0.6
expo-splash-screen@0.20.5
expo-modules-core@1.5.9
expo-updates@0.18.11

Please let us know if the above fixes your issue.

douglowder on Aug 5, 2023

Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

expo-bot on Aug 3, 2023

same issue, my temp workaround is to downgrade to 0.20.4

dlbears on Aug 2, 2023

@marcus-chr - please share a minimal reproducible example

Sorry for late reply. Everything works fine now!

The mistake was on my side, I still had the following code in package.json which now is removed:

"resolutions": {
  "expo-modules-core": "1.5.5"
},

marcus-chr on Aug 10, 2023

I’m using the following packages:
"expo-splash-screen": "0.20.5",
"expo": "49.0.6",
But still getting the error:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':expo-splash-screen:compileReleaseKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Seems like this was fixed for many others though. Anyone else experiencing issues after running npx expo install --fix?

Are you sure you upgraded as instructed?

npm i -g eas-cli yarn add expo@^49.0.6 npx expo install --fix npx expo-doctor@latest

You could also try to regenerate your .lock file if you’re using yarn.

reft on Aug 7, 2023

Upgrading expo to 49.0.6 fixes the issue for me

can you share this command (npx expo-env-info )log? may be related to some environment. after the upgrading, it didn’t work

expo-env-info 1.0.5 environment info: System: OS: Windows 10 10.0.22621 Binaries: Node: 18.16.1 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD SDKs: Android SDK: API Levels: 29, 30, 31, 33 Build Tools: 30.0.3, 33.0.0 System Images: android-30 | Google Play Intel x86 Atom, android-31 | Google APIs Intel x86 Atom_64, android-31 | Google Play Intel x86 Atom_64, android-33 | Google APIs Intel x86_64 Atom IDEs: Android Studio: AI-213.7172.25.2113.9123335 npmPackages: expo: ^49.0.6 => 49.0.6 react: 18.2.0 => 18.2.0 react-native: 0.72.3 => 0.72.3 Expo Workflow: bare

manamelacedric on Aug 4, 2023

“expo-splash-screen”: “~0.20.5”

Can you try this repo? There is no issue in development mode. After release update(eas update), splash screen is showing as white. https://github.com/burhanyilmaz/expo-splash-screen-eas-update

burhanyilmaz on Aug 3, 2023

+1 and can confirm workaround is to downgrade to 0.20.4

I removed expo-splash-screen entirely and still seeing this issue

Alekzv9 on Aug 2, 2023