Reproducible Build for v5.7.0 fails

[IzzySoft]

Which version of floccus are you using?

v5.7.0

How many bookmarks do you have, roughly?

n/a

Are you using other means to sync bookmarks in parallel to floccus?

n/a

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

n/a

Which version of Nextcloud Bookmarks are you using? (if relevant)

n/a

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Build succeeds, but is missing a file:

  -rw-r--r--  0.0 unx      407 b-      173 defN 1981-01-01 01:01:02 b105e29d assets/public/html/background.html
- -rw-r--r--  0.0 unx      775 b-      324 defN 1981-01-01 01:01:02 aaf16b91 assets/public/html/index.html
  -rw-r--r--  0.0 unx     1096 b-      400 defN 1981-01-01 01:01:02 7ac60b0d assets/public/html/options.html

Unfortunately, the vcsInfo embedded in the APK is not providing the commit the APK was built from (META-INF/version-control-info.textproto just states generate_error_reason: NO_SUPPORTED_VCS_FOUND), so we cannot check if the commit matches. We assume so, though, as you are using the Github CI to build your release (and the action file hasn't been changed since the last release). Also, there is no newer commit than the tagged one.

Expected Behavior

build succeeds and results in an identical APK (as before).

To Reproduce

Build with rbtlog and the following recipe (which succeeded for previous releases):

  - tag: v5.7.0
    apks:
      - apk_pattern: floccus-build-.*\.apk
        apk_url: https://github.com/floccusaddon/floccus/releases/download/$$TAG$$/floccus-build-$$TAG$$.apk
        build:
          - wget -q -O /tmp/nodejs-lts.tar.xz -- https://nodejs.org/dist/v22.18.0/node-v22.18.0-linux-x64.tar.xz
          - sha256sum -c <<< 'c1bfeecf1d7404fa74728f9db72e697decbd8119ccc6f5a294d795756dfcfca7  /tmp/nodejs-lts.tar.xz'
          - tar xf /tmp/nodejs-lts.tar.xz -C /opt
          - export PATH="${PATH}:/opt/node-v22.18.0-linux-x64/bin"
          - npm install
          - npx gulp
          - npx cap sync
          - cd android
          - ./gradlew assembleRelease
          - mv app/build/outputs/apk/release/app-release-unsigned.apk /outputs/unsigned.apk
        build_home_dir: /build
        build_repo_dir: /build/repo
        build_user: build
        provisioning:
          android_home: /opt/sdk
          build_tools:
          cmake:
          cmdline_tools:
            version: '19.0'
            url: https://dl.google.com/android/repository/commandlinetools-linux-13114758_latest.zip
            sha256: 7ec965280a073311c339e571cd5de778b9975026cfcbe79f2b1cdcb1e15317ee
          extra_packages:
            - xz-utils
          image: ubuntu:jammy
          jdk: openjdk-21-jdk-headless
          ndk:
          platform:
          platform_tools:
          tools:
          verify_gradle_wrapper: true

Debug log provided

• I have provided a debug log file

[github-actions]

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

[IzzySoft]

Hi Marcel, as the 24h window closes now and we have no solution, we'll have to mark v5.7.0 "RB failed" now. Hope we can find out before the next release what went wrong here, so that will get the green shield up again then.

[marcelklehr]

Hey, sorry, I haven't had time to look into this so far.

[IzzySoft]

No blame meant! Just commented that so you don't wonder. I know what a "full schedule" means…