-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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] Renaming package (or use of Brave APK at all) results in drawable not found #3346
Comments
We do have a growing collection of these type of issues and they remain to this day to be incredibly complex to track down. With such large applications its difficult to pinpoint exactly what may be going wrong.
I'll give it a solid triage try soon and if I don't find anything, I'll close for one of these others. Thanks for the detailed research - I'll be sure to give it a solid attempt before I give up. |
@iBotPeaches I can attach a very simple FDroid application (single activity) that exposes the same bug referenced in above issues:
This happens only if you rebuild the APK using the option |
For reference, on my issue, I am not using |
thanks - I'll wait for the Android 14 drop, rebuild aapts(2) and dig into this. |
@iBotPeaches Thank you. To be safe, I have tried v2.7.0 and I have the same issues with that version, so while the error message from @auermich93 is the same, these may be separate issues. For me specifically, I am working to provide a free service (and FOSS) for users to create "renamed browsers" so they can have separate Work and Personal profiles for browsers like Brave and Firefox. Profiles seems to be a highly requested feature so this will monitor their releases and create versions for people to download and use as alternates. I can compile Brave from source, but that's HUGE overhead for a Chromium compile, so really hoping I can get EDIT: I've also taken what I've done to get things started in Docker and created a PR so you can take advantage of it if you would like (fully documented): #3351 |
Using this @auermich93 application as a sample, the PR linked above solves this. Either way - I'm rebuilding all the aapts shortly with Android 14 changes, but I'll close this with the above PR. |
Information
apktool -version
) - 2.8.1java --version
) - openjdk 22-ea 2024-03-19Stacktrace/Logcat
Steps to Reproduce
I am attempting to rename the package from
com.brave.browser
tocom.brave.personal
(to have multiple installs for multiple profiles).Attempt to rename
Other attempts
I have also tried multiple combinations of things, including, all of which fail similarly:
Attempt to rename manually
I have also tried renaming all text occurrences of the package name in XML and SMALI files to different extents with the same errors.
Attempt to use apktool without renaming
Running with no changes at all (zipalign and sign) causes the same error:
Result:
Running without signing (with and without zip aligning):
Results in an install erorr:
In all of the above, when running
apktool b
, I get warnings like this (a lot of them):And also when the APK installs, the icon is the default Android icon, and not the Brave icon.
Thoughts
Given that the error creeps up even when not changing anything (just zipalign and sign), perhaps there is something specific with the Brave APK causing issues?
APK
Downloadable: https://github.com/brave/brave-browser/releases/download/v1.58.135/BraveMonoarm64.apk
Questions to ask before submission
apktool d
,apktool b
without changing anything? YesThe text was updated successfully, but these errors were encountered: