-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
bug: default settings don't update on updates #1222
Comments
If we decide what the API should be, then why are we even allowing the users to modify it? If we remove the ability to modify it, then we can control it via updates. |
Because the entirety of ReVanced is built in a way that is independent of us, a few extra settings go a long way |
OK. So, updating the settings only if they are set to default, right? |
Yes |
Essentially, the API URL should be a global variable in the app, and the default value of the API URL should use that variable instead of duplicate it, if API URL is equal to the variable after transformation, it should stay a reference to the variable when applying changes |
A migration function has been introduced. Does this suffice? |
🍜 This issue should been resolved by the release of v1.19.0 |
Type
Error while running the manager
Bug description
If a default setting, like the default API URL changes in an update, installing the new update doesn't update it
Steps to reproduce
releases.revanced.app
releases.revanced.app
not functioning)api.revanced.app
but instead it'sreleases.revanced.app
Acknowledgments
The text was updated successfully, but these errors were encountered: