Farhan: build fails (due to missing resources?)
Trying to build v0.2.2 fails at :core:verifyReleaseResources:
Execution failed for task ':core:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
> Android resource linking failed
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:25: AAPT: error: attribute layout_constraintTop_toTopOf (aka ly.com.tahaben.core:layout_constraintTop_toTopOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:25: AAPT: error: attribute layout_constraintStart_toStartOf (aka ly.com.tahaben.core:layout_constraintStart_toStartOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:34: AAPT: error: attribute layout_constraintTop_toBottomOf (aka ly.com.tahaben.core:layout_constraintTop_toBottomOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:51: AAPT: error: attribute layout_constraintStart_toStartOf (aka ly.com.tahaben.core:layout_constraintStart_toStartOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:51: AAPT: error: attribute layout_constraintTop_toBottomOf (aka ly.com.tahaben.core:layout_constraintTop_toBottomOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:61: AAPT: error: attribute layout_constraintTop_toTopOf (aka ly.com.tahaben.core:layout_constraintTop_toTopOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:61: AAPT: error: attribute layout_constraintStart_toEndOf (aka ly.com.tahaben.core:layout_constraintStart_toEndOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:76: AAPT: error: attribute layout_constraintStart_toStartOf (aka ly.com.tahaben.core:layout_constraintStart_toStartOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:76: AAPT: error: attribute layout_constraintTop_toBottomOf (aka ly.com.tahaben.core:layout_constraintTop_toBottomOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:86: AAPT: error: attribute layout_constraintTop_toTopOf (aka ly.com.tahaben.core:layout_constraintTop_toTopOf) not found.
ERROR: /build/repo/core/build/intermediates/merged_res/release/mergeReleaseResources/layout/usage_widget_preview.xml:86: AAPT: error: attribute layout_constraintStart_toEndOf (aka
Could it be something was not checked in to this repo?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 35 (16 by maintainers)
Yepp, that builds – with a huge diff because of… oh, no more
zlib-ng? Let’s kick that out of the recipe then and try again…Yeah! 🥳 Congrats, that’s RB!!! Next release when? 😃
oh yes here app-release.zip
Soon 😀 (hopefully within the next three days)
Sorry, but unfortunately does not even build:
May I suggest you to check out that commit (9119da99e6b882eacee80477daa406a1168fc826) to a separate place, and try building from there yourself? You should then be able to reproduce the error – and hopefully find and fix the culprit 😉 Thanks!
Open JDK 17
Mac os 15.2
Which one? OpenJDK – or Jetbrains?
Our updater just picks what’s at the release, scans it, and (if all seems fine) publishes it – it does not check for RB. The latter is done by our builders, on a separate track. So a failed RB does not stop your (maybe urgent security) update from going live, it just keeps the “green shield” from coming up. Later, (some) clients might offer an option to only install/update confirmed RBs, so the choice is with the people (as it should be).
Btw: My guess for that PNG is that it is rendered from
res/mipmap-anydpi-v26/ic_launcher.xml; that should be easy to avoid by “forbidding” such action:For the TTF, I have no clue. That’s definitely a compression issue (same uncompressed size, same file hash – just different compressed size), no idea what causes that. What OS are you building on?
It’s MS, so it just goes by file extensions. Simply rename it to
*.zipand suddenly it’s fine 🤷♂️ But never mind, works this way as well.But it’s not RB. Here’s the diff:
Ad.ttfis strange: it’s identical when uncompressed (previous to last column: file hash), but the compressed size differs by a few bytes. That smells a bit likezlib-ngwas used instead ofzlib, but that cannot be as then all other files would be affected as well (tested: confirmed, it’s not that). Still, I cannot even get the compression level of the file viazipfile. Not sure what happened to that font.The PNG on the other side also differs when uncompressed. Could it be you use PNGCrunch or something like that? Those tools produce non-deterministic results. If so, for this I would have a hint. But if we cannot resolve the TTF file, that won’t help much…
Do you have any ideas there? Maybe let’s compare build environments: I’ve built the APK on Debian bookworm using JDK-17 and gradle at the command line. What did you use?
From the commit the tag points to: 876c925dc0ec76d7073d5ca5d1bd8b9f7c1c49e6
I can of course. Though it would be strange if that suddenly would work out. If the resources were missing at that commit, how should they suddenly show up? But then, strange things happen (non-deterministic builds), so let’s see… Nope, as expected, error remains.
I’ll take a look later tonight
@tahaak67 could you please take a look? ^^ (guess you’ve missed the notification for this)