-
Notifications
You must be signed in to change notification settings - Fork 476
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
assets dont get encrypted #95
Comments
i tried an older fork and asset encryption works as it should. |
I don't know if it's a Studio issue or template issue but my theme no longer installs after building, I just get "app not installed". |
Hi @hndrk-themer! I believe I have fixed the asset encryption issue on my fork. Could you please check and verify? If it works, I'll open a PR to merge the fix to this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, after building signed apk the assets still are unencrypted tho build log states thst duplicates are getting encrypted. using apkeditor to analyze the signed release apk covers only plaintext xml overlays.
i imported the latest template and focused on readme.md, changeg package name and merged my overlays.
tried 4.1.2, beta3 and canary build of Android Studio.
The text was updated successfully, but these errors were encountered: