Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fig not working despite all fig doctor checks passing #2885

Open
3 tasks done
Tom-Ainsworth opened this issue Jan 25, 2024 · 47 comments
Open
3 tasks done

Fig not working despite all fig doctor checks passing #2885

Tom-Ainsworth opened this issue Jan 25, 2024 · 47 comments
Labels
type:bug Something isn't working

Comments

@Tom-Ainsworth
Copy link

Checks

  • I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
  • I have run fig doctor in the affected terminal session
  • I have run fig restart and replicated the issue again

Operating system

macOS 14.2.1 (23C71)

Expected behaviour

Auto complete/prompts should appear

Actual behaviour

No autocomplete/prompts, and an extra cursor appears either above or below my current line, depending on the terminal (below in vs code, above in macOS terminal)

Steps to reproduce

I've run fig doctor and fig restart
uninstalled fig from the fig dashboard
reinstalled fig
setup shell integrations
reran fig doctor/restart
closed the terminal window and opened a new one, then reran the commands

still no luck

Environment

fig-details:
  - 2.17.0
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Apple M1
  - cores: 8
  - mem: 16.00 GB
os-info:
  - macOS 14.2.1 (23C71)
environment:
  - shell: /bin/zsh
  - terminal: vscode
  - cwd: /Users/tomainsworth/Code/otsuka-hcp-portal
  - exe-path: /Users/tomainsworth/.fig/bin/fig
  - install-method: unknown
  - env-vars:
    - FIGTERM_SESSION_ID: 16f3f357-ea0a-4a2f-acbd-62499de4d214
    - FIG_PID: 18054
    - FIG_SET_PARENT: 16f3f357-ea0a-4a2f-acbd-62499de4d214
    - FIG_SET_PARENT_CHECK: 1
    - FIG_TERM: 2.17.0
    - PATH: /Users/tomainsworth/.nvm/versions/node/v18.16.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Users/tomainsworth/.nvm/versions/node/v18.16.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/tomainsworth/.fig/bin:/Users/tomainsworth/.local/bin:/Users/tomainsworth/.composer/vendor/bin:/Users/tomainsworth/.composer/vendor/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - ZDOTDIR: /Users/tomainsworth
    - __CFBundleIdentifier: com.microsoft.VSCode
@shifenis
Copy link

I have same problem, switch from beta to stable but same problem.
fig doctor passes all stages with success

@Tom-Ainsworth
Copy link
Author

Sidenote: I've had Fig since May 2023, and got upgraded to the Pro tier when Amazon took over. It has been working fine for a long time, but today I've had a number of issues, this being the latest one

@ismael01866
Copy link

ismael01866 commented Jan 25, 2024

Yep, same issue. Started today, prompt is not displaying. Ran fig doctor/restart (all checks passes, ...)

fig-details:

  • 2.17.0
    hardware-info:
  • model:
  • model-id:
  • chip-id: Apple M1 Max
  • cores: 10
  • mem: 32.00 GB
    os-info:
  • macOS 13.2.1 (22D68)
    environment:
  • shell: /bin/zsh
  • terminal: terminal
  • cwd: /Users/imariscal
  • exe-path: /opt/homebrew/bin/fig
  • install-method: brew
  • env-vars:
    • FIGTERM_SESSION_ID: 0ea527fb-90a3-4c23-afdf-192350a3d639
    • FIG_SET_PARENT_CHECK: 1
    • FIG_TERM: 2.17.0
    • PATH: /Users/imariscal/.bun/bin:/Users/imariscal/.pyenv/shims:/Users/imariscal/.volta/bin:/Users/imariscal/.sdkman/candidates/java/current/bin:/Users/imariscal/.sdkman/candidates/gradle/current/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/imariscal/Library/Android/sdk/emulator:/Users/imariscal/Library/Android/sdk/tools:/Users/imariscal/Library/Android/sdk/tools/bin:/Users/imariscal/Library/Android/sdk/platform-tools:/Users/imariscal/Library/Android/sdk/emulator:/Users/imariscal/Library/Android/sdk/platform-tools:/Users/imariscal/.fig/bin:/Users/imariscal/.local/bin
    • SHELL: /bin/zsh
    • TERM: xterm-256color
    • __CFBundleIdentifier: com.apple.Terminal
    • FIG_PID: 1405
    • FIG_SET_PARENT: 0ea527fb-90a3-4c23-afdf-192350a3d639

@patrikbily
Copy link

Same here.

@idlethumbs
Copy link

Same problem here, started today, fig doctor passing

@laurapadilla
Copy link

Same issue as well. Started today. Ran fig doctor (passing), fig restart and closed the terminal, still not working.

@navid-asgharzadeh
Copy link

navid-asgharzadeh commented Jan 25, 2024

same here

I also updated my Macbook to Sonoma 14.3 and then this happend. Don't know if it matters

@shifenis
Copy link

same here

I also updated my Macbook to Sonoma 14.3 and then this happend. Don't know if it matters

Same here, updated today to Sonoma 14.3 (23D56) and stop working since that

@elizatlawy
Copy link

Same here

@laurapadilla
Copy link

same here
I also updated my Macbook to Sonoma 14.3 and then this happend. Don't know if it matters

Same here, updated today to Sonoma 14.3 (23D56) and stop working since that

I'm still on 14.2.1 and everything was working fine until today. I'm thinking it's a Fig-specific issue?

@commonPlaceC
Copy link

same here, that's what web inspector says
image

@hugoewarrior
Copy link

Same here, with MacOs Sonoma 14.3

@SamJBarney
Copy link

This is also occurring on MacOS Ventura 13.6.3.

@mkirlin
Copy link

mkirlin commented Jan 25, 2024

Checking in to note another instance of this on Sonoma 14.2.1 (23C71), fig_cli 2.17.0. fig doctor is reporting clean, but no autocomplete anywhere.

@themashcodee
Copy link

same here, all of a sudden it stopped working, everything is fine.

I tried reinstalling fig, restarting fig, restarting my laptop. But the suggestions does not comes up.

@nabetse28
Copy link

nabetse28 commented Jan 26, 2024

Same here, with MacOS Sonoma 14.3 intel chip. I got this:

Let's see if Fig is in a working state...
✘ Figterm: No FIGTERM_SESSION_ID

   0: No FIGTERM_SESSION_ID
   1: environment variable not found

Location:
   fig_cli/src/cli/doctor.rs:658

@2coo
Copy link

2coo commented Jan 26, 2024

Dropdown not appearing

fig.not.working.mov

@2coo
Copy link

2coo commented Jan 26, 2024

Guys, they rebranded Fig as CodeWhisperer.

Solution: uninstall Fig but install AWS CodeWhisperer

https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

@themashcodee
Copy link

@2coo I did that but CodeWhisperer does not support https://cursor.sh/

@80imike
Copy link

80imike commented Jan 26, 2024

Same here, with MacOs Sonoma 14.2.1

@tungamiraimujuru
Copy link

Also running MacOs Sonoma 14.2.1 and facing the same issue, since yesterday.

@akifunal
Copy link

I have been experiencing the same issue with macOS Sonoma 14.2.1 since yesterday.

@knielsen-foreflight
Copy link

I think they forgot to do some permission handling in the normal Fig.
Installing CodeWhisperer instead which works.

@rostik32
Copy link

I have been using fig for a year and I encountered the same problem a few days ago.

I have not updated Mac OS in the past few days, I have version 14.1.2 (23B92) MacbookAir m1

@jumpogpo
Copy link

Same here, with MacOs Sonoma 14.3

@yaser-alazm
Copy link

Same here, Fig stopped working since yesterday on Mac.

@marklanham
Copy link

Guys, they rebranded Fig as CodeWhisperer.

Solution: uninstall Fig but install AWS CodeWhisperer

https://aws.amazon.com/blogs/devops/introducing-amazon-codewhisperer-for-command-line/

Yep, I uninstalled Fig and installed CodeWhisperer and now it works again.

@yaser-alazm
Copy link

I can confirm too that it's working after installing CodeWhisperer

@laurapadilla
Copy link

laurapadilla commented Jan 26, 2024

Can confirm that it works after installing CodeWhisperer (on MacOS Sonoma 14.3 [23D56]).

They have a tiny little message [that I just noticed 2 minutes ago] on the fig.io homepage announcing the change.

Screenshot 2024-01-26 at 9 23 03 AM

@danielweck
Copy link

Yep, same experience here, I uninstalled Fig and migrated to AWS CodeWhisperer.

@LawrenceZ
Copy link

did anyone get the autocomplete with history to work in the aws codewhisperer cli?

@shifenis
Copy link

With CodeWhisperer we can't use custom scripts

@favna
Copy link

favna commented Jan 28, 2024

Same issue here, sidegrading to codewhisper works. Shame for the no custom scripts though as I used one for work. I hope they add that back.

@themashcodee
Copy link

It started working now, I don't know how 🧐, maybe they fixed their servers or something.
But I am happy now :)

@HeathStratosphere
Copy link

HeathStratosphere commented Jan 29, 2024

@2coo I did that but CodeWhisperer does not support https://cursor.sh/

Working in Cursor IDE for me, on Ventura 13.4.1:


Version: 0.24.3
VSCode Version: 1.85.1
Commit: 0924ede25947ac9b7d2e64a607a8c74cf8668f70
Date: 2024-01-28T07:15:14.673Z
Electron: 25.9.7
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 22.5.0

@themashcodee


All of that aside, if this was the planned method of sunsetting Fig- to break it on the server side, let fig doctor keep showing all green, and let devs figure it out for themselves- then that's pretty raggedy.

@navid-asgharzadeh
Copy link

I just ran 'fig restart' and now it works again 🥳

@mschrage
Copy link
Member

mschrage commented Jan 29, 2024

Hi everyone!

Quick Fix

  1. Run fig restart
  2. If still not fixed, run fig debug devtools autocomplete and once the page is open hit cmd+r to refresh the page

More information
It appears that this is a caching issue related to macOS Sonoma. We aren't 100% sure and we are investigating. We are currently not able to reproduce it on our end. We are working with users to find out more.

If you are still having issues, please share you a screenshot of the Web Inspector console.

Other
If you're just using Fig for autocomplete, we recommend upgrading to CodeWhisperer for command line

@jole78
Copy link

jole78 commented Jan 29, 2024

@mschrage I see this in the Web Inspector console
CleanShot 2024-01-29 at 21 04 27@2x

UPDATE: it works again after a second restart 🤷

@micheletedeschi
Copy link

I fixed changing zsh theme, using awesomepanda theme the autocomplete doesn't work

@dikaio
Copy link

dikaio commented Jan 31, 2024

9 months since this repository has been worked on. Like most other open-source projects bought out by FANGs, they end up dead or push users into one of their paid products/services.

@TvojTatk0
Copy link

I had very same issues with fig. Today, update showed up. Since update, even dashboard stop working with error message: "Something went wrong :(".
I tried:

  • reinstall
  • a lot of restarts
  • log in/out
  • force quit

Do I really have to switch to the CodeWhisperer?
image

@beatrizsmerino
Copy link

beatrizsmerino commented Jan 31, 2024

I have the same problem

Captura de pantalla 2024-01-31 a las 12 59 34

The login does not work now, but a few days ago it was good

I have wasted a lot of time with this and just today I can't spare it. A word of advice to anyone who is having the same thing happen to them, uninstall Fig and install CodeWhisperer instead.

I leave here the commands:

1. Uninstall FIG

fig uninstall

2. Install CodeWhisperer

https://desktop-release.codewhisperer.us-east-1.amazonaws.com/latest/CodeWhisperer.dmg

3. Enable accessibility on MAC

System settings / Privacy and security / Accessibility / CodeWhisperer (Enable the app)

image image image

4. Check if there are no errors and if it works

cw doctor
Captura de pantalla 2024-01-31 a las 13 31 48

5. These steps will modify your VSC and ZSH configuration file automatically

image image image

This was referenced Feb 1, 2024
@blockiyt
Copy link

blockiyt commented Feb 2, 2024

+1

@ben-girardet
Copy link

I tried AWS CodeWhisperer but it doesn't cover half of the features available in Fig (yet I presume). It's not a valid workaround for now.

@kachkaev
Copy link

kachkaev commented Feb 2, 2024

Same here. Autocompletion works, but Dashboard does not load. Following #2885 (comment) does not help. Here is what I see in fig debug devtools autocomplete:

Screenshot 2024-02-02 at 16 50 12

Running fig --version in CLI returns 2.17.1.

@withfig withfig locked as resolved and limited conversation to collaborators Feb 13, 2024
@mschrage
Copy link
Member

Thanks to everyone for chiming in! This thread has quite a few different issues being reported, and we think most have been resolved.

Please open a new issue if you are still being impacted.

@mschrage mschrage added type:bug Something isn't working and removed NEED_TO_LABEL labels Feb 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests