#Fastlane Shorebird
1 messages · Page 1 of 1 (latest)
@shy coral wrote our fastlane config, it's possible we're putting the IPA in an unexpected location? https://docs.shorebird.dev/ci/fastlane/
I think we would need to learn more about what's going wrong. Could you share the error from fastlane?
I also have this issue, and it has been preventing my company from adopting shorebird for several months now. (I created an issue in July but there was no resolution, search: "shorebird_release fastlane plugin doesn't produce an ipa file when building for ios").
There is no useful error. Usually what you actually get is something like e.g "version code already used: (code of previous release)" because it's just uploading an old ipa that wasn't built with shorebird. However, if you delete ios/Runner.ipa you don't get an error because fastlane's deliver just runs without uploading anything.
I am convinced at this point that shorebird actually doesn't build an ipa at all when using the fastlane plugin. I cannot find one anywhere. It generates a .xcarchive and .app in build/ios but never a .ipa.
Can you share your fastfile?
Yeah I'll clean up in a minute and share but actually made a bit of progress - do you know if --no-codesign is supposed to make it not build an ipa? I think it could actually be intended behaviour.
Now I'm trying to use build_app to convert the xcarchive to an ipa, but running into another error: pod file is out of sync with the sandbox. I know this error and it can usually just be resolved with pod install --repo-update but it's not working here, and it also doesn't fail with a non-shorebird build. Cleared every cache I can think of and it's still happening.
Not really relevant to OP's original issue now though, so I'll make a different one.