On: MacBook M1, MacOS 12.4, Xcode 13.4.1 (the issue was present in the previous Xcode version too). When executing (for an iOS app): "xcrun altool --upload-package ...", I've started getting (it didn't happen before) this error sequentially 28 times: 2022-06-07 07:58:57.740 *** Error: /Applications/Xcode.app/Contents/Developer/usr/bin/bitcode-build-tool, terminated with status: 2 2022-06-07 07:58:57.740 *** Error: /Applications/Xcode.app/Contents/Developer/usr/bin/bitcode-build-tool (2): bitcode-build-tool internal error Traceback (most recent call last):  File "/Applications/Xcode.app/Contents/Developer/usr/bin/bitcode-build-tool", line 10, in   bitcode_build_tool_main(sys.argv)  File "/Applications/Xcode.app/Contents/Developer/usr/bin/../lib/bitcode_build_tool/main.py", line 65, in main   env.initState(args)  File "/Applications/Xcode.app/Contents/Developer/usr/bin/../lib/bitcode_build_tool/buildenv.py", line 160, in initState   self.logger.debug("SDK path: {}".format(self.sdk)) AttributeError: 'BuildEnvironment' object has no attribute 'sdk' After the errors are printed the upload-package starts the upload – though it no longer will show the upload progress – and eventually finishes without issue. I added some debug prints in buildenv.py and sure enough the args has "sdk_path=None". Anyone else experiencing this? Any ideas on how to fix it?

I've added a privacy manifest (via Xcode 15) in my iOS app and created a new release that was approved and published.. However, in App Store Connect my apps Privacy Nutrition Labels (General > App Privacy) have not been updated, nor have the privacy labels been updated in the actual App Store for my latest release. So my question is: Shouldn't have my app's App Store Connect privacy page and App Store privacy nutrition labels be automatically updated, per my latest release that included the new privacy manifest? I'm under the impression that they should have but maybe I'm mistaken; it would seem odd to still have to manually update privacy nutrition labels in App Store Connect when a privacy manifest was in the latest approved/published release. Thanks.

Recently I've started receiving a "FORBIDDEN_ERROR" error when submitting a PATCH to "/v1/apps/xxxx". The data below is what is being sent: { "data": { "type": "apps", "id": "xxxx", "attributes": { "contentRightsDeclaration": "DOES_NOT_USE_THIRD_PARTY_CONTENT" } } } This used to work (for over a year) fine. We also update several other things (Category, Age Rating, Available Territories etc) and they still work as expected; this is the only type that has started (about a month or so ago) to behave this way. I also generated a new API key with full Admin privileges but the issue still occurs. The specific error returned is: { "errors" : [ { "id" : "1cfb7772-940c-46d5-bfe5-a97bbe314", "status" : "403", "code" : "FORBIDDEN_ERROR", "title" : "This request is forbidden for security reasons", "detail" : "The API key in use does not allow this request" } ] } Any ideas how to fix this or what's going on? Thanks in advance.