Windows desktop: repeated "TypeError: h.setProgressBar is not a function" dialog when saving/downloading files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Description
On the ChatGPT/Codex Windows desktop app, any operation that triggers a file download/save (e.g. saving a photo/image inside a Codex session) causes a recurring error dialog: "A JavaScript error occurred in the main process — Uncaught Exception: TypeError: h.setProgressBar is not a function".
The stack points to a DownloadItem event handler, so the app appears to call setProgressBar on an object that doesn't have that method (likely DownloadItem; the actual API is BrowserWindow.setProgressBar).
Environment
- App version: 26.820.7780.0 (ChatGPT.exe 151.0.7922.170)
- OS: Windows x64
- Install source: Microsoft Store (package
OpenAI.Codex)
Steps to reproduce
- Open the ChatGPT/Codex desktop app on Windows.
- Start a Codex session and ask it to save/export an image (or any action that triggers a download via DownloadItem).
- The "A JavaScript error occurred in the main process" dialog appears.
- Dismissing it with OK does not help; it reappears repeatedly during/after the download.
Expected behavior
No error dialog when saving/downloading files; download progress should be handled gracefully.
Actual behavior
Recurring uncaught TypeError dialog in the main process.
Error text
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the desktop app codebase for the DownloadItem event handler and calls to setProgressBar, then reproduce a file save or download on Windows. Confirm which object owns the progress-bar API and verify that downloads complete without a recurring JavaScript error dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100