“xcode github”

Hi @DTS Engineer - we have re-applied for the capability however upon submitting the form we got a Server 500 error. Could you advise what to do in this situation? Nothing seems to have changed in XCode either. Thanks

Thanks for the post, this is extremely interesting to me. Can you post as much code as possible to see how you use the LiveActivitiy and is configured in the main entry? So the system successfully registers the activity from the main app, but when it asks to render it, the Widget Extension fails to provide a matching ActivityConfiguration? And your Xcode previews work, the UI code is valid, but it is not being successfully exposed to the system at runtime? Even if your Live Activity code is perfectly written and included in the target, the system will not know it exists unless it is explicitly instantiated in your extension's main entry point. Can you provide the code for that for me to review? If you have standard home screen widgets alongside your Live Activity, you must include both in the bundle. If the LiveActivity is missing from this bundle, the OS will create the activity in the background, but the extension will silently fail to render it, resulting in the error you are seeing I believe. Loo

[quote='884233022, DTS Engineer, /thread/821961?answerId=884233022#884233022'] I’m talking with the right folks about this [/quote] I now have specific advice for folks in this situation: Please re-apply for the Contactless Pass Provisioning capability. The approval folks will then assign you the Contactless Pass Provisioning (deprecated) capability, which you can use right now. Once this Xcode issue is resolved (FB22439399), they will assign you the newer Contactless Pass Provisioning (SharableCredential) to use going forward. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Ya the connection bubbles are gone in source files it seems. I wouldn't be terribly surprised if this was on purpose as a optimization / way to clean out source from Xcode to make room for ...er never mind. You can still connect outlets/actions by just writing the property in your interface: @property (nonatomic, weak) IBOutlet NSTextField *label; -(IBAction)methodName:(id)sender And then making the connection in Interface Builder from the Connections Inspector. I use to use the Assistant editor and make connections the way you describe all the time back in the day when I was learning UIKit but I do find it faster to just type the property with IBOutlet and then connecting it in the Connections Inspector in IB. A shame not to see those nice little connection bubbles anymore in source files. I don't care what anyone says about live previews or whatever...IB was the thing. It's a shame Apple doesn't make improvements to it anymore but I still find it useful.

@briggr1 Thanks for the post, it's not a bug that Xcode does not allow Timer to run in the background. I would recommend to read my answer again about how the background process works but I may have failed to explain it well, I have been known to make that mistake, let me try it again. When you launch an app via Xcode (Build and Run), the Xcode debugger attaches to your app's process. To prevent the debugger from randomly disconnecting, iOS disables standard background suspension rules. Your app is allowed to run continuously in the background, consuming as much CPU and battery as it wants, so you can debug it. Now this is not the way on released apps. I think previously I have recommended to other users to move the process to as server to avoid using the device as to process the work. Also I think have previously recommended to go over this great documentation about how to use background processing: https://developer.apple.com/documentation/uikit/preparing-your-ui-to-run-in-the-bac

@szymczyk Thank so much for the great answer to download the selected simulators. https://developer.apple.com/documentation/xcode/downloading-and-installing-additional-xcode-components Albert
  Worldwide Developer Relations.

Choose Xcode > Settings to open the settings window. Select Components from the left side of the settings window. Click the Add Platforms button at the bottom of the settings window to open a sheet to select simulators to download.

bump - I appreciate any suggestions on how to proceed - should I file a defect against Xcode?

Thanks for your post, can you provide a link and description of this JAMP distribution? Is that a 3rd party app? Is that a MDM installation? The error usually means iOS has rejected the app because of a code-signing mismatch? And a mismatch between the certificate used to sign the existing IPA and the certificate associated with the new provisioning profile. Looking forward to get a better understanding of your distribution method. I would also recommend you to use Apple distribution methods. Have you tried the unlisted method to distribute apps? This allows you to publish an app on the App Store that is completely hidden from public search, categories, and charts. https://developer.apple.com/support/unlisted-app-distribution/ Or the Enterprise distribution? It allows you to generate Enterprise Certificates and Provisioning Profiles to sign an IPA locally and distribute it. You build and sign the app in Xcode using an Enterprise Distribution Certificate. Pushed via MDM (like JAMF, not JAMP) Hope this