03-26-2024 12:03 PM
Peace. This is the first iOS build after moving from AppGyver. App Store Distribution Certificate & Provisioning are both valid & unchanged from last successful build on 2024/11/10. Please advise ASAP. Thank you...
The error message follows:
Troubleshooting Tips:
The certificate in use is not a valid iOS distribution certificate. It should match Team ID "7HD3HFC9Z8".
Runtime version: 4.9.201;
AB version: 2.1.14
COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.201 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-51820\""
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.201 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-51820\""
04-07-2024 8:46 PM
04-07-2024 11:51 PM
04-16-2024 11:19 AM
04-17-2024 8:51 AM
04-18-2024 1:49 PM
@SeifEldin you built in Runtime version: 4.9.201, have you tried it with 4.9.218? If not, can you try it to see if the problem persists?
04-18-2024 2:58 PM
@MaiaraEllwanger, yes I did several times but to no avail! Last build attempt was at: 4/11/2024, 10:49:28 PM
04-19-2024 12:04 PM
04-19-2024 12:29 PM
04-19-2024 12:53 PM
Sure, my tip is:
The certificate in use is not a valid iOS distribution certificate. It should match Team ID "ZWQ5SQ57W4".
and my error is:
Runtime version: 4.9.218; AB version: 2.1.14COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.218 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.218 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
04-22-2024 6:41 AM
Maybe some of you can help me.
I am trying to compile using the iOS distribution certificate generated online at developer.apple.com but I am never asked to set any password for this certificate.
At this point, I think the problem is this: how do I create the certificate with password?
Thank you all!
a month ago
Respectfully, I don't fully understand your question, whether you mean adding a password to an existing certificate, which I don't how or if even possible, or you would like to create a new certificate with a password, in which case the following should be helpful (as suggested by old AppGyver's IOS builds - Build - Distribute😞
Hope this helps…
a month ago - last edited a month ago
That definitely helped me a lot, thank you very much.
Now, when I try to get my iOS build I no longer get TIPs but only the following error, how can I fix it?
______
Runtime version: 4.9.218;
AB version: 2.1.14
COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.218 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.218 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
Can someone please help me?
a month ago
@MaiaraEllwanger, please, is it possible, somehow, to get more information from the compilation error? I can't compile the iOS version and I really don't know how to intervene to solve my problem.
I assume it is not a "code" problem: the Android version compiles (and works) perfectly.
Does anyone please know if there is a way to ask for "verbose" compilation?
Thank you all.
a month ago
Well, that's the original topic of this thread.
According to @MaiaraEllwanger, we're awaiting feedback from SAP developers already working on the issue for over a month now...
a month ago
a month ago
Yes, @MaiaraEllwanger, thanks, i succeded in uploading the right certificates: i have no TIPs now in my error response.
4 weeks ago
How did you get it resolved? My certificates are valid but I'm getting the same error
3 weeks ago
Unfortunately, I have not solved it.
Even though my certificates are now valid, I still get the same error too.
I am here to see if there is a way to request a more verbose compilation, just to see where the problem is, because, as it is, it's impossible to make corrections.
Or if someone please who can provide some kind of support.
3 weeks ago
@MaiaraEllwanger, problem still persists with runtime version: 4.9.259. Last build attempt was at: 4/29/2024, 9:06:39 PM
3 weeks ago
Same here also with Runtime Version 4.9.259:
Runtime version: 4.9.259;
AB version: 2.1.14
COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.259 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.259 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
3 weeks ago - last edited 3 weeks ago
Hi, I´m having the same problem too, my build is for Android, the keystore, alias and password are correct, but I´m getting this error:
History
Runtime version: 4.9.259;
AB version: 2.3.0
COMMAND:
NODE_OPTIONS=--max-old-space-size=16000 npxrnv export -p android -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.259 -r
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p android -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.259 -r
3 weeks ago
@MaiaraEllwangeri'm facing the same issue also with the new runtime version 4.9.260.
Please, I need to know where I am going wrong.
I can't do anything if I don't know the nature of the problem.
Runtime version: 4.9.260;
AB version: 2.1.14
COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.260 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
FAILED with ERROR:
Command failed with exit code 1: npx rnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.9.260 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-72867\""
3 weeks ago
@Alek I've got me resolved! I have no clue what fixed it exactly but here is what I did:
1. Recreated my p12 certificate (Make sure its password sealed)
2. Made sure the email associated with my certificate matches my admin email in Apple Developer (not sure if that matters but I was just trying everything)
3. Changed the name of my application when configuring the Build (Made sure to not use any special characters like "&")
And it worked! Good luck.
3 weeks ago
@MaiaraEllwanger, @AmgadAlamin. Unfortunately, that didn't work for me!
I've tried different combinations of:
but the problem still persists with runtime version: 4.9.260. Last build attempt was at: 5/3/2024, 1:55:18 AM!
That's getting really frustrating.
Awaiting your reply impatiently @MaiaraEllwanger. Thank you…
3 weeks ago
Well, okay, it looks like I finally succeeded in compiling my app!
I can't say exactly which of these was the solution to my problem but I was now able to upload my build to TestFlight.
I hope I can be of help to some of you!
3 weeks ago - last edited 3 weeks ago
@MaiaraEllwanger. My attempts included:
All to no avail!
The only remaining options are to:
But this would imply being identified as a new app by users (my app is about 2 years old now with over 50 updates). Also, that would be different from &roid's bundle identifier, causing inconsistent branding.
Again, the previous logic applies here, with the additional loss of code changes log!
I contacted Apple from the very beginning, & they denied any possible cause on their side, to my understanding of course.
So, with all due respect, there's a missing link here for the app built to be working before on all platforms but failing now after moving to SAP without any change on my side, either significant code change or certificate / provision profile. It's more like a bug with app building's cache or similar…
The problem persisted with runtime version: 4.9.260. Last build attempt was at: 5/5/2024, 3:25:56 AM!
Still awaiting your reply / advice impatiently. Thank you…
* I do realize that the compilation occurs server-side, but this error is seemingly illogical, so I'm trying illogical ideas, too.
2 weeks ago
@MaiaraEllwanger. Update: The problem has been resolved, without changing bundle ID nor app name.
The error was caused by a mistake on my behalf with applying the certificate in SAP build.
I'm terribly sorry for any unintentional inconvenience caused.
Thank you & God bless...
a week ago - last edited a week ago
Hi, could you please explain in more detail how you fixed it? I'm getting the same error:
"The certificate in use is not a valid iOS distribution certificate. It should match Team ID XXXXXXXXXX"
I recreated completely new P12 (iOS Distribution) and provisioning profile and uploaded them both in the build config and yet I still get the error repeatedly. I even made sure I had all of Apple's latest certs in my Keychain before creating the P12. Yes, I added a password to the P12. Any help would be very appreciated!
EDIT: ...aaaaannnnnddddd I figured it out. My error. When exporting the certificate in Keychain Access, I was right clicking on the private key and not the certificate. Whoops. Working now.