`npx create-react-native-dapp` errors out

• 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 npx create-react-native-dapp errors out:

[21:20:44] Error: Problems validating fields in app.json. See https://docs.expo.io/versions/v40.0.0/workflow/configuration/
[21:20:44]  • is missing required property 'name'.
[21:20:44]  • is missing required property 'slug'.
Warning! Your git working tree is dirty.
It's recommended to commit all your changes before proceeding,
so you can revert the changes made by this command if necessary.

[21:20:44] Input is required, but Expo CLI is in non-interactive mode.
Please specify eject method (bare, expokit) with the --eject-method option.
(node:9459) UnhandledPromiseRejectionWarning: Error: Command failed: cd /Users/foobar/.../my-react-dapp; expo eject --non-interactive;
    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at ejectExpoProject (/Users/collinglass/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/buidler/index.js:61:21)
    at Object.create (/Users/collinglass/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/buidler/index.js:720:5)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /Users/foobar/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/cli/index.js:115:33
(node:9459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:9459) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
111

• 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.)

Using nvm on mac, tried with node v12.20.0 and v13.12.0, same error.

[collinglass]

Yes I am, just reverified that

[cawfree]

@collinglass Great to hear you found a solution! Best of luck.