Solutions to the most common GITmaxed issues. Each entry follows a symptom → fix structure so you can scan quickly and get back to work.
Sign-in window does not open
Symptom: clicking "Sign in using your browser" does nothing.
Fix: the default browser handler may be broken, or a security tool blocked the custom URL protocol. Open any https link manually to verify your browser works, then retry — or temporarily allow protocol launches from GITmaxed in your security software.
Push fails with 401 or 403 after a while
Symptom: pushes that worked yesterday now fail authentication.
Fix: the account's OAuth token was revoked, expired, or invalidated by a password/2FA change. Open Preferences → Accounts, remove the affected account, and add it again with the browser flow. Other accounts are unaffected.
Push goes to the wrong organization
Symptom: a repository pushes as the wrong identity.
Fix: the repository has no explicit account assignment and fell back to the primary account. Open the repository, use the account picker in the Changes sidebar, and select the correct account — the choice sticks permanently.
The update window appears on every launch
Symptom: the "Update Available" window shows even after installing what you believe is the newest build.
Fix: the updater compares release titles literally — the installed title doesn't exactly match the published release name. Install the build published under the matching release name (see the Updates page).
Updater shows "STATUS: ERROR"
Symptom: the updater window shows an error state.
Fix: the GitHub API could not be reached (offline, proxy, firewall). Verify internet access to github.com and api.github.com; corporate proxies may need an allowlist entry. The application itself remains fully usable without update checks.
Repository list is empty after reinstalling
Symptom: after reinstalling, no repositories appear.
Fix: the repository database lives in per-user application data; a portable↔installer switch can change the expected data location. Use Add local repository and point at your existing clone folders — history and settings inside them are untouched. Re-assign accounts with the sidebar picker if prompted.
Clone fails with a folder or permission error
Symptom: cloning aborts complaining about the target path.
Fix: the default clone path is unavailable, contains unsupported characters, or is inside a protected folder. Choose a different location in the clone dialog — a dedicated folder per account is recommended, which also enables automatic account assignment.
Window opens tiny or with broken fonts
Symptom: the interface renders at odd scale on high-DPI displays.
Fix: fully close GITmaxed (check the system tray too), then relaunch. If fonts stay wrong, toggle Windows display scaling and restart the app.
Bundled Git seems missing (advanced)
Symptom: operations fail claiming Git was not found inside the installation.
Fix: antivirus may have quarantined files inside the app's Git directory after an update. Restore the quarantined folder or reinstall GITmaxed, and consider an antivirus exclusion for the install path if the false positive persists.
Still stuck?
Report the issue with: your GITmaxed version (Help → About), Windows version, the exact operation failing, and any error text from the app. That combination is enough for maintainers to reproduce most problems.
No comments:
Post a Comment