Ignite: I don't have any screen (except launch Screen with Rocket icon) when I create ignite new myapp

[boyinfotronics]

I don't have any screen (except launch Screen with Rocket icon) when I create ignite new myapp
I choose all yes on generate CLI Screen (already choose dev mode)
But i don't have "OPEN DEVSCREENS" button
like a in this vdo
(Building a React Native App in Under 15 Minutes)

[GantMan]

2 questions to help us here:

did you say YES to dev screens during the setup process?

Do you have dev screens in your ./ignite folder?

[boyinfotronics]

Yes . I choose yes on setup process
I do it repeat 3 time . In 3 project but it's all same thing like that .

I need more screen like ignite 2 tutorial

[GantMan]

It looks like you might have said "NO" to development screens.

ignite add dev-screens to fix.

[ljuborados]

I'm running this under Windows 10, same error, I DID SELECT Yes on the setup process, twice.
Worked after ignite add dev-screens so thanks!

[caxco93]

cool i was about to post the same thing. it apparently ignores YES on windows
Apparently its ignoring every package you select on windows. After adding dev-screens manually (having selected YES on the creation CLI to every packge) and going into the Plugin Examples section, theres no Animatables, i18n or Vector Icons either.

[mathieuhasum]

Same issue here on Windows 10.
Tried Powershell as well as the old console and even Git Bash.
Had to install manually.

[akuma06]

Same issue as @mathieuhasum

[GantMan]

Everyone on windows eh? Need to boot up my VM to fix this one.

[ljuborados]

Yeah well, still saving up for a Mac..

[anderm]

Same issue, I see a few errors during the setup process:

 🔥 igniting app ReactHpm
√ using the Infinite Red boilerplate v2 (code name 'Andross')
√ added React Native 0.42.3 in 57.24s
√ added ignite-ir-boilerplate in 10.77s
The filename, directory name, or volume label syntax is incorrect.
/ ▸ linking
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.

√ configured git
√ ignited ReactHpm in 70.84s

[mathieuhasum]

Haha good luck with that @GantMan :)

[tugrulcan]

Error after running ignite add dev-screens

@GantMan Maybe this is related with problem?
This suggestion worked for me.

[caxco93]

@tugrulcan i had that too. simply close the react packager and run that again. it should work

[skellock]

Anyone still having this issue?

[smartcris]

I got this bug in windows 8.1 too....and my editors changes are not reflected on the device.

2.0.0-rc.2

after manually installing the dev-screens I had to rebuild 2 times the package and now it seems to work

[endru-ralali]

Same here. I use Windows 10.
At the end, I compiled manually from the source code on GitHub using yarn, and... it works.
The "Open DevScreens" button and all the demo appear.

The ignite binary cannot be run directly. So, need to use node:
node ignite new MyApp

[RobertoE91]

On the setup process select with SPACE then ENTER

[nosizejosh]

just started with ignite and I am facing same issues. Run the setup twice, chose yes for dev screens but none appeared. * windows 10.

[GantMan]

But when you add them after the fact it works?

Please verify that.

I might have to kick open my windows VM and check. Though it would be epic if @kevinvangelder could help here.

[nosizejosh]

@GantMan it works if you add manually, shut down packager and re-run. I have only tried dev-screens.
NB: The SPACE method suggested by @RobertoE91 doesnt work, at least not for me.

Edits, worked for only one out of two app so far. The other just wont start. keep getting "cannot install on device" after manually adding the dev-screens. tried everything form gradlew clean to reset cache. Now trying another install.

Edits* running ignite new MyApp --maxx dint work either. Got "The filename, directory name, or volume label syntax is incorrect." warnings

[anshchauhan]

I'm having same issue in mac. Any resolution?

[GantMan]

@anshchauhan - when you install dev-screens by hand does it show up?

Also, what OS are you on?

[anshchauhan]

@GantMan I was on Sierra and it was not showing even when I installed from hand. I found the solution though.

When I created a new app and ran it, I was getting this error "unable to load script from assets index.android.bundle"

After I applied the given solution here:
https://stackoverflow.com/questions/44446523/unable-to-load-script-from-assets-index-android-bundle-on-windows
the app was opening but dev screens were not showing.

Then I created a new app and I removed --dev false option from the given solution and I got my screens.

[puzpuz]

Windows 10 here, and experience same issue, say YES to all options but:

• no dev screen
• react-native-vector-icons, i18n, and animatable not installed ( Not linked and not installed)

EDIT: manually install dev screen as Gant suggested is working. For all three library, needs to install again manually :(

[Pixelartist]

Hello there,

same issue for me.

System
platform win32 --> windows 10
arch x64
cpu 8 cores Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
directory H:\projects\myproject

JavaScript
node 8.5.0 G:\Program Files\nodejs\node.EXE
npm 5.5.1 G:\Program Files\nodejs\npm.CMD
yarn 1.0.2 G:\Program Files (x86)\Yarn\bin\yarn.CMD

React Native
react-native-cli 2.0.1
app rn version 0.47.2

Ignite
ignite 2.0.0 C:\Users\bioth\AppData\Roaming\npmignite.CMD

Android
java - C:\ProgramData\Oracle\Java\javapath\java.EXE
android home - G:\androidsdk

After installing plugins manually it works.

[cihadturhan]

Lol, I already started my project and didn't know there were more screens haha. I was wondering why all these github services and fixtures exist. Again, windows 10 here.

[GantMan]

@kevinvangelder - you're our only hope! :D

[effexts]

I was having the same issue, but on mac... using latest version of node. (v10.11.0 i think).

Switching to node 7.6.0 finally added the DevScreens files in the ignite folder.

I haven't tested other versions of node.

[jamonholmgren]

We are planning to re-address this soon!

[morgandonze]

Hey everyone thank you for your patience! I've discovered the root cause and I'll make a PR asap!

[morgandonze]

This is the workaround I used to get dev-screens to show up on Windows, unfortunately
it is NO LONGER WORKING for me today. I am stumped, and I'm putting this issue aside until I get some outside help. However, I will still post this. The inconsistency
must mean that I made some other changes that I didn't realize were necessary. (cc @jamonholmgren )

_[Note: I will actively seek someone else to help]_

Clone ignite-dev-screens to inside /Users/<your name>/.ignite/overrides/

Clone ignite to a directory /path/to/my/ignite

Change ignite to /path/to/my/ignite/bin/ignite on this line:

https://github.com/infinitered/ignite-ir-boilerplate-andross/blob/master/boilerplate.js#L178

then create an app normally

[jamonholmgren]

This should be fixed with the latest Ignite CLI and Ignite Andross 3.0.2.

[jazst21]

It looks like you might have said "NO" to development screens.

ignite add dev-screens to fix.

not working on mac mojave. perhaps need to rollback to node 7? ignite doctor :
System
platform darwin
arch x64
cpu 4 cores Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz
directory /Users/pugar/GitHub/ignite1

JavaScript
node 10.7.0 /usr/local/bin/node
npm 6.4.1 /usr/local/bin/npm
yarn 1.12.3 /usr/local/bin/yarn

React Native
react-native-cli 2.0.1
app rn version 0.57.7

Ignite
ignite 2.1.8 /usr/local/bin/ignite
boilerplate ignite-andross

Android
java 1.8.0_191 /usr/bin/java
android home - /Users/pugar/android-sdks

iOS
xcode 7.0

[jamonholmgren]

@jazst21 Can you open a new issue and provide more information that will let us easily debug this?