Skip to content
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: universal patches are always shown #1080

Closed
4 tasks done
Ushie opened this issue Aug 3, 2023 · 11 comments · Fixed by #1087 or #1096
Closed
4 tasks done

bug: universal patches are always shown #1080

Ushie opened this issue Aug 3, 2023 · 11 comments · Fixed by #1087 or #1096
Labels
Bug report Something isn't working

Comments

@Ushie
Copy link
Member

Ushie commented Aug 3, 2023

Bug description

Universal patches are shown in the patches selector screen regardless of whether or not "Experimental universal patches support" is enabled in ReVanced Manager settings

Solution

Hide universal patches in patches selector if the setting is not toggled on

Acknowledgments

  • I have searched the existing issues; this is new and no duplicate or related to another open issue.
  • I have written a short but informative title.
  • I properly filled out all of the requested information in this issue.
  • The issue is solely related to ReVanced Manager and not caused by patches.
@Ushie Ushie added the Bug report Something isn't working label Aug 3, 2023
@TheAabedKhan
Copy link
Member

Are they just shown or selectable as well?? If they are not selectable then that's not an issue because user needs to see that there are other patches as well which are, although, disabled.

However, If they are causing disturbance in patches selection, I can add a chip that can hide/show unsupported patches, but they will be able to use them only after enabling the toggle in the settings page.

@Ushie
Copy link
Member Author

Ushie commented Aug 4, 2023

They are selectable, that's where the issue lies, people with universal patches not toggled on might not realise that these patches aren't specific to that package, as it looks like any other, it might be good to separate them too or add an indicator

@TheAabedKhan
Copy link
Member

Screenshot_20230804-164942_Pixel Launcher Extended.png

I am unable to reproduce your issue. Can you send a screen recording?

@Ushie
Copy link
Member Author

Ushie commented Aug 4, 2023

Screenshot_20230804_150610
SmartSelect_20230804_150631

@TheAabedKhan
Copy link
Member

Oh, ok! I got confused between experimental patches and universal patches.

You are right! PR on the way.

@ILoveOpenSourceApplications

Can we consider #888 to be solved with this implementation as well?

@TheAabedKhan
Copy link
Member

TheAabedKhan commented Aug 5, 2023

@ILoveOpenSourceApplications I will create a new PR for #888 which will actually separate them. Right now, if universal patches are enabled, they are mixed with the other patches.

@ILoveOpenSourceApplications

Yes, so either we can hide universal patches and only show it to users who enable them in settings or have what the user in #888 say, a separate section for universal patches be implemented. I think one or the other is enough and implementing both would be unnecessary. Any opinion?

@TheAabedKhan
Copy link
Member

TheAabedKhan commented Aug 5, 2023

I think one or the other is enough and implementing both would be unnecessary.

A separate section like this can help easily separate the universal patches even though all the patches are shown on the same page.

@Ushie
Copy link
Member Author

Ushie commented Aug 5, 2023

Yes, so either we can hide universal patches and only show it to users who enable them in settings or have what the user in #888 say, a separate section for universal patches be implemented. I think one or the other is enough and implementing both would be unnecessary. Any opinion?

Implementing both is definitely necessary:

  1. your average consumer has no idea what the difference between universal and package-specific patches is
  2. there is no differentiator between universal and package-specific patches, so even ones that know the difference would be unable to specify which is which

@validcube
Copy link
Member

validcube commented Aug 6, 2023

🎉 Hooray! This issue have been fixed in #1087, please wait for the next version of ReVanced Manager.

Feel free to reopen if you like to suggest another solution.

@validcube validcube linked a pull request Aug 6, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug report Something isn't working
Projects
None yet
4 participants