User Profile

Posts

Posts

Post marked as solved
2 Replies
4k Views

xcodebuild proxy settings

Hi, I am trying to upload an app using xcodebuild from the command line from an automated build-server. This works perfectly when I am not behind a proxy, but my build-machine is behind the proxy and cannot turn it off. The build and upload also works fine from xcode-ui when the proxy is enabled. My current proxy-settings are defined in the environment-variables http_proxy and https_proxy and are working for other command-line tools like curl and wget, The proxy has its own certificate so I need the xcodebuild command to recognize both my proxy-settings and trust the certificate for the proxy. When trying to upload, the process is stuck at the step "Authenticating with the App Store...", and finally quits with exit code 70: 2020-11-12 13:00:51.355 xcodebuild[79720:561739] Starting upload 2020-11-12 13:00:51.457 xcodebuild[79720:561739] Progress 2 %: Extracting archive… 2020-11-12 13:00:51.557 xcodebuild[79720:561739] Progress 4 %: Creating App Store Connect API analysis file… 2020-11-12 13:00:54.420 xcodebuild[79720:561739] Progress 6 %: Authenticating with the App Store… 2020-11-12 13:09:42.466 xcodebuild[79720:562922] Progress 100 %: Authenticating with the App Store… 2020-11-12 13:09:42.467 xcodebuild[79720:562922] Progress 100 %: Completed App Store operation. error: exportArchive: App Store Connect Operation Error. An error occurred uploading to the App Store. Error Domain=WorkerErrorDomain Code=-10000 "error: App Store Connect Operation Error. An error occurred uploading to the App Store." UserInfo={NSLocalizedDescription=error: App Store Connect Operation Error. An error occurred uploading to the App Store.} EXPORT FAILED make: *** [ios-testflight] Error 70 When i run netstat -an|grep SYN during the upload, it shows that a tcp-connection is blocked by a firewall or something, wich i suppose is because of the proxy is not beeing used: tcp4 0 0 10.0.16.193.61011 17.110.232.68.443 SYN_SENT (17.110.232.68 is an ip owned by apple) Is there any known way to solve this with the xcodebuild-command?
Posted
by nilsl.
Last updated
.
Post not yet marked as solved
0 Replies
817 Views

Creating a key in secure enclave with custom LAContext

Hi, I am looking for a way to create a key in secure enclave with the option .biometryCurrentSet in combination with a custom LAContext with a custom value for LAContext.touchIDAuthenticationAllowableReuseDuration so that I can use the key in secure-enclave multiple times after the user has authenticated himself just one time. Is this possible, or does the .biometryCurrentSet require the user to authenticate on each use of the key no matter what options i use to create the key? I have tried some solutions without any luck, I am suspecting that I am trying to do something that is not supported at the moment. For the equivalent android-option, I can use setUserAuthenticationValidityDurationSeconds on the key specification.
Posted
by nilsl.
Last updated
.
Post not yet marked as solved
0 Replies
420 Views

DCAppAttestService.attestKey hangs on wrong input

When calling DCAppAttestService.attestKey(...) with either invalid keyIdentifier too long clientDataHash the service just hangs and the callback is never called with an error or result. How should we handle this, apart from validating the input before calling the method? Shouldnt the callback return with an error if any of the arguments are invalid?
Posted
by nilsl.
Last updated
.