I had the same issue, because of an update from Apple, my provisioning profile was invalid. I recreated dist certificate and provisioning and uploaded to the build service, then it was working.

I got a new error. So I suppose you guys are working on this.

AB version: 1.7.8

COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/q8wensh8i96sgmhv7vhd3vdx0192?response-content-disposition=attachment%3B%20filename%3D%22assets.zip%22%3B%20filename%2A%3DUTF-8%27%27assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230216%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230216T170736Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=3cced678702cd2e2a935ec0f2fdd1fd6d9d636090a783965cca8826703bdc6f8 npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.6.35 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-467612\""

FAILED with ERROR:

│ [ error ] [export] COMMAND:

xcodebuildOTHER_CODE_SIGN_FLAGS=--keychain AppGyver-467612 -workspace /private/var/folders/pf/p5g2vb2j0yx1x6vlmxdppc700000gn/T/467612-ios-270228/platformBuilds/standalone_ios/RNVApp.xcworkspace -scheme RNVApp -sdk iphoneos -configuration Release archive -archivePath /private/var/folders/pf/p5g2vb2j0yx1x6vlmxdppc700000gn/T/467612-ios-270228/platformBuilds/standalone_ios/release/RNVApp.xcarchive

FAILED with ERROR:

CreateBuildDirectory /var/folders/pf/p5g2vb2j0yx1x6vlmxdppc700000gn/T/467612-ios-270228/platformBuilds/standalone_ios/DerivedData/RNVApp/Build/Intermediates.noindex/ArchiveIntermediates/RNVApp/BuildProductsPath/Release-iphoneos/ReactNativeExceptionHandler

cd /var/folders/pf/p5g2vb2j0yx1x6vlmxdppc700000gn/T/467612-ios-270228/platformBuilds/standalone_ios

.........

Carlos Gabrielli - Try step #2? or just wait it out. I have found that can work at times.

For the first time in a while I was able to build my ios project. However, it immediately errored out when uploading via transporter due to the transparent pngs. So yea, if anyone is looking after the fact, AppGyver is not doing any image checks (maybe sizing ones). If you don't want to waste time in a design software, convert to jpg and back to png. I believe that will fix it.

NOTE: Skip my overview of things below if you want to the main item I found that seemed to 'maybe' cause an issue recently. If you are working through the issue, fix #2 if it is one and then go back to #1.

Not sure if we will ever here from a dev. I assume these open forums are more to push all the people with problems together to try and solve it together first. Then their dev team might come in depending on the severity of the problem. But only an assumption based on turn around times I have seen with even responses.

So back to the fact finding:

I use Firebase (users, db, and messaging) and Appgyver

Obviously not being able to build ios is a massive issue. And with a generic message like the above it could mean lots of things.

- Your cert and setup could indeed be wrong. That is always an option I suppose but not the only reason.

- Links that helped me work back through creating these once again

If you need push notifications -> https://forums.appgyver.com/t/push-notification-tutorial-for-ios-firebase-cloud-messaging/18980

One of the better overall articles about setting them up -> https://luismts.com/distribution-certificates-p12-files-provisioning-profiles/

I used this for a reminder of creating Push notification cert for Firebase (Step #9) -> https://support.magplus.com/hc/en-us/articles/204972657-iOS-Reference-Updating-Your-Provisioning-Profiles-to-Accept-Push-Notifications

There is atleast one gap in most articles (minor differences) so try to compare them as you work and hopefully you will have a good result here.

I then found this : https://developer.apple.com/forums/thread/662300

TLDR: Apple has updated Developer Relations Intermediate Certificate. Just download the certificate from here and install it. If the it doesn't works have a look on https://developer.apple.com/support/expiration/

I hadn't updated my laptop / certs in some time. This is definitely not something I work on much so not something that naturally I get reminded to do.

Did you start seeing errors around these times:

"The Apple Worldwide Developer Relations Intermediate Certificate has a version that’s set to expire on February 7, 2023 and a renewed version that’s set to expire on February 20, 2030. The renewed version is used to sign new software signing certificates issued after January 28, 2021. Remaining service certificates will be updated on January 27, 2022. See the Apple Push Notification Service SSL Certificates section for details."

So long story,

Download the following

Intermediate cert: https://www.apple.com/certificateauthority/AppleWWDRCAG3.cer

Push notifications: https://www.apple.com/certificateauthority/AppleWWDRCAG4.cer

I believe this is all correct as I do see that my new certs are valid now.

I will keep testing and hopefully the most recent error was just a fluke but who knows.

Note:

Failed: 8:34 AM EST

Testing again

We have also been experiencing this issue for the last days. I am going to try and get brand new certs but they had all been working fine up until recently. Are there ever any failures due to browser issues when uploading things? It just feels a bit random when things fail

Same error. Builds were fine this morning but started failing after 14:00 SAST. Also gives the error of signing certificate.

Kudos, you mentioned this tutorial on another bug report post, which resolved the iOS distribution certificate upload error for me :)

My guess is if everyone follows this guide regenerating and replacing their existing certificates from Apple then it should work.

The only difference we made from the guide was to choose 'iOS Distribution' when choosing the certificate type in the Apple portal.

Thanks again

I have the same problem. Tried to build today and after two very long hours of it being queued, I got an error message saying "error: No signing certificate "iOS Distribution" found: No "iOS Distribution" signing certificate matching team ID "SB3ZV4P7C8" with a private key was found. (in target 'RNVApp' from project 'RNVApp')".

Is this solved or what's the status and why can't we build successfully?

Same Problems since 4 days.

Seems like its an issue again. Got the same error on 26 September 2022.