Something went wrong

[othyn]

Almost every panel I try to load, this error is constant. Just 'Something went wrong.' Nothing works in the app!

Things I've tried;

• Clearing cache
• Signing in/out
• Deleting and re-downloading the app, making sure to delete all app contents and docs
• Using different networks; WiFi, cellular, other WiFi networks...

I think there is something wrong with my account or GitHub's API as no matter how many times I clear things out, networks I'm on or anything, nothing gets it working.

ℹ️ Additional Debug Info

GitHub for iOS, Version 1.75.0 (74400986) Device: iPhone 12 Pro Max (iOS 16.0)

And before people mention the iOS 16 beta, it's not the beta. I've had this issue for a very long time. I've just given up using the app and every now and again try it only to be disappointed again.

EDIT:

For future readers, if you are experiencing this problem, I contacted GitHub support in the end as it was outside of the scope of this message board. An engineer patched something I believe on my account (given the back and forth we had) and it started working again shortly after. No idea what the root cause is, but its not something that can be fixed 'client' side.

[haldun]

Hi @othyn, I am sorry to hear that you are having problems with the app. In order to pin down the problem, can you please share some details about the issues you are having? Is that happens on every screen?

[othyn]

Absolutely!

Unfortunately I don't have any steps to reproduce as its just happening no matter what.

What is very interesting though is that I've had friends and collegues try to visit my account (Othyn) in the GitHub app and they get the same error when trying to view or load any of my repo's. However, this problem does not exist on the web version of GitHub.

Noticable behaviour

• Any page I try to access that is related to my own account's (Othyn) repo's results in the request timing out and being presented with a page that simply states 'Something went wrong.' with the option to 'Try again', which ultimately does nothing but result in the same error page. This behaviour is still observed even after doing all of the following:
  • Clearing cache
  • Signing in/out
  • Deleting and re-downloading the app, making sure to delete all app contents and docs
  • Using different networks; WiFi, cellular, other WiFi networks...
• This seems to only affect access to Repo's that my account owns.
• I can access other accounts, organisations and shared repo's just fine, I cannot access any of my own repo's through the GitHub app. GitHub web is unaffected.
• Friends and collegues GitHub app's also exhibit the same error when viewing any of my account's (Othyn) repo's. But this does not affect their own accounts in the GitHub app or viewing my account's (Othyn) repo's on the web.

Screenshots

When trying to interact with the 'favorite repo' functionality, any search results that contain my own repo's makes the request fail with this page, although I can search and add other repo's as long as the rendered list does not contain any repo's I own. However this will just randomly break completely at times too and not render any repos at all resulting in the same error until I quit and restart the app.

When trying to view any of my accounts repos, it just flat out fails.

When trying to open any of my accounts repos, it just flat out fails.

[othyn]

I've also sent off a ticket to GitHub as I think this is out of the communities hands tbf.

[haldun]

Thank you very much for the details. I can actually reproduce this when I navigate to one of your repositories. I will create an issue for this to track further.

[othyn]

Amazing, thanks!

[Fopen1]

У меня такая же ошибка в веб версии

[thorwhalen]

Was this solved?
How was it solved?

Because I have the same issue.
I'm on an iPhone (ne newest I think). The issue appeared first a few months ago I think.

[othyn]

I contacted GitHub support in the end as it was outside of the scope of this. An engineer patched something I believe on my account (given the back and forth we had) and it started working again.

[rocheparadox]

I faced the same issue in my iPhone and iPad. It is not fixed yet. However, I found a workaround. If you click your profile (bottom right in iPhone) or your profile (bottom left in iPad) and then click the repositories from the options, the repositories are fetched and displayed properly.

[riteshjagga]

I faced the same issue in my iPhone. I contacted GitHub support but they couldn't fix it and shared this note

Note that while this support ticket may automatically close, that the internal issue will remain open and under investigation.

However, I could get it working on my own by following these steps:

Note: The steps involve Signing out and Signing in. I remember that I did that in the past before I raised the ticket with GitHub support but this time I think I got something different on signing out.

• Navigate to Profile (In the bottom-right) > Settings (Cog icon button) > Manage Accounts > Edit > Delete (on the left) > Sign out (on the right)
• A popup opened saying that "We couldn't sign out you successfully because some token was not found" and options to OK (which is sort of Cancel) and "Sign out anyway".
• I said OK once without paying attention carefully and this time I choose "Sign out anyway"
• Signed in again to see that I could access Repositories and Pull Requests.

[keypointt]

Worked for me. Thank you.

[kumaraguru1735]

I am having same issue for the past week, still not cleared

[Fopen1]

У меня год уже бесить этот ошибка не исправляют

[alex-ak1]

Got same error on old browser inside virtual machine (firefox 86, ubuntu 20). Switched to new google chrome and all works fine.

[Fopen1]

оказывается русский язык не поддерживает гитхаб

[dataspun]

Same issue with GitHub iOS app version 1.198.0
Repos are fine but not the org -- I'm an owner.
Workarounds above (signing out/in) don't work.

Update:
Working with GitHub support
Using the beta app to help developer team troubleshoot

[damoncoo]

Same issue with the latest iOS app

[MichalecSS]

Michal Bičík

[jankais3r]

Still happening in 2026. Signing out and back in helps. No need to contact GitHub support.