desktop icon indicating copy to clipboard operation
desktop copied to clipboard

Cannot Clone Private Repository Even Though I Have Adequate Access

Open amarraff opened this issue 1 year ago • 2 comments

The problem

I am collaborating with a team on a project, and I've had difficulty cloning their project on Linux via GitHub Desktop. Today we were troubleshooting, and they tried making the repository public for a brief period of time. This worked fine, and I was able to clone the repo. However, it's a private project with NDAs and such, so they immediately made it private again. As soon as that happened, I received the error in the attached screenshot again. Due to this project being under NDA, I cannot attach a log file, I'm sorry. However, after viewing the logs myself, the key error seems to be that the repository cannot be found. The log says "remote: Repository not found."

I booted into my Windows 11 partition and was able to clone the repo while private with no issues. So, after a lot of narrowing it down, the problem unfortunately seems to stem from this version of the GitHub Desktop client.

Release version

3.3.18-linux1 (x64)

Operating system

Linux Mint 21.3 x86_64

Steps to reproduce the behavior

1.) Have someone else add you as a member of their private GitHub repo, either direct access or team access (both yielded the error). 2.) Try cloning their repo to your machine. 3.) See thrown error that says repo doesn't exist, or you don't have access. 4.) Have repo owner make it public. 5.) Try cloning again, should work. 6.) Have repo owner make it private again. 7.) Try fetching origin, should throw an error saying the repo no longer exists.

Log files

No response

Screenshots

github linux error from 2024-06-14 13-02-20

Additional context

This appears to be different from the known issue of Github Desktop being unable to access a repo. I can see the repo in my list, I just can't clone it when it's private.

amarraff avatar Jun 14 '24 17:06 amarraff

Same issue with latest version

tonislcs avatar Jun 15 '24 10:06 tonislcs

I have the same issue. I tried downgrading to 3.3.17 and to 3.3.13 but I have the same problem. Same problem trying to clone a repo or to pull a repo cloned by bash using ssh authentication. How can I see what SSH key is used for SSH authentication? Thanks

benetti-marco avatar Jun 22 '24 18:06 benetti-marco