cap init prompt issues
See original GitHub issueDescription of the problem: When initializing capacitor in a newly created CRA, it hangs in the 2nd step when it asks for App Package ID.
Affected platform
- Android
- iOS
- electron
- web
OS of the development machine
- Windows
- macOS 10.14.5
- linux
Other information:
node version: v12.2.0 v10.15.1 v8.15.1
npm version: 6.9.0
Steps to reproduce:
$ npx create-react-app test
$ cd test
$ npm i -S @capacitor/core @capacitor/cli
$ npx cap init
? App name (App) <ENTER>
? App Package ID (in Java package format, no dashes) (com.example.app) <ENTER>
When it asks for App Package ID it does not proceed by hitting enter or CTRL C.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Stuck at capacitor init - Ionic Forum
I wont go very far because the cap add task never finishes. After this last log, nothing happens for minutes (I waited about...
Read more >cant complete ionic capacitor add android command
I got this issue while adding the android platform in the Ionic Capacitor app using the below command. $ ionic capacitor add android....
Read more >Troubleshooting - SAP Capire
The issue is discussed in detail in this blog post by Adam Crowder. One solution is to increase the server's keepAliveTimeout to above...
Read more >FAQs for CAPs :: Support - Certiport - Pearson VUE
Technical issues. We are experiencing issues with the Autodesk (ACU) toolbar, how do we correct it?
Read more >Overview of community-acquired pneumonia in adults
Progression of the initial infection – For some patients, CAP can lead to overwhelming infection despite appropriate antibiotic treatment. In ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this is a bug in inquirer 6.4.0 that was released today, will pin the dependency to 6.3.1
I’ve been able to reproduce in a different computer, will try to figure out whats going on.
As workaround you can use
npx cap init appName com.app.id