You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add obfuscation option to flutter build aar also #56068
I meant the dart obfuscation flag you added (awesome feature btw) is equally useful for APKs as it is for AARs. It's an Android library. For library developers, that's sometimes the final shipping artifacts (to be consumed by other companies that they don't want to share "source" with).
The build_aar command would need to be refactored to get the buildInfo from the flutter command instead of manually constructing it. I don't have time to look at this right now, but I could advise someone else that wanted to take a look
Dart doesn't support any sort of separate compilation, so any plugin dart code would be compiled into libapp.so in the main AAR and obfuscated. I think (but @blasten would need to confirm) that this is only building the Java side of things
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
jonahwilliams commentedon Apr 30, 2020
should build aar have this? What is it for?
jonahwilliams commentedon Apr 30, 2020
i.e. I though aar was for producing testing artifacts, and the actual build would be done separately
xster commentedon Apr 30, 2020
I meant the dart obfuscation flag you added (awesome feature btw) is equally useful for APKs as it is for AARs. It's an Android library. For library developers, that's sometimes the final shipping artifacts (to be consumed by other companies that they don't want to share "source" with).
jonahwilliams commentedon Apr 30, 2020
Oh okay, I thought that was only for testing artifacts
jonahwilliams commentedon Apr 30, 2020
The build_aar command would need to be refactored to get the buildInfo from the flutter command instead of manually constructing it. I don't have time to look at this right now, but I could advise someone else that wanted to take a look
xster commentedon Apr 30, 2020
(I don't know what's the best way to test) but can't it just do #56069?
jmagman commentedon May 4, 2020
I can look at this.
jmagman commentedon May 6, 2020
Should plugins also be obfuscated? And if so, what's the right thing to do with splitDebugInfoPath?
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/android/gradle.dart#L773-L775
jonahwilliams commentedon May 6, 2020
Dart doesn't support any sort of separate compilation, so any plugin dart code would be compiled into libapp.so in the main AAR and obfuscated. I think (but @blasten would need to confirm) that this is only building the Java side of things
github-actions commentedon Aug 21, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.