Hi,I'm attempting to use xcodebuild to automate our release process. Because our build has an associated provisioning profile, I have added the `-allowProvisioningUpdates` flag to the xcodebuild command.If I run my xcodebuild command while logged in locally to the build machine, Xcode's automatic process of downloading the correct prov profile appears to work - the archive completes succesfully.However. If I ssh into the build machine and run the exact same xcodebuild command, I get the following error.2019-10-08 00:04:50.828 xcodebuild[53165:1665565] DVTPortal: Service '' encountered an unexpected result code from the portal ('1100') 2019-10-08 00:04:50.828 xcodebuild[53165:1665565] DVTPortal: Error: Error Domain=DVTPortalServiceErrorDomain Code=1100 "Your session has expired. Please log in." UserInfo={payload={type = mutable dict, count = 9, entries => 0 : responseId = {contents = "78442697-9dda-449d-90b7-cfc0d646fde4"} 2 : {contents = "protocolVersion"} = QH65B2 3 : {contents = "requestUrl"} = {contents = "https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action"} 6 : {contents = "userLocale"} = en_US 8 : resultCode = {value = +1100, type = kCFNumberSInt64Type} 9 : userString = {contents = "Your session has expired. Please log in."} 10 : {contents = "resultString"} = {contents = "Your session has expired. Please log in."} 11 : httpCode = {value = +200, type = kCFNumberSInt64Type} 12 : {contents = "creationTimestamp"} = {contents = "2019-10-07T22:04:50Z"} } , NSLocalizedDescription=Your session has expired. Please log in.}In my attempts to fix this issue I made sure the login keychain was unlocked using the `security` command, but it made no difference.Is there any way of fixing this? Is it possible to log into the service via the command line?The user I ssh in as is present in the Accounts pane of Xcode, but I guess this login is somehow "lost" over ssh.Thanks in advance!Heather.

Hello,Because our app has a Plugin system, I am trying to release a version that has both com.apple.security.get-task-allow and com.apple.security.cs.disable-library-validation entitements enabled (along with further entitlements).The disable library validation entitlement has been added to my entitlements file, and I have set CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES in my xcconfig file for both Release and Debug configurations.My codesigning settings are as follows:CODE_SIGN_IDENTITY = Developer ID ApplicationDEVELOPMENT_TEAM = WUxxxxx46CODE_SIGN_STYLE = ManualI'm creating the archive as follows:xcodebuild -workspace S.xcworkspace -scheme S -sdk macosx -configuration Release archive -archivePath S.xcarchive -derivedDataPath ddd -xcconfig S/Configs/Final.xcconfigHowever when I run codesign on the resulting app, the get-task-allow entitlement is not present.codesign -d --entitlements :- S.xcarchive/Products/Applications/S.app/<?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>com.apple.security.application-groups</key> <array> <string>WUxxxx46.</string> </array> <key>com.apple.security.automation.apple-events</key> <true/> <key>com.apple.security.cs.allow-jit</key> <true/> <key>com.apple.security.cs.allow-unsigned-executable-memory</key> <true/> <key>com.apple.security.cs.disable-library-validation</key> <true/> <key>com.apple.security.personal-information.photos-library</key> <true/></dict></plist>If I add -showBuildSettings to the end of my xcarchive line, the output there does confirm that CODE_SIGN_INJECT_BASE_ENTITLEMENTS is set to YES.I've also had a look at the xcent file in the Intermediate build phase directory and get-task-allow isn't there either.Can anyone provide any insight as to what I'm doing wrong please?ThanksHeather.

Hello,As part of testing the qlgenerator that ships as part of our app, we have a test that calls the following command:qlmanage -o /tmp/<unique-dir-name> -g SQuicklook.qlgenerator -c com.bo.s.dr -p path/to/testing/source/file.drThis generates a file structure under /tmp/<unique-dir-name> and we examine the generated Preview.png file in there. Under 10.14 this is all working perfectly.However, under Catalina, running the exact same command produces the following output:qlmanage -o /tmp/ -g SQuicklook.qlgenerator -c com.bo.s.dr -p path/to/testing/source/file.dr Testing Quick Look preview with files: /full/path/to/path/to/testing/source/file.dr - force using content type UTI: com.bo.s.dr - force using generator at path: SQuicklook.qlgenerator * path/to/testing/source/file.dr produced an image preview Can't decode raw image for path/to/testing/source/file.drRunning `qlmanage -g SQuicklook.qlgenerator -c com.bo.s.dr -p path/to/testing/source/file.dr` (i.e. without the -o parameter) produces the preview image with no problems on screen. That indicates to me at least that the generator is working fine, it's just that as soon as I try to write it out to disk, qlmanage is doing something weird.Does anyone know if qlmanage -o behaviour has changed with Catalina?Are there any insights as to why this doesn't work anymore on Catalina?For the record, getting it to generate a thumbnail (-t) works fine on Catalina. It's just the preview (-p) that's stopped working.Thanks in advance!Heather.