Joshua Yoes

**What's Left:** - [x] More clear error message for for unexpected command output - [x] More robust validation for `yarn list` command output

These changes should be implemented in gluegun instead of ignite: https://github.com/infinitered/gluegun/issues/762

I was able to log the value of the output passed to [`packager.list`](https://github.com/infinitered/ignite/blob/master/src/tools/packager.ts#L167) on my machine, it appears the warn is getting prepended to the JSON output, causing it throw:...

@vijjusri14 8.0.0-beta.7 is out now with a PR that should resolve this! You can try again with `npx ignite-cli@next new` I'm going to close this issue for now. But if...

Is it possible this has to do with Xcode using an old workspace from a previous PizzaApp?

@jamonholmgren do we want to leave this issue open? This seems like an upstream issue to me

I did just run into this trying to do Detox tests. Perhaps there is a way we could detect in Ignite whether the default simulator is available and print a...

@frankcalise I like that solution, it appears we may be able to install simulators for Xcode. So perhaps the following logic may be good to add somewhere in the `new`...

> add this "iphone13": "npx react-native run-ios --simulator=\"iPhone 13 Pro\"", in your script in package.json file and then run "npm run iphone13" @Gurminder-Kaler I'm not sure that will solve what...

Since this isn't entirely related to Ignite, and our default workflow out of the box, I'm going to close this issue for now. However, in the future, we are working...