Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

Expo app never leaves the splash screen

ErrorApp shows the splash screen forever and no error appears

Short answer

After SplashScreen.preventAutoHideAsync() the splash stays until you hide it yourself. The app stays stuck when hide is never called, or when the ready flag is only set after async work succeeds and that work throws or never finishes. Hide it from a flag set in a finally block.

  • Applies to Expo SDK 5x, expo-splash-screen, React Native 0.7x
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Search the project for every call to the splash screen module and see where preventAutoHideAsync and hide are used.

    grep -rn "SplashScreen\." app src App.* --include=*.tsx --include=*.js
  2. 2Match what you see, then jump to its fix

    1. 1The grep shows preventAutoHideAsync and no hideAsync or hidepreventAutoHideAsync is called but hide is never reachedFix
    2. 2A fetch, font load or storage read runs before setIsReady(true)The ready flag is set only when async startup work succeedsFix
    3. 3The splash looks different or sticks only in developmentThe check was made in Expo Go or a dev buildFix

What does the error look like?

  • App shows the splash screen forever and no error appears

Cause 1 of 3

preventAutoHideAsync is called but hide is never reached

1Check

preventAutoHideAsync keeps the splash visible until hideAsync is called.

grep -rn "hideAsync\|SplashScreen.hide" app src App.* --include=*.tsx --include=*.js

2Fix

Call preventAutoHideAsync at global scope, outside any component, and hide the splash from an effect once the app is ready.

SplashScreen.preventAutoHideAsync();

useEffect(() => {
  if (isReady) {
    SplashScreen.hideAsync();
  }
}, [isReady]);

3Verify

Restart the app. The splash disappears when isReady becomes true.

npx expo start --clear

Confirmed by docs.expo.dev

Did this fix it?

Cause 2 of 3

The ready flag is set only when async startup work succeeds

1Check

If that work throws or hangs, isReady stays false and the splash never hides.

grep -rn "setIsReady\|setReady\|setAppIsReady" app src App.* --include=*.tsx --include=*.js

2Fix

Set the flag in a finally block so a failure still ends the splash, and log the error.

useEffect(() => {
  async function prepare() {
    try {
      // load fonts, read storage
    } catch (e) {
      console.warn(e);
    } finally {
      setIsReady(true);
    }
  }
  prepare();
}, []);

3Verify

Break the async step on purpose (go offline). The app should still leave the splash.

npx expo start --clear

Confirmed by docs.expo.dev

Did this fix it?

Cause 3 of 3

The check was made in Expo Go or a dev build

1Check

Expo notes that Expo Go and development builds do not fully reproduce the splash screen.

npx expo --version

2Fix

Test the behaviour on a release build before changing code.

npx expo run:ios --configuration Release

3Verify

The release build leaves the splash when the app is ready.

npx expo run:ios --configuration Release

Confirmed by docs.expo.dev

Did this fix it?

How do I stop it coming back?

  • Call preventAutoHideAsync at the top of the file, not inside components or hooks.
  • Always set the ready flag in finally.
  • Hide the splash as soon as content is ready, to avoid a blank screen.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.