Post

Replies

Boosts

Views

Activity

xcodebuild command failing after upgrading to Xcode 15
We have a server with mac and Xcode which generates apps for IOS signing them with release provisioning profile and sign identities. It does by command line It worked perfectly until we upgraded from Xcode 14 to Xcode 15.2 This is the command that we execute to generate the Xarchive, and it is failing, not generating anything and giving error: xcodebuild -workspace Project.xcworkspace -scheme "Release Ads" -xcconfig Project/Custom.xcconfig PROVISIONING_PROFILE_SPECIFIER=realidentifier CODE_SIGN_IDENTITY=realsignidentity CODE_SIGN_ENTITLEMENTS=/Users/user/project/Project/Project.entitlements archive This is the content of Custom.xcconfig file: OTHER_SWIFT_FLAGS = -Onone -DCOCOAPODS -DRELEASE -DADS -DFIREBASE -DPUSH This is the content of Project.entitlements file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>aps-environment</key> <string>production</string> <key>application-identifier</key> <string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string> <key>beta-reports-active</key> <true/> </dict> </plist> I can see this on the error log of the console: 2024-05-08 18:38:55.527 --- xcodebuild: WARNING: Using the first of multiple matching destinations: 2024-05-08 18:38:55.527 { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00008103-001904CE1EC3001E } 2024-05-08 18:38:55.527 { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:588FF55F-AFE3-4201-883D-AA074825765E, OS:17.2, name:iPad (10th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:588FF55F-AFE3-4201-883D-AA074825765E, OS:17.2, name:iPad (10th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:E7D3BE01-626C-4448-AD07-9B72E8D59778, OS:17.2, name:iPad Air (5th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:E7D3BE01-626C-4448-AD07-9B72E8D59778, OS:17.2, name:iPad Air (5th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:CE0E7741-9872-4903-95D3-DA86730D8D91, OS:17.2, name:iPad Pro (11-inch) (4th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:CE0E7741-9872-4903-95D3-DA86730D8D91, OS:17.2, name:iPad Pro (11-inch) (4th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:23DEF9D6-7B62-4829-A2F0-9C4356F7CB22, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:23DEF9D6-7B62-4829-A2F0-9C4356F7CB22, OS:17.2, name:iPad Pro (12.9-inch) (6th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:00F68979-CC31-4FDA-BD44-6AE3E41EEC3A, OS:17.2, name:iPad mini (6th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:00F68979-CC31-4FDA-BD44-6AE3E41EEC3A, OS:17.2, name:iPad mini (6th generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:5396905C-A343-4D94-95DD-23FE0ADDDCEB, OS:17.2, name:iPhone 15 } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:5396905C-A343-4D94-95DD-23FE0ADDDCEB, OS:17.2, name:iPhone 15 } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:F713CFB0-8617-424D-BE03-51B506931BFD, OS:17.2, name:iPhone 15 Plus } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:F713CFB0-8617-424D-BE03-51B506931BFD, OS:17.2, name:iPhone 15 Plus } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:594E330B-252D-4728-955C-B508E70AD20A, OS:17.2, name:iPhone 15 Pro } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:594E330B-252D-4728-955C-B508E70AD20A, OS:17.2, name:iPhone 15 Pro } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:B7551687-D9C6-46E9-BA26-D0CC70AC134D, OS:17.2, name:iPhone 15 Pro Max } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:B7551687-D9C6-46E9-BA26-D0CC70AC134D, OS:17.2, name:iPhone 15 Pro Max } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:E5D6C1EA-81B1-49D5-BF55-673258AE1227, OS:17.2, name:iPhone SE (3rd generation) } 2024-05-08 18:38:55.527 { platform:iOS Simulator, id:E5D6C1EA-81B1-49D5-BF55-673258AE1227, OS:17.2, name:iPhone SE (3rd generation) } 2024-05-08 18:39:24.105 ** ARCHIVE FAILED ** 2024-05-08 18:39:24.105 2024-05-08 18:39:24.105 2024-05-08 18:39:24.105 The following build commands failed: 2024-05-08 18:39:24.105 PhaseScriptExecution [CP]\ Embed\ Pods\ Frameworks /Users/user/Library/Developer/Xcode/DerivedData/Project-bdyzwdcujggpnmedzctlookvtuwv/Build/Intermediates.noindex/ArchiveIntermediates/Release/IntermediateBuildFilesPath/Project.build/Release-iphoneos/Project.build/Script-FEF05C244C47CB5438EC384B.sh (in target 'Project' from project 'Project')
1
0
3.1k
May ’24
Sometimes the DTD file of info.plist xml is giving me XML parsing error
Hi I'm using this code (java code) to parse the info.plist file of an iOS project and add or replace some values: DocumentBuilder dBuilder = dbFactory.newDocumentBuilder(); File plistFile=new File("/project/SupportingFiles/Info.plist"); Document doc = dBuilder.parse(new BufferedInputStream(new FileInputStream(plistFile))); In some cases is working perfectly and parsing the XML, then I can replace values and transform the XML and it works perfectly. But since yesterday, day 7, in some cases, the last line of that sample code is giving me a parsing exception: SAXParseExceptionpublicId: -//Apple//DTD PLIST 1.0//EN; systemId:http://www.apple.com/DTDs/PropertyList-1.0.dtd; lineNumber: 1; columnNumber: 2; The markup declarations contained or pointed to by the document type declaration must be well-formed. This is the start of the infoplist file: ?xml version="1.0" encoding="UTF-8"? !DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" plist version="1.0" How its possible that sometimes is working and sometimes not since yesterday when it was working for years? how can this be solved? Thanks
3
0
3.0k
May ’21
Warning: unable to build chain to self-signed root for signer. Certificate is not trusted
Hi. I manage an automatic server that compiles iOS apps. It worked perfectly until some days ago. It successfully compiled and generated around 500 or 600 ipas maybe, probably with different certificates, not sure. This is the server: Xcode 12.2 This server receives Xcode projects, and certificates. First It installs certificates, then, generates the xarchive, and finally the IPA. Now there is a problem with certificates in every project I try to compile. This is the problem that is printed into log when I try to compile a project: Warning: unable to build chain to self-signed root for signer "iPhone Distribution: Xxxx Xxxxx (XXXXXX)" If I open keychain, the certificate has this error red line in the top of the keychain: "iPhone Distribution: Xxxx Xxxxx (XXXXXX)" certificate is not trusted I read all the related questions openned here with similar titles and none of them gives a solution for this case, remember that I didn't change anything in the server, it worked perfectly until some days ago and stopped worked suddenly. Maybe something has been corrupted? Now, I will explain how this automatic compiler server works... This is how I install certificates in the server before compiling the IPA. I execute a procesCerts.sh file which contains these lines: ditto prov.mobileprovision ~/Library/MobileDevice/Provisioning\\ Profiles/ Then, I extract the signIdentity and the provisioningProfileUUID and after that, I generate the Xarchive with this line: xcodebuild -workspace App.xcworkspace -scheme Release -xcconfig Caponate/Custom.xcconfig PROVISIONING_PROFILE_SPECIFIER=xxxxxxx CODE_SIGN_IDENTITY=iPhone Distribution: Xxxx xxxxx CODE_SIGN_ENTITLEMENTS=/Users/user/jobs/83554/project/App/App.entitlements archive And I generate the Ipa with this line: xcodebuild -exportArchive -archivePath sourceFile -exportPath targetFile -exportOptionsPlist /project/exportOptions.plist Which is the problem? why certificates are not working anymore? Thanks
1
0
4.5k
Feb ’21