9/21/2023 0 Comments React navigation uncompiled png file passed as argument. must be compiled first into .flat fileThis will cause any local state in the old component to be lost. flat file.Įrror: failed parsing overlays. React will see a new component and unmount the previous component before rendering the new one. ![]() android/app/build/intermediates/res/merged/debug/drawable-hdpi/node_modules_reactnavigationstack_dist_views_assets_backicon.png: error: uncompiled PNG file passed as argument. I have come across this issue (3097) and tried to set android.enableAapt2f. Current Behavior While trying to build production apk with gradle v4.3 and gradle tools 3.0 process crashes. gradlew assembleDebug, the build fails with the following error: The issue tracker is reserved for bug reports only. React-native-git-upgrade: 0.2.7 Description Watchman: 4.9.0 - /usr/local/bin/watchman Your EnvironmentĪs already stated, Android Studio 3.0, gradle 4.1 & gradle tools 3.0.0 (build tools 26.0.2).CPU: 圆4 Intel(R) Core(TM) i7-3770 CPU 3.40GHz That everything gets bundled properly with AAPT2. The react-navigation picture resource may cause a package error? #1976 (comment).set android.enableAapt2=false in /android/gradle.properties.This SO answer seems to provide some more details but, yeah, until better explanations here are some workarounds: flat file. 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. Which is it's caused by the asset files that gets bundled, like: node_modules_reactnavigation_src_views_assets_backicon.png ![]() 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: ![]() This is basically a "reload" of issue #1976 because it became polluted and hard to follow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |