I have a mobile application already created on android and iOS, however this most recent build has been failing for over a month no matter the runtime version. Hereās the error however much of it wont fit, its over 100k characters⦠and keep in mind I donāt know how to code, Iāve made my app using Appgyver codeless, so iām not sure what could be wrongā¦
Runtime version: 4.5.12;
AB version: 1.7.6
FAILED with ERROR:
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ā:app:mergeReleaseResourcesā.
Multiple task action failures occurred:
A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/drawable-mdpi/ic_stat_ic_notification.png: AAPT: error: failed to read PNG signature: file does not start with PNG signature.
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/drawable-mdpi/ic_stat_ic_notification.png: AAPT: error: file failed to compile.
A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/mipmap-ldpi/ic_launcher.png: AAPT: error: failed to read PNG signature: file does not start with PNG signature.
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/mipmap-ldpi/ic_launcher.png: AAPT: error: file failed to compile.
A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/mipmap-mdpi/ic_launcher.png: AAPT: error: failed to read PNG signature: file does not start with PNG signature.
ERROR:/tmp/594070-android-256392/platformBuilds/standalone_android/app/src/main/res/mipmap-mdpi/ic_launcher.png: AAPT: error: file failed to compile.
- Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
1 Like
I believe the App. ID is 491338, this has been quite a nuisance, so any assistance is appreciated greatly.
1 Like
Did you get this fixed? I am having the same issue.
1 Like
I eventually was able to get the iOS version downloaded. However I still cannot build the Android version without error⦠Itās been so long, trying twice a day at least. I am losing faith in Appgyver, and no one seems to reach out to developers to help. Clearly over 100 people are curious about this post, we canāt be the only two developers having no luck using the service any longer. Someone please look into this, let us know.
1 Like
itās also different errors every dayā¦
1 Like
That error is usually also seen when we compile in Android Studio. That error is caused by a problem with the āAssetsā PNG files and they may be corrupted. Many times the images that you load as PNG have to be reloaded and put into a folder and given a name. When uploading a PNG image, it should be advised that the ending of the image is .png and not leave empty spaces between the name and the point .png
Img.png
Img .png
If your images that were generated with a user interface program like FIGMA or Adobe XD, please note that before generating a PNG image, you must activate in the program:
Ignore overlapping layers.
Include bounding box.
Because if you donāt activate those two options, AppGyver Assets will detect the metadata of the image that something is not right, and will not take that image as a PNG even if it is read as a PNG.
Whereas if you work the images with Affinity Designer, Affinity Photo, Affinity Publisher, Gimp, Inkscape, etc, you wonāt have the āInclude Bounding Boxā problems, because the other programs are so advanced, internal codes can be generated inside of an image.
Another cause is to reconfigure Image Resources and upload the images again with the exact dimensions and make sure that the images are PNG or JPG when uploading them for the same reasons as above:
Icons
Presentation screens
Notification Icons
It may also be that it is deprecated in the REACT NATIVE programming and the error is āAapt2ā because in Android Studio it is deprecated and it was also generating such errors. That is why you have to reload these well-organized images and thus on Android where the problem generates the most, it can be solved.
1 Like
Unfortunately it is the very same with me. UNBELIEVABLE