Upgrade Storagejsdebugger flag breaks app update
Not sure if it's right for this issue to be posted in the forums, but considering it doesn't involve developer things like plugin interfaces and the stable version is affected, it's posted here, feel free to close it if it's not suitable.
---
Description:
When the command line has the jsdebugger flag, checking for updates will always show ‘Checking for updates...’ .
To reproduce the steps:
1. Delete the profile directory (to avoid the effects of prefs)
2. Run
3. Open the check for updates window: always show "checking for updates".
4. Close zotero and delete the profile directory.
5. Run
6. Open the check for updates window: "no update"
The only difference between the two is the presence or absence of the --jsdebugger flag.
Stable reproduction on Zotero 7.0.13, Zotero 7.1b12, Zotero 7.1b19 (x64).
OS: Windows 11 24H2.
No plugins were installed when performing the above operations.
---
Description:
When the command line has the jsdebugger flag, checking for updates will always show ‘Checking for updates...’ .
To reproduce the steps:
1. Delete the profile directory (to avoid the effects of prefs)
2. Run
binpath -p 'profile path' --jsdebugger3. Open the check for updates window: always show "checking for updates".
4. Close zotero and delete the profile directory.
5. Run
binpath -p 'profile path'6. Open the check for updates window: "no update"
The only difference between the two is the presence or absence of the --jsdebugger flag.
Stable reproduction on Zotero 7.0.13, Zotero 7.1b12, Zotero 7.1b19 (x64).
OS: Windows 11 24H2.
No plugins were installed when performing the above operations.
-
dstillmanedited March 12, 2025The debugger is a separate instance of Zotero, so it prevents the updater from completing. We might be able to make it not hang on "Check for Updates…", though (not particularly for this use case, which really doesn't matter, but because it could probably happen in other situations).