breezmobile
breezmobile copied to clipboard
Add .ipa file to github releases
Add .ipa file (ios app) to the releases as asset at github releases, which currently have only apk (android app) file: https://github.com/breez/breezmobile/releases
What's the purpose? Is there an open iOS?
Not sure about "open iOS" and side-loading story on apple devices, it might be possible?! also there is virtualization of iOS by corellium which might be used to install the app as well: https://github.com/corellium/corellium-api#async-installpath-progress
Other purposes and usage of published .ipa besides installing it on device/virtualization are:
- Reproducible builds, see this comment and issue for more details to understand why publishing the .ipa is needed: https://gitlab.com/walletscrutiny/walletScrutinyCom/-/issues/149#note_537109159 this is the primary objective for me as I plan to look at the situation of Reproducible builds in source-available bitcoin wallets on iOS.
- looking at the file content after unzip, might report issues if found some during so
- comparing the content of .ipa between versions with diffoscope https://diffoscope.org/
And there probably other usages as well..
There's an open issue on reproducible builds.
The issue about reproducible builds at #247 ask about android, you already publish .apk in releases this issue is about publishing .ipa file as well.
regarding reproducible builds the current review at walletscrutiny https://walletscrutiny.com/android/com.breez.client/ show this app as FTBFS/missing-tags.
The missing steps are adding a build script (better as a Containerfile/Dockerfile) which build the apk and more clear build instructions, I tried to write the script myself but failed to build the breez.aar, thus also asked for you to publish it as well in #479
I wrote Containerfile that built Android app apk in: https://github.com/breez/breezmobile/issues/247#issuecomment-864363933 Still publishing of breez.aar #479 is needed (to ensure it's reproducible by itself & easier building for others by reusing it precompiled) And for reproducible builds in iOS publishing of .ipa file is needed which is what this issue is about.
It could also be nice to configure Github Actions so we can easilly run build also on forks to get ipa even without setting up dev environment. Then we can run it in a Simulator.
Use-case: I would translate app to Czech, but learning how to build Flutter is too big barrier for me.