Blank screen for new app, and no hot-reloading

[Ibcs16]

• I'm submitting a ...
  [X ] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary
  I don't why, but Ive tried to setup a project many times now, and all I get is a blank screen. It also never hot-reload when I change something in App file. Dont have a clue why!?

• Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

• Runnpx create-react-native-dapp command

• Run yarn start
  Gives a blank screen and nothing else

[cawfree]

Hello, this looks like a duplicate of #17, so I'm going to close this issue in the hope that we can continue discussion there.

[blixit]

Hello,
I allow myself to comment this closed thread because I think this error is not #17 related. I hope my analysis is right if not I apologize for adding confusion.

I also add this comment because my resolution step is reproductible. Fixing the warnings about the version of @react-native-async-storage/async-storage and react-native-get-random-values helped to resolve the problem.

Local Context:

• MacOS 12
• Xcode 13
• node 12 (by the way, it should be explicit in the readme)
• yarn 1.22.10
• expo 4.13.0

After installation, running expo start led me to a blank screen on my iOS simulator running expoGo:

iOS 15 simulator	expo start warning

I first ignored the warnings by trying many other solutions like ejecting Expo. I felt I was leaving the solution behind me. Then I tried to fix the warnings.

I upgraded all the libraries. It turns out that using the [email protected] introduced a conflict with WallectConnect internal configuration. So I decided to rollback to 9.6.4 but keeping upgraded the versions of @react-native-async-storage/async-storage and react-native-get-random-values.

That's the way I fixed up the white screen issue

[dparker2]

seconded, upgrading both react-native-get-random-values and @react-native-async-storage/async-storage fixes this issue for me too

[demayaa]

@blixit thanks bro