Closed linsui closed 2 months ago
Hi thanks for reporting error, version/tag 0.6.37 should be ok while the one with the version/tag problem was 0.6.36.1
Your apk is built from 8730755c0825a7af22d3b83e135cada83df3eea3. https://monitor.f-droid.org/builds/log/it.fast4x.rimusic/36#site-footer I guess you built the apk first then committed the change.
I’ll pay more attention to that, thank you.
So we skip 0.6.37? Or you rebuild the apk against the tag?
Yes skip because I can’t build from the specific commit.
:ok_hand:
reopen, you've tagged https://github.com/fast4x/RiMusic/releases/tag/v0.6.45.1 to f55affa8ac651175a1f426be2ab58861219e2658
but the APK was built from the older a553714caaff9e746e3fa58b29af5bf18c3ebeab ?
ref: https://gitlab.com/fdroid/fdroiddata/-/jobs/7445634123#L1483
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/06cf7a95cc9a3e8ecd4163508f6965afe35848c4
I have committed all code for resolving crash on 0.6.45 and builded with new tag 0.6.45.1
@fast4x are we lost in translation? :)
:) I added commits to created a new tag, that’s all I did.
Great... ok... and you did not build the APK from the Tag commit
why? that's up to you :)
what now? please build a NEW APK from the Tagged commit, or delete the Tag and re-Tag to the NEW commit
Friday I’ll do the new version, skip this version
0.6.46 build also failed. Which commit does it build from?
Hi, commit is https://github.com/fast4x/RiMusic/commit/f55affa8ac651175a1f426be2ab58861219e2658
There are new things,
Maybe that’s why you’re here?
https://gitlab.com/linsui/fdroiddata/-/commit/740797646364550b1da1f9bdef972a69ad739905 Can you move the tag to that commit then rebuild the apk from the tag?
Unfortunately can't reuse existing tag with other commit. I can create a new one and rebuild apk. Would be ok?
Please rebuild the apk from a commit. And please make sure it maych the tag next time. Maybe you can disable vcsInfo. :)
App rebuilded at specific commit (34689e1768679ecd590c437c012d7ccae303293d
) and added apk in existing tag 0.6.46 I've understand what was my error...
The apk is not reproducible. it.fast4x.rimusic_47.apk.zip
can you clean the cache and rebuild the apk?
Yes i do
Done and uploaded new apk
It's still not reproducible. I have no idea...
Then the problem is not that, i can create a new tag but i don't know other.
Is jdk changed?
No, it's same as before
@licaon-kter @linsui Maybe it fails because the gradle file contains two flavors? Can you configure the build to compile the flavour foss?
Flavour foss is default for F-Droid
Can you configure the build to compile the flavour foss?
will try, brb
trying foss
for https://github.com/fast4x/RiMusic/releases/tag/v0.6.46
==== detail begin ====
verification of APK with copied signature failed
Comparing reference APK to APK with copied signature...
Unexpected diff output:
diff -r /tmp/tmpqwr020mc/unsigned_binaries_it.fast4x.rimusic_47.binary/content/META-INF/version-control-info.textproto /tmp/tmpqwr020mc/_tmp_tmpqwr020mc_sigcp_it.fast4x.rimusic_47/content/META-INF/version-control-info.textproto
4c4
< revision: "34689e1768679ecd590c437c012d7ccae303293d"
---
> revision: "a68b94aa6aebaf279daa02b2d634f7b3b70bf006"
Binary files /tmp/tmpqwr020mc/unsigned_binaries_it.fast4x.rimusic_47.binary/content/assets/dexopt/baseline.prof and /tmp/tmpqwr020mc/_tmp_tmpqwr020mc_sigcp_it.fast4x.rimusic_47/content/assets/dexopt/baseline.prof differ
Binary files /tmp/tmpqwr020mc/unsigned_binaries_it.fast4x.rimusic_47.binary/content/assets/dexopt/baseline.profm and /tmp/tmpqwr020mc/_tmp_tmpqwr020mc_sigcp_it.fast4x.rimusic_47/content/assets/dexopt/baseline.profm differ
Binary files /tmp/tmpqwr020mc/unsigned_binaries_it.fast4x.rimusic_47.binary/content/classes.dex and /tmp/tmpqwr020mc/_tmp_tmpqwr020mc_sigcp_it.fast4x.rimusic_47/content/classes.dex differ
==== detail end ====
On next Friday I'll build new tag, so we can try again.
Thanks
New tag builded, flavour foss
Still not reproducible... Let's check it again:
Is the apk built with jdk 17 from https://github.com/fast4x/RiMusic/releases/tag/v0.6.47? Did you clean the cache before the build? Did you run any other commands before gradle assembleFossRelease
?
Yes, jdk 17, I'll clean cache and run command for rebuild apk.
before the command assemble.... I did not execute anything
The only difference from the last build played by F-Droid is the introduction of flavour foss and accrescent.
Which OS do you use?
Today re build with new tag for fix any bugs.
Which OS do you use?
Windows 11 with Android Studio
Can you also try rebuilding the apk out of AS?
From the command line?
Yes
If you agree I would test with the two apk files, could be he FDroid is compiling the flavor accrescent and finding the apk file foss, find it different?
I think isn't reproducible because it build accrescent and not foss...
Yes
yes I'll build from command line
https://gitlab.com/linsui/fdroiddata/-/jobs/7550604124#L427 We build the foss flavor.
https://gitlab.com/linsui/fdroiddata/-/jobs/7550604124#L427 We build the foss flavor.
Would be the gradle version? I see that fdroid use 8.6 I'll check it in my project.
I'm confused, i don't understand why not build.
I don't know, either... Maybe you can try rebuild 0.6.44 and check if the apk is changed.
Builded new tag v0.6.47.1 with vcsInfo disabled
It's reproducible finally! What's changed?
Steps to reproduce the bug
Your apk is built before you commit the last changes. This causes a small difference. See https://f-droid.org/en/docs/Reproducible_Builds/#vcs-info.
Expected behavior
Reproducible
Actual behavior
Not reproducible
Screenshots/Screen recordings
No response
Logs
No response
RiMusic version
0.6.37
Android version
12
Additional information
No response