Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

:mergeDebugResources Failure



  • Why is the APK creation failing on a file that is part of the Android SDK? What can I do to resolve this?
    Clean builds don't work. I've tried opening the png file and saving as png in paint, as others have stated this resolved similar issues. I'm at a loss. Here is the "fail" portion of the build output.

    :mergeDebugResources
    Error: Failed to crunch file C:\Prj\build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug\android-build\build\intermediates\exploded-aar\com.android.support\support-compat\28.0.0-alpha1\res\drawable-xhdpi-v4\notification_bg_low_pressed.9.png into C:\Prj\build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug\android-build\build\intermediates\res\merged\debug\drawable-xhdpi-v4\notification_bg_low_pressed.9.png
    :mergeDebugResources FAILED

    FAILURE: Build failed with an exception.

    • What went wrong:
      Execution failed for task ':mergeDebugResources'.

    Error: Failed to crunch file C:\Prj\build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug\android-build\build\intermediates\exploded-aar\com.android.support\support-compat\28.0.0-alpha1\res\drawable-xhdpi-v4\notification_bg_low_pressed.9.png into C:\Prj\build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug\android-build\build\intermediates\res\merged\debug\drawable-xhdpi-v4\notification_bg_low_pressed.9.png



  • @ebonnett said in :mergeDebugResources Failure:

    Failed to crunch file C:\Prj\build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug\android-build\build\intermediates\exploded-aar\com.android.support\support-compat\28.0.0-alpha1\res\drawable-xhdpi-v4\notification_bg_low_pressed.9.png

    I should add that the file path does not exceed the 255 char limitation. The source path is 241 and the destination is 193 chars. This isn't even a file I have anything do do with. I assume it's Windows native control images, but I could be mistaken. Please help Obie Wan Kanobe, you're my only hope.


  • Moderators

    @ebonnett
    i once had the same issue. It was definitively vanished with one of the 2 following solutions. i can't remember anymore which one though.

    1. delete the whole build folder and build the apk again
    2. shorten the build path. Best start with the build folder name (build-RMS-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7_ce25e1-Debug)


  • @raven-worx Thanks. I changed my output directory and it did get me over that hump. They I got these errors listed below:

    ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontVariationSettings
    ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:ttcIndex

    I found the following post:

    https://stackoverflow.com/questions/49186095/ionic-error-in-declare-styleable-fontfamilyfont-unable-to-find-attribute-and?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

    Making the changes prescribed in the post in my gradle-wrapper.properties file fixed those issues by forcing an update (not sure what it updated).

    Thank you for the quick assist!



  • @raven-worx But one thing I don't quite understand is that the file paths were not exceeding 255. Perhaps something under the hood was exceeding th 255?


  • Moderators

    @ebonnett
    i dont know where this requirement in the chain comes from to cause this issue


Log in to reply