Fastlane deployments broken

[digitaldan]

Not sure whats going on since this was working until a few days ago....... but now our test flight beta builds are failing to sign. Our legacy app had another build issue so i cherry picked the gemfile lock from develop and a build is running right now, but i would expect to see the same issue with it.

@timbms @weakfl have you seen this error before ?

https://github.com/openhab/openhab-ios/actions/runs/10877429259/job/30178785803

 ::error file=/Users/runner/work/openhab-ios/openhab-ios/openHAB.xcodeproj::No Accounts: Add a new account in Accounts settings. (in target 'openHABIntents' from project 'openHAB')
[04:32:52]: ▸ /Users/runner/work/openhab-ios/openhab-ios/openHAB.xcodeproj: error: No profiles for 'org.openhab.app.openHABIntents' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'org.openhab.app.openHABIntents'. (in target 'openHABIntents' from project 'openHAB')
[04:32:52]: ▸ note: Disabling previews because SWIFT_VERSION is set and SWIFT_OPTIMIZATION_LEVEL=-O, expected -Onone (in target 'openHABIntents' from project 'openHAB')
[04:32:52]: ▸ ::error file=/Users/runner/work/openhab-ios/openhab-ios/openHAB.xcodeproj::No Accounts: Add a new account in Accounts settings. (in target 'openHAB' from project 'openHAB')
[04:32:52]: ▸ /Users/runner/work/openhab-ios/openhab-ios/openHAB.xcodeproj: error: No profiles for 'org.openhab.app' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'org.openhab.app'. (in target 'openHAB' from project 'openHAB')
[04:32:52]: ▸ note: Disabling previews because SWIFT_VERSION is set and SWIFT_OPTIMIZATION_LEVEL=-O, expected -Onone (in target 'openHAB' from project 'openHAB')
[04:32:52]: ▸ ::warning ::Run script build phase 'Run Build Tools' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'openHAB' from project 'openHAB')

[timbms]

Not seen so far
I have tried uploading an archive to appstore connect for TestFlight. This was successful

[digitaldan]

Actually i think this may have been transient , running it again now has different results.

[timbms]

Testflight seems to be still broken

[timbms]

Now there are complaints about the xcode version used. Is this because of the release of iOS 18 and Xcode 16?

[digitaldan]

Good guess , not sure , I'm away from my computer , will look tomorrow . Also the "none" option I added for not bumping the version is not working , but that's another issue I'll debug tomorrow , but is unrelated to the current signing issues

[digitaldan]

so this is odd, after updating the gem lock file on the legacy build, signing oddly does work for v1, but we get this different error when trying to upload to Apple. I'm not sure what this is about, i assumed the SDK is tied to the version of Xcode, which i think we specify as "latest" so that should be 15?

[altool] 2024-09-16 19:54:32.772 *** Error: Asset validation failed Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. (ID: c5c92a01-3086-4bdc-9cd4-406708f960e2) (90534)

[digitaldan]

Is this because of the release of iOS 18 and Xcode 16?

Hmm, maybe indeed thats the error we are seeing with the v1 build too. I wonder if this is something we may need to wait out for a few days and see others have the same issues and some workarounds get published? I guess i can just push builds manually from xcode for the time being.

[digitaldan]

fixed with #828