bug: Confusing app name variant

[validcube]

Bug description

ReVanced Manager build types has two type, release mode and debug mode

• Compile as Release mode will have the app name set to default

• Compile as Debug mode will append the (Debug) suffix to the app name

Interestingly when you compile as Release mode without apk signing information will append the (Debug signed) suffix to the app name

(Debug signed) build, it does not act like (Debug) build, but rather default release build signed with generic debug/development keystore

A new naming as to be made, this issue affects both Flutter/Compose.

Version of ReVanced Manager and version & name of app you are patching

... not relevant

Installation method

None

ReVanced Manager logs

... not relevant

Patch logs

... not relevant

Acknowledgements

• [x] I have checked all open and closed bug reports and this is not a duplicate.
• [x] I have chosen an appropriate title.
• [x] All requested information has been provided properly.
• [x] The bug is only related to ReVanced Manager.

[Axelen123]

Honestly, the app name and package name change depending on build configuration (debug signed release build, debug) should be removed. It seems unnecessary and you can't install them alongside eachother anyway due to conflicting signature permissions.