Open IzzySoft opened 1 month ago
@dstark5 you're still around?
Yes @IzzySoft sorry for the delayed response
Hey, are you guys going to fix ( no available mirrors )? I can't download a single book?
@dstark5 thanks for your response! Do you need additional details from our end (for the differing dex)?
@droidjedininja please don't hijack issues not related to your question :wink: It would be much preferred if you could open your own issue.
Sorry bout that. Wasn't trying to hi-jack your space. I opened my own Issue, thanks.
Thanks @droidjedininja! Helps to keep things clear :wink:
@dstark5 could it be you build on Windows? libapp.so
e.g. contains a string file:///C:/Users/rog/StudioProjects/Libgen/.dart_tool/flutter_build/dart_plugin_registrant.dart
…
Hey, are you guys going to fix ( no available mirrors )? I can't download a single book?
Hey Hi👋, The issue will be fixed within a couple of days, Thank you
Thanks @droidjedininja! Helps to keep things clear 😉
@dstark5 could it be you build on Windows?
libapp.so
e.g. contains a stringfile:///C:/Users/rog/StudioProjects/Libgen/.dart_tool/flutter_build/dart_plugin_registrant.dart
…
Yes @IzzySoft
Aw… OK, guess then we have no chance to match the paths – and thus cannot achieve reproducible builds. Just to make sure I didn't miss something: cc @obfusk
You could try setting build_repo_dir: /C:/Users/rog/StudioProjects/Libgen
and build_home_dir: /C:/Users/rog
. It could work if the embedded paths are all file:
URLs.
Nope, unfortunately not:
useradd: invalid home directory '/C:/Users/rog'
useradd: invalid home directory '/C:/Users/rog'
Ah. That would require some adjustments to provisioning then. But you could try android_home: /C:/Users/rog/sdk
, build_repo_dir: /C:/Users/rog/StudioProjects/Libgen
and keep build_home_dir
as usual.
Sorry, that doesn't work either:
+ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/C:/Users/rog/sdk/cmdline-tools/12.0/bin
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/C:/Users/rog/sdk/cmdline-tools/12.0/bin
+ yes
+ sdkmanager --sdk_root=/C:/Users/rog/sdk --licenses
/scripts/provision.sh: line 30: sdkmanager: command not found
+ true
Colon is the separator in PATH
, so android_home
gets split into two separate entries there.
@dstark5 I've just chatted with Fay to see what options are left. We tried some more – but from our end, we can't get it built reproducibly; the only remaining option would be if you could build on Linux. You're welcome to use Fay's rbtlog for that (we could give you our build recipe for that to get you started), which would almost guarantee RB then.
As RB is not mandatory at IzzyOnDroid (though highly recommended), we leave the decision to you and of course accept it if you say that's asked too much. Just let us know please what you decide.
Thanks a lot for having us supported up to here!
Hi @IzzySoft 👋 I've mistakenly changed the app version build number to 1.0.7+1 which haven't triggered any build on the izzyOnDroid now I have changed the build number to +10 but still the build isn't triggered
As it isn't set up for RB, there are no builds triggered here (the APKs for the repo are taken directly from your releases, signed by you). So what build do you mean? If for RB, until set up that's done manually. And we'd need an APK from you plus the matching tag/commit it was built from.
I've checked your app if its build is reproducible (see: Reproducible bulds, special client support and more in our repo), but while I was able to successfully generate the APK by manually specifying the Flutter version (having flutter as a submodule in your git repo would eliminate the manual step here), the differences to the one provided at your latest release were huge. Which is at least partly due to Flutter embedding the build paths into its native libs (could you please let me know the path you are building in?) – but seemingly the APK here was also build from a commit other than the tag points to.
Here's the APK diff:
As pointed out above, the diff in the
*.so
can most likely be eliminated if we use the same build path here that you have. I gladly try another run if you can provide me the mentioned details (build path and commit hash).We'd appreciate if you could help making your build reproducible. We've prepared some hints on reproducible builds for that.
Looking forward to your reply!