-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Updates" section in RVX Manager loads indefinitely #1956
Comments
This is an old issue with the official ReVanced Manager.
|
Unfortunately, it didn't work for me, still the same. |
Well.. try again later |
@inotia00 I changed my IP address and this issue did not happen, it seems like GH is restricting the IP from accessing the GitHub API, it's kind of a rate limit, but I have no idea why it happens, it's strange. |
Maybe there's something wrong with the way ReVanced Manager accesses the Github API. rvx-builder also had a similar issue, but I was able to resolve this issue in rvx-builder by refactoring the source code. |
Thanks for the info. |
It is working for me while using 1.1.1.1 application. |
fixed in rvx manager v1.20.2 |
This issue is reported in ReVanced/revanced-manager#1776. And yes, it's caused by GitHub ratelimit not being handled. |
Still having the issue where it keeps "loading" with the new version 1.20.2. |
There are a variety of reasons why Manager may not display information from Github. One of the most well-known reasons was that it took too long to wait for the Github API response. - This bug has been fixed in RVX Manager 1.20.2. There may be a variety of reasons why the Manager is still unable to fetch information from Github. |
I'm still having this issue on 1.23.4 and 1.22.2 |
Type
Other
Tools used
RVX Manager
Application
RVX Manager 1.20.1
Bug description
It just indefinitely loads whilst trying to check for Manager and patches updates. Also, I can't use patches because of that, I guess.
Error logs
No response
Solution
No response
Additional context
No response
Device Environment
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: