Gitlab pipeline - checkupdate stage failed

Hi, this is my 1st F-droid app I made in Flutter. It has 2 tags v1.0.0 and v1.1.0. I’ve no idea why checkupdate stage is failing but apparently get the new VersionName
(v1.1.0), VersionCode (2), Commit, CurrentVersion and CurrentVersionCode from the GitHub tag correctly.

The latest pipeline:
https://gitlab.com/boredcodebyk/fdroiddata/-/pipelines/883607180

My app’s metadata:
https://gitlab.com/boredcodebyk/fdroiddata/-/blob/bored.codebyk.mint_task/metadata/bored.codebyk.mint_task.yml

And the source code:
https://github.com/boredcodebyk/mint_task

I appreciate if you could have a look. Thanks.

Just update the block with the new version… :slight_smile:

I’ve updated it for you: update, scan deps (3328bf94) · Commits · K / Data · GitLab

How about adding flutter as a submodule? Else the build will fail you it will need a newer Flutter version and we need to manually intervene, but with a submodule in your repo, you just update it and it will just work.

Not sure how to start the pipeline in your repo… :frowning:

RIght, it’s here: New App: bored.codebyk.mint_task (!13106) · Merge requests · F-Droid / Data · GitLab

Thank you so much for the big help. I have few questions, do I have to manually add new blocks for future updates? Also I tried submodules method before opening the merge request, but the pipeline failed. I’m guessing my repo don’t have Flutter as submodule and I’ve no idea how to add Flutter as sub (I looked up about it before)

the build machine does not have Flutter… you add it via the submodule: Git - Submodules to your app source repo

then you/me/we adapt the recipe: templates/build-flutter.yml · master · F-Droid / Data · GitLab

Here is an update: I added submodules for tag v1.1.0 and also updated metadata with v1.1.0 using submodules and v1.0.0 same as before.
But now the build stage fails. According to the log, it does successfully build v1.0.0 (which has srclibs) but show ERROR: Could not build app bored.codebyk.mint_task: Can't build due to 6 errors while scanning for v1.1.0. Is there any way to fix this?

Lets talk there instead :slight_smile:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.