Repository shows “does not seem to exist anymore” after renaming project on GitHub and re-adding to GitHub Desktop (Linux)

[developersharif]

The problem

After renaming a repository on GitHub, GitHub Desktop (Linux) fails to recognize the renamed project properly. Even after removing the old project and adding the newly renamed one, GitHub Desktop displays an error message and network operations (fetch, push, publish, etc.) stop working.

Expected Behavior:

GitHub Desktop should correctly recognize and connect to the renamed repository, allowing fetch/push/publish actions to work normally.

---

Actual Behavior:

An error dialog appears:

“The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.”

No network activity occurs, and fetch/publish operations are disabled.

---

Environment:

• OS: Linux (Ubuntu 25.04 x86_64)
• GitHub Desktop Version: 3.4.0-linux1 (x64)
• Git Version: 2.48.1
• Network: Stable internet connection verified

---

Additional Context:

• Repository was renamed from <old-repo-name> to <new-repo-name> on GitHub.
• Verified that the renamed repository is accessible via browser and terminal (git fetch works manually).
• Screenshot attached for reference.

Release version

3.4.0-linux1 (x64)

Operating system

Ubuntu 25.04 x86_64

Steps to reproduce the behavior

Steps to Reproduce:

1. Rename an existing repository on GitHub.
2. In GitHub Desktop (Linux), remove the old repository entry.
3. Clone or add the renamed repository again.
4. Try fetching or publishing any branch.

Log files

No response

Screenshots

Additional context

No response