[Bug]: F-Droid can't build

[licaon-kter]

在使用的时候发生了什么 Bug ？

Binary files /tmp/tmplkk02w5i/tmp_binaries_com.predidit.kazumi_105072.binary/content/lib/arm64-v8a/libflutter.so and /tmp/tmplkk02w5i/_tmp_tmplkk02w5i_sigcp_com.predidit.kazumi_105072/content/lib/arm64-v8a/libflutter.so differ

sounds like the Flutter version used to build your APK does not match the one in the submodule

ref: https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/9137318111#L6266

您在使用哪个操作系统？

Android

请具体提供设备、版本号等信息。

（选填）一些与 Bug 相关的硬件信息。

No response

日志信息

-

提交前确认

• issue 列表中，没有我发现的这个 Bug
• 我正在使用最新版本的 Kazumi

[Predidit]

This issue is very strange. We indeed synchronized the git submodules before releasing the new version. Currently, flutter is at commit 35c388afb57ef061d06a39b537336c87e0e3d1b1, which is the same as the stable branch in the official flutter repository. Our build script outputs the SDK version during the build, and both Gitlab CI and GitHub Actions report version 3.29.0.

@ErBWs

What do you think about this issue? Should we try using srclib instead?

[ErBWs]

I really don't know how this happened. Since commit id is the same I don't think using srclib can solve this problem, there should be some other reasons

[Predidit]

@licaon-kter

Seems that 1.5.6 build failed too. I can't find it on F-Droid.

Could we get the build logs for version 1.5.6? That way, we can see what happened and whether it's related to the current error.

[licaon-kter]

1.5.6 built fine, will be published soon: https://monitor.f-droid.org/builds/log/com.predidit.kazumi/105062#site-footer

and the CI at update time: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/19393/pipelines

[Predidit]

@ErBWs

I think maybe it's related to flutter monorepo.

Seems that flutter don't have independent flutter/engine repo any more since 3.28 beta.

Let's try using srclib as part of our debugging process.

[ErBWs]

https://gitlab.com/fdroid/fdroiddata/-/jobs/9141863246#L6313

@Predidit I think this is a flutter side issue

[licaon-kter]

from a chat with @linsui

how about we use submodules BUT instead of using the CI provided Flutter you use the submodule Flutter to build too?

[licaon-kter]

here: https://github.com/Predidit/Kazumi/blob/main/.github/workflows/release.yaml#L52

use: run: fastlane/.flutter/flutter build apk --split-per-abi or something

[Predidit]

I don't think this approach is appropriate, as it contradicts the purpose of the fastlane folder. In my view, the files in fastlane should only affect Android builds, and this could lead to discrepancies between GitHub CI and our development environment. I am trying to track down the origin of libflutter.so—it appears to be a prebuilt binary from Google.

[ErBWs]

I've suggested this operation here.

#587 (comment)

but we've tried using submodule and srclib in metadata and both failed, I think it will not make any difference

[linsui]

When we run flutter from the flutter repo, it should automatically fetch the flutter package with corresponding version. But it fetches a wrong version for flutter 3.29.0. I'm not sure why this happens yet.

[Predidit]

We should be able to retrieve detailed information about the Flutter version currently in use within GitLab CI, just like this.

1896673

https://github.com/Predidit/Kazumi/actions/runs/13331237800/job/37235617435

[licaon-kter]

as it contradicts the purpose of the fastlane folder.

who forces you to put something in the fastlane folder? not sure I follow 😄

as said, we need both CIs, yours and ours, to run with the same Flutter, and the best way is to run from the folder that you control

not F-Droid srclib, nor Github image random version

[ErBWs]

In flutter repo, branch stable's commit was completely changed when 3.29.0 is released. I cannot simply use git pull to update my local environment. Don't know what happened to it. Though I think it's not the reason.