GitHub App orphaned cache — getting Failed to fetch repository files
suvrodattamitu
HOBBYOP

a month ago

I have completely uninstalled and reinstalled the GitHub App authorization, unlinked my account, and completely rebuilt my project from scratch, but the backend is still throwing a bad credentials error.

$10 Bounty

9 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


a month ago

Try disconnect and reconnect the repo after reinstall?


mayori

Try disconnect and reconnect the repo after reinstall?

suvrodattamitu
HOBBYOP

a month ago

Already did that, fetched all the repositores and made the repository from private to public. still not working and it's showing the same issue.


a month ago

Is this repo under an orgs?


mayori

Is this repo under an orgs?

suvrodattamitu
HOBBYOP

a month ago

No. I checked organisations. No organisations. Also it's my personal project.


suvrodattamitu
HOBBYOP

a month ago

I can see project appeared in the select repositores option, once I click the repository this message appear. I am trying and doing different things, still same issue.


suvrodattamitu
HOBBYOP

a month ago

So what worked for me is,

Every time it's creating empty project. Then I went to the empty project by curiosity and then selected a repository, and it worked.


suvrodattamitu
HOBBYOP

a month ago

But getting a new issue here in deploying, "There was an error deploying from source". I think it's related to permission but I don't think I missed any permission anywhere.

image.png

Attachments


a month ago

Maybe try deploying it as a new service? if that work then you can delete the old service


mayori

Maybe try deploying it as a new service? if that work then you can delete the old service

suvrodattamitu
HOBBYOP

a month ago

Everytime I try creating new project, it's showing the same error I got first. getting Failed to fetch repository files and it creates empty project.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...