withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.05k stars 63 forks source link

Three errors after updating to v1.0.56 #1075

Closed GamaG27 closed 2 years ago

GamaG27 commented 2 years ago

Description:

Please include a detailed description of the issue (and an image or screen recording, if applicable)

Screenshot 2022-03-10 at 03 45 52

error: Found argument 'completion' which wasn't expected, or isn't valid in this context

USAGE: fig [SUBCOMMAND]

For more information try --help

❯ fig doctor

✘ Figterm socket: Figterm socket did not read buffer correctly: "\Testing figterm...\n"

✘ Doctor found errors. Please fix them and try again

tried using settings the this appears

Screenshot 2022-03-10 at 03 48 42

what do i do ?

Details:

macOS Fig Shell
12.2.1 Version 1.0.56 (B401) /bin/zsh
fig diagnostic

Version 1.0.56 (B401) [British] 
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: false
Settings.json: true
CLI installed: true
CLI tool path: /Users/occ/.fig/bin/fig
Accessibility: true
SSH Integration: false
Tmux Integration: false
iTerm Integration: true [Authenticated]
Hyper Integration: true
VSCode Integration: true
Docker Integration: false
Symlinked dotfiles: false
Only insert on tab: false
UNIX Socket Exists: true
Installation Script: true
PseudoTerminal Path: 
SecureKeyboardInput: false
SecureKeyboardProcess: 
Current active process: ??? (???) - ???
Current terminal session: ???
Current working directory: ???
Current window identifier: ???

oorzc commented 2 years ago

Mac 10.14.6 cannot be used

GamaG27 commented 2 years ago

ok.. ? there seams to be a misunderstanding i am using macOS 12.2.1 .

mschrage commented 2 years ago

@GamaG27 thanks for reporting this!

error: Found argument 'completion' which wasn't expected, or isn't valid in this context

We've removed this subcommand from the fig CLI. Search your zshrc/zprofile for occurrences of fig completion and remove it.

✘ Figterm socket: Figterm socket did not read buffer correctly: "\Testing figterm...\n"

Try opening a new terminal session and running fig doctor. Let me know if you still see the same warning and we can get @grant0417 involved.

"Something went wrong :("

This was related to an issue on our backend. It has since been resolved. You should be able to edit settings as usual.

GamaG27 commented 2 years ago

I followed everything you said and it was fixed ! Thank you very much!