App crashes on splash screen
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devtools, mobile-dev
Research direction
Start with the DevTools plugin setup in index.tsx and the useDevToolsPluginClient error shown in the adb log; reproduce the issue in an Expo 50 development APK, both with and without the react-navigation plugin. Done means the development build proceeds past the splash screen without the reported client-setup error.
Written by the indexing model from the issue text.
Description
Thanks for the great work for Expo 50.
I enabled the DevTools plugin for react-navigation in my index.tsx file:
The app works fine with the dev server locally. But When I build it and try the development build (apk file on my device or emulator), the app hangs at the Splash screen. And this is the adb log from the console:
01-20 14:00:03.693 4767 4812 I cr_LibraryLoader: Successfully loaded native library
01-20 14:00:03.693 4767 4812 I cr_CachingUmaRecorder: Flushed 8 samples from 8 histograms.
01-20 14:00:03.699 4767 4811 E ReactNativeJS: Error: Failed to setup client from useDevToolsPluginClient: [object Object]
01-20 14:00:03.699 4767 4811 E ReactNativeJS:
01-20 14:00:03.699 4767 4811 E ReactNativeJS: This error is located at:
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in Index
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in RCTView
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in Unknown
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in RCTView
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in Unknown
01-20 14:00:03.699 4767 4811 E ReactNativeJS: in AppContainer, js engine: hermes
01-20 14:00:03.701 402 402 I RanchuHwc: validateDisplay: layer 66 CompositionType 1, fallback to client
01-20 14:00:03.701 402 402 I RanchuHwc: validateDisplay: layer 65 CompositionType 1, fallback to client
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: Error: Failed to setup client from useDevToolsPluginClient: [object Object]
01-20 14:00:03.702 4767 4812 E unknown:ReactNative:
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: This error is located at:
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in Index
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in RCTView
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in Unknown
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in RCTView
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in Unknown
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: in AppContainer, js engine: hermes, stack:
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: ?anon_0_@1:3334106
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: asyncGeneratorStep@1:148149
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: _throw@1:148451
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: tryCallOne@53:15
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: anonymous@139:26
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: anonymous@1:321582
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: _callTimer@1:320581
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: _callReactNativeMicrotasksPass@1:320725
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: callReactNativeMicrotasks@1:322659
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: __callReactNativeMicrotasks@1:163417
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: anonymous@1:162552
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: __guard@1:163291
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: flushedQueue@1:162463
01-20 14:00:03.702 4767 4812 E unknown:ReactNative: callFunctionReturnFlushedQueue@1:162319
Versions
expo: 50.0.2
react-navigation/native: 6.1.9
react-navigation/stack: 6.3.20
react-navigation/drawer: 6.6.6
Not sure if this is related to this plugin or react-router. Thanks.
- Dominant language
- TypeScript
- Stars
- 250
- Forks
- 37
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from expo/dev-plugins
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
expo/dev-plugins#65 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
expo/dev-plugins#58 · 2 comments · 1 reaction ·
-
expo-router devtoolOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
expo/dev-plugins#47 · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
expo/dev-plugins#45 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
expo/dev-plugins#44 · 6 comments · 3 reactions ·
All issues in expo/dev-plugins
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day