Appcenter-cli: OS X: setup-autocomplete - breaks file tab-completion

[krukow]

System: OS X Sierra 10.12.6, mobile-center version 0.11.0, zsh

Installing setup-autocomplete causes to complete filenames to stop working.

It would be great to get both autocomplete and tab-complete file names.

Example:

➜  espresso ls
total 69864
drwxr-xr-x@  4 krukow  staff   136B Oct 10 14:44 ./
drwx------+ 89 krukow  staff   3.0K Oct 10 15:59 ../
-rw-r--r--@  1 krukow  staff   2.4M Oct 10 14:44 gc-androidTest.apk
-rw-r--r--@  1 krukow  staff    32M Oct 10 14:44 gc.apk

➜  espresso mobile-center test run espresso --app "karl.krukow/Example-espresso" \ 
    --devices any_top_1_device \ 
    --app-path gc.ap<TAB> \ 
    --build-dir ./  \ 
     --debug --test-series master --output --test-parameter test=test

the here does not complete the filename gc.app

here does not complete file.

[christav]

Tab completion only supports bash at this time, not zsh.

[christav]

Reopening now that I understand the behavior better.

[amchew]

Hey @krukow and @RIDE55 , thanks for flagging this out :) We're working on fixing this bug in the next few sprints and will update again when it's completed.

[amchew]

~Hi @krukow! The bug is now fixed in CLI v1.1.14. Please download the new version of the CLI, and test this out. Let us know if you run into any issues. Thank you for the patience!~ There are still issues with the bug fix, my apologies. I'll update again when this is fixed.
cc @AndreyMitsyk @owenniblock

[krukow]

thanks @amchew ! I'm trying to upgrade, but now I run into this?

➜  ~ npm install -g appcenter-cli
npm ERR! Unexpected end of JSON input while parsing near '...^2.1.0","cli-width":"'

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/krukow/.npm/_logs/2018-10-11T19_25_05_779Z-debug.log

not sure if it's a local problem with my setup, but I couldn't find any similar errors via Google search.

Here's the verbose log

392 http fetch GET 200 https://registry.npmjs.org/yazl 15ms (from cache)
393 silly pacote range manifest for xmldom@^0.1.27 fetched in 25ms
394 silly resolveWithNewModule [email protected] checking installable status
395 silly pacote range manifest for xml2js@^0.4.19 fetched in 25ms
396 silly resolveWithNewModule [email protected] checking installable status
397 silly pacote range manifest for which@^1.3.1 fetched in 30ms
398 silly resolveWithNewModule [email protected] checking installable status
399 silly pacote range manifest for wordwrap@^1.0.0 fetched in 29ms
400 silly resolveWithNewModule [email protected] checking installable status
401 silly pacote range manifest for yazl@^2.4.3 fetched in 19ms
402 silly resolveWithNewModule [email protected] checking installable status
403 timing stage:rollbackFailedOptional Completed in 0ms
404 timing stage:runTopLevelLifecycles Completed in 1082ms
405 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '...^2.1.0","cli-width":"'
405 verbose stack     at JSON.parse (<anonymous>)
405 verbose stack     at parseJson (/usr/local/lib/node_modules/npm/node_modules/json-parse-better-errors/index.js:7:17)
405 verbose stack     at consumeBody.call.then.buffer (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/body.js:96:50)
405 verbose stack     at process._tickCallback (internal/process/next_tick.js:68:7)
406 verbose cwd /Users/krukow
407 verbose Darwin 17.7.0
408 verbose argv "/usr/local/Cellar/node/10.8.0/bin/node" "/usr/local/bin/npm" "install" "-g" "appcenter-cli"
409 verbose node v10.8.0
410 verbose npm  v6.4.1
411 error Unexpected end of JSON input while parsing near '...^2.1.0","cli-width":"'
412 verbose exit [ 1, true ]

[owenniblock]

@krukow I can't seem to replicate here. Although it looks like I'm on an older node version to you (not sure how that would lead to a JSON parsing error though!)

Looking at the error - it looks like some sort of weird error in the npm processes. Do you have a different network nearby that you can switch to just in case there's some strange connectivity issue?

[krukow]

Hey @owenniblock I've reproduced it on several networks today. I've also tried to uninstall appcenter-cli. I'm not a node or npm expert, so I'm not sure how to do a completely clean install which also uninstalls dependencies.

[owenniblock]

This suggests maybe an npm cache issue

Suggestion is to try this:

npm cache clean --force

[krukow]

It worked!

➜  ~ npm cache clean --force
npm WARN using --force I sure hope you know what you are doing. (I didn't )

➜  ~ npm install -g appcenter-cli
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
/usr/local/bin/appcenter -> /usr/local/lib/node_modules/appcenter-cli/bin/appcenter.js
+ [email protected]
added 273 packages from 232 contributors in 12.081s

[amchew]

Yess @krukow 👯‍♂️ ! Have a good weekend.