I just created a new iOS build and ran it. It failed with this error message (seems to be related to the Cloud Build service itself):
21573: ! build of ‘default-ios’ failed. compile failed
21574: /BUILD_PATH/.rvm/gems/ruby-2.1.1/gems/bvr-1.1.2/lib/bvr/project.rb:383:in `publish_build’: Could not find .release.yaml in archive path. (RuntimeError)
Is this a known issue ? is there any known workaround ?
That line will show up for failed iOS builds currently, but isn’t the actual source of the failure. The actual error will usually show up just above that line in the full log. If you can’t track it down, PM me a link to your project and I’ll help investigate.
I am also getting this error, but I don’t see any other errors right above, although it does say something about “no identity found”. Could that be the cause of it? And why would that error show up, when the settings say that the credentials are correct and valid?
Apparently cloud builds are not so happy about ‘weird’ letters in names. I have the Danish letter ‘ø’ in my last name for the profile that was being used when we got the “no identity found” error. Today we made a build using another profile with no ‘weird’ letters in it and the build succeeded. It might of course be that there was something else wrong with the credentials I had uploaded with my profile, but it seems to be related to the ‘ø’ character. Especially since that ‘ø’ shows up as ‘J\xC3\xB8’ when I look in the cloud build log.
Our Cloud builds on iOS seem to fail for the same reason. Our certificates contain the letter “ö”. Since the logs do not report any errors, but the build fails at the end for no apparent reason. Local builds work just fine. Could someone please verify this issue?