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
Android prod release - gradle tools 3 error #3097
Comments
As stated in #1976 the following temporary workaround got things moving again for me:
I'm using Android Studio 3.0.1 on OS X, Gradle 4.1, Build tools 26.0.2 |
Still facing this issue here. Any updates / fix on this? I tried adding the workaround and now get confronted by this error:
UPDATE: This specific error can be handled by deleting all images from: 'android/app/src/main/res/drawable-mdpi' (Thanks @sujayjaju) |
For me deleting all images did not help, It's not a fix, |
Any updates on this? I tried to set |
@adsellor I also did |
this is an upstream issue facebook/react-native#16906 |
I too was facing this issue, even after placing |
This is basically a "reload" of issue #1976 because it became polluted and hard to follow.
Current Behavior
When using Android Studio 3.0, gradle 4.1 & gradle tools 3.0.0 (build tools 26.0.2) (or higher), creating a production release is impossible because of this error:
uncompiled PNG file passed as argument. Must be compiled first into a .flat file.. error: failed parsing overlays.
Which is it's caused by the asset files that gets bundled, like:
node_modules_reactnavigation_src_views_assets_backicon.png
It's clearly related to AAPT2, the new version present in gradle tools 3.0 - but even the migration guide doesn't seem to offer an explanation for this kind of error. This SO answer seems to provide some more details but, yeah, until better explanations here are some workarounds:
android.enableAapt2=false
in[YOUR PROJECT]/android/gradle.properties
Expected Behavior
That everything gets bundled properly with AAPT2.
Your Environment
As already stated, Android Studio 3.0, gradle 4.1 & gradle tools 3.0.0 (build tools 26.0.2). Doesn't look like it's related to rn/navigation versions, but still happens with latest:
The text was updated successfully, but these errors were encountered: