iOS Building Error

[Jay-eem]

App 84376

History

Runtime Version: 4.11.132
Status: error

Queued at: 7/11/2024, 10:03:20 AM
Build ID: 31464

===========================================================
@Dan_Wroblewski 
@MaiaraEllwanger 
@marihirvi 

Runtime version: 4.11.132; AB version: 2.12.0COMMAND:
npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @sapappgyver/orchestra-template-standalone@4.11.132 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-84376\""
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.11.132 -r --xcodebuildArchiveArgs "OTHER_CODE_SIGN_FLAGS=\"--keychain\ AppGyver-84376\""

[Jay-eem]

@Dan_Wroblewski 
@MaiaraEllwanger 
@marihirvi 
Update on this. thank you

[Jay-eem]

Hi, Anyone facing same issue as mine? need urgent help on this. and what workaround did you do at least temporary solution? thanks 

[RAHUL1221]

Hey,

The error message you're encountering suggests that there was an issue while running the command to export and build your iOS app using the SAP AppGyver runtime version. Here are some potential causes and steps to troubleshoot the problem:

1. Dependency Issues: There might be missing or conflicting dependencies. Ensure that all required dependencies are properly installed. Run yarn install or npm install to make sure all packages are up-to-date.

2. Template Version: The specific template version @sapappgyver/orchestra-template-standalone@4.11.132 might have issues. Check if there are any updates or known issues with this version.

3. Xcode and Keychain Issues: The xcodebuildArchiveArgs parameter indicates a keychain issue. Ensure that the specified keychain (AppGyver-84376) is available and accessible. Verify that the keychain is unlocked and that the signing certificates are correctly installed.

4. Permission Issues: The command might require elevated permissions. Try running the command with sudo to see if it resolves any permission-related issues.

5. Environment Configuration: Ensure that your development environment is correctly set up. Verify that you have the correct versions of Node.js, npm, yarn, Xcode, and other tools.

6. Network Issues: Sometimes, network issues can cause package installation failures. Ensure that you have a stable internet connection and try again.

7. Logs and Error Messages: Check the detailed logs and error messages for more specific information about what might have gone wrong. The logs should provide more context about the failure.

8. Rebuild: Clean the build artifacts and try rebuilding the app. Sometimes, residual files from previous builds can cause issues. Run commands like npx rnv clean or manually delete the build folders.
   
   
   
   Can maybe check and recheck all the above points. there might be sometimes bugs in sap build **bleep** well. can try to rebuild again. or reconfigure all the authorizations.also can export your project and then remove sap build subscription from marketplace and re subscribe again.
   
   Thanks,
   Rahul

[Jay-eem]

Hi @RAHUL1221 . Thank you for this. but all of them can't do it on my side. maybe Appgyver developer can. but thanks.

[Jay-eem]

Hi @beapasch . can you help me?. I'm facing this issue. thank you.

[Jay-eem]

Hi, @beapasch  
Can you help me on this. any or anyone explain how this happened? 

[beapasch]

Hi @Jay-eem; Have you already tried to build the application with the new client runtime version 4.11.149? If that's the case and you're still having the problem, we need to take a closer look. Can you please send me the project file so that I can test it on our test systems? (email address buildapps@sap.com) ?
Kind regards, Bea

[Jay-eem]

Yes. i tried and same error appear

[Jay-eem]

Hi, @beapasch . already sent the project file on your email. thanks you so much.