I usually edit my original post after submitting it to add images.
The update is almost always for the latest version. I agree it would be nice if they told us the version, but would it even help if they tell us the version? Itâs not like there are any changelogs to know what you are getting yourself into. I find that it is better to just disable all auto updates and update manually via Help menu or by reinstalling.
If youâre on Cursor Nightly, the update notification should offer a newer Nightly build. It shouldnât downgrade you to Stable. Nightly and Stable update through different channels.
If youâre not sure, you can check your current version in Help > About and compare it with the version shown in the update prompt. If you notice that your version got lower after updating, let me know, thatâs definitely a bug.
About showing the version in the notification and having a more detailed changelog, Iâve passed both requests to the team and theyâre on the radar.
After running DockerDesktop and Cursor again I see that Cursor have correct newer Nightly version
though it still have this problem with missed file:
```
⯠ge 1
cursor-nightly ../../../env-level/pd/.terraform.lock.hcl
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open â/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.jsonâ
on î feature/PC-18744_Centralize_pipelines [$!?] via v3.14.3 (.venv) via default
⯠cursor-nightly --version
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open â/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.jsonâ
2.7.0-pre.76.patch.0
dbf1f1e2fb595868a79f3c011f76fc41eeb20b29
arm64
```
Glad the update eventually went through and youâre on the correct version.
About the Restart to Update hang, thatâs a known issue with Nightly updates. The team is aware. If it happens again, Force Quit plus a manual relaunch is a solid workaround, like you did.
Docker Desktop crashing after Force Quit is probably a coincidence. macOS sometimes terminates related processes when you force-close an app. If it keeps happening specifically when closing Cursor, let me know.
For the nls.messages.json error, I see weâre already discussing it in your other thread Error when I use -w option. The file is still missing in the new version too. Iâll share this with the team along with both examples. Letâs keep tracking it there.
@deanrie please note the first 2 comments are about the ongoing issue that we canât paste images to bug reports, like we can with every other forum post.
Bug reports are using a form to format your post which does not allow pasted images. Ideally the text areas in the form could receive pasted images, but I think they are unformatted text areas as of now. The workaround is to immediately edit the post after submitting the bug report, which then behaves like a normal post and can add the images like normal then.
No reason whatsoever for disabling pasting images, and I wonder how many bug reports are given up mid composing - Iâve certainly dropped about 75% submissions are the effort required is too high.
Fair point. If you are using Windows, pressing âWindows Key + Vâ allows you to have clipboard history which you can then paste a screenshot from before. The overall bug form is hassle. I use Greenshot to take screenshots which has the option to save it or open it up in an image editor, which can help preserve the screenshot.