Closed licaon-kter closed 4 months ago
@linsui @licaon-kter What's the meaning? I can't understand, what should I do?
@realOxy was this apk https://github.com/realOxy/M3UAndroid/releases/tag/v1.14.0-alpha06 really built from https://github.com/realOxy/M3UAndroid/commit/9d6211a9d7bf4dc5e0afee8e954b03344aca3b5a ?
If so... maybe try to rebuild it from command line, but first clean up any caches. Put the APK here or there and ping us to retest
@licaon-kter oh sorry, let me push all local commits and release a new version now.
@realOxy was this apk https://github.com/realOxy/M3UAndroid/releases/tag/v1.14.0-alpha06 really built from 9d6211a ?
If so... maybe try to rebuild it from command line, but first clean up any caches. Put the APK here or there and ping us to retest
Hi, I have released a new one. Based latest commit.
@licaon-kter Do I need to close this issue before ci can be re-executed?
We'll retest and close if confirmed
still fails https://gitlab.com/fdroid/fdroiddata/-/jobs/5936278922#L1104
How can I look for their difference
The APK is in right sidebar Browse -> tmp -> https://gitlab.com/fdroid/fdroiddata/-/jobs/5936278922/artifacts/file/tmp/com.m3u.androidApp_92.apk
diff log: m3u92.log
All those const
sound like https://gitlab.com/fdroid/fdroiddata/-/issues/3138
@licaon-kter It means I should build it in compose compiler 1.5.6 ? π€ https://github.com/realOxy/M3UAndroid/blob/93a55c1a0e7f21ca11bf3e5c6e9b63f221323d0c/gradle/libs.versions.toml#L40
If you can build an APK with that we could test
@licaon-kter released: https://github.com/realOxy/M3UAndroid/releases/tag/v1.14.0-alpha08
Since M3U 1.13.6 already uses complier 1.5.7, that shouldn't be the problem.
Since M3U 1.13.6 already uses complier 1.5.7, that shouldn't be the problem.
This software has never been successfully uploaded to f-droid before. Were the previous builds not affected by the compose compiler?
1.13.6 is the first version which is just published.
1.13.6 is the first version which is just published.
Oh, sorry. I just noticed this
building 1.14.0-alpha09 locally now
diff log :(
@licaon-kter why...
Is your apk built with GitHub Action?
Is your apk built with GitHub Action?
No, I built them in my own Mac, the GitHub action is merged from other contributors. It may be useless to repository or not(I am not sureπ). I have not studied GitHub action :(
Currently it builds the debug apk. Maybe we can try building the release apk with it and compare it with the fdroid apk. https://github.com/realOxy/M3UAndroid/blob/master/.github/workflows/android.yml#L27
Currently it builds the debug apk. Maybe we can try building the release apk with it and compare it with the fdroid apk. https://github.com/realOxy/M3UAndroid/blob/master/.github/workflows/android.yml#L27
Does it means I should change it to androidApp:assembleRelease ?
Do I need to publish a new release after changing it?
Does it means I should change it to androidApp:assembleRelease ?
Yes.
Do I need to publish a new release after changing it?
No, we just need to check the apk.
@linsui Hi, I have pushed it. Yesterday I merged a PR which has an android resource file changed and a fastlane metadata file changed, I just revert the android resource commit.
Your apk is in https://github.com/realOxy/M3UAndroid/actions/runs/7551132575/artifacts/1174212234. Our apk is in https://gitlab.com/linsui/fdroiddata/-/jobs/5945007947/artifacts/file/tmp/com.m3u.androidApp_94.apk. They have lots of diff. Weird...
@linsui What compare tool you used
I compared them in android studio
Use apktool to disassemble each APK first, remove META-INF, original and apktool.yml, then use diff -ru
or better yet diffoscope
between the folders.
Or just feed the APKs to the diffoscope site :)
Hi, I use apktool d, remove META-INF, original and apktool.yml, and use pkgdiff -d. Get this result:
which apks did you compare? links pls
Yup confirmed the same difference locally
β β --- m3u_94_githubci/unknown/kotlin-tooling-metadata.json
β βββ +++ com.m3u.androidApp_94/unknown/kotlin-tooling-metadata.json
β β β + "buildSystemVersion": "8.4",
β β β - "buildSystemVersion": "8.5",
so you are close :)
Also... makes us think about why your Mac is outputting un-repro builds :(
I build the apk by android studio -> build -> generate signed APK -> choose release build variant. Is this right?
Should be okay too, now you need to hunt for that difference, buildSystemVersion
buildSystemVersion is a cli command? I cannot execute it. My Mac is MBA M2 Sonoma 14.2.1
Oh sorry, It is Gradle. I forgot
Now I re-compare diff between the f-droid generated APK and Mac generated APK.
pkgdiff_reports.f-d_to_local.zip It seems only has one diff. https://en.wikipedia.org/wiki/.DS_Store
Which links?
Which links?
left: https://gitlab.com/linsui/fdroiddata/-/jobs/5945007947/artifacts/file/tmp/com.m3u.androidApp_94.apk right: Same commit in my Mac
I just push a new ci commit, maybe can solve the Gradle version mistake. We should restart ci and then check them again.
hmmmm, failed..
right: Same commit in my Mac
you mean https://github.com/realOxy/M3UAndroid/releases/tag/v1.14.0-alpha09 this one published 19h ago?
hmmmm, failed..
I guess you should run ./gradlew
right: Same commit in my Mac
you mean https://github.com/realOxy/M3UAndroid/releases/tag/v1.14.0-alpha09 this one published 19h ago?
I am not sure, but Now I get their Md5, They are different. Are they should has some md5?
hmmmm, failed..
I guess you should run
./gradlew
OK, let me try.
@linsui CI now passed. Should I publish a new version?
@realOxy just say which commit and post a link to the APK so we can test
@licaon-kter Based on latest commit: https://tmpfiles.org/3893637/androidapp-release.apk
ref: https://gitlab.com/fdroid/fdroiddata/-/jobs/5928486717#L1100
/LE: fyi https://gitlab.com/fdroid/fdroiddata/-/commit/104c2ec47f9d159c18bef8ead0a1b4e98a34deb8