Version: 1.9.12: Message: Unknown error, contact support for more details. IOS Build error

I am receiving this error message when attempting a build for my IOS App. I did manage to get past the earlier certificates problems, but I am not sure how to progress past this one. I have reviewed the log file which ends with the following paragraph. Any help appreciated!

[SQSListener] errored job was: {“id”:147568,“application_id”:201953,“user_id”:439695,“status”:“error”,“result_type”:“standalone_appstore”,“queued_at”:null,“finished_at”:null,“delivered_at”:null,“created_at”:“2020-07-27T23:58:51.315Z”,“updated_at”:“2020-07-27T23:58:51.315Z”,“error_at”:null,“platform”:“ios”,“version”:“version_skunkworks_1_0”,“edge”:false,“hidden”:false,“client_branch_id”:325,“metadata_json”:null,“app_id”:99732,“release_target_id”:null,“version_is_latest”:true,“client_branch”:“1.9.12”,“job_log”:[“2020-07-27 23:58:51 UTC - buildservice-host-16.appgyver - started job”,“2020-07-27 23:58:51 UTC - buildservice-host-16.appgyver - NonPackaged build, nothing to prepare”,“2020-07-27 23:58:51 UTC - buildservice-host-16.appgyver - Sending job to queue for the latest version”],“hosts_that_started_to_build_this”:[“buildservice-host-16.appgyver started at Tue Jul 28 2020 03:01:55 GMT+0300 (Eastern European Summer Time)”,“buildservice-host-16.appgyver started at Tue Jul 28 2020 03:06:55 GMT+0300 (Eastern European Summer Time)”,“buildservice-host-16.appgyver started at Tue Jul 28 2020 03:11:56 GMT+0300 (Eastern European Summer Time)”],“retries”:4}
[SQSListener] uploading build error log to S3

Looking at this now!

Could it be failing because my Version Code was not an Integer? I think I might have used 1.0.0 but have since seen examples of an Integer being used in the field. Eg 1

For iOS, semver-style version numbers are alright, and Android has a public-facing version number that’s text too – Android’s internal version code does need to be an integer. We pinpointed the issue (one of the asset URLS that the build service caches for packaging into the binary didn’t return HTTP headers in the response, which crashed the build) and are working on a fix.

Thanks Harri, do you have any time frames for the fix?

Are there any changes I can make to how I reference the assets to workaround this problem?

This is fixed with build service client version 1.9.17.

However, AFAIK there were still some issues with the provisioning profiles for the build, so I’d recheck the whole bundle ID/distribution cert P12/provisioning profile combo one more time.