Xcode

It appears to be correctly signed. Automatically manage signing is checked, my standard team is set. With those settings, as soon as I assign an app group in Xcode 26.1, it changes to an Xcode managed provisioning profile and my valid Apple Development certificate and does not let me change them. I also checked the build with codesign -dv --verbose=4 and in ~/Library/Developer/Xcode/UserData/Provisioning Profiles to verify and that the profiles update, e.g., when I change the Info.plist. I also tried setting up a fresh sample project from the standard multiplatform SwiftUI app template in Xcode and did not change anything in Signing & Capabilities except setting the app group for the app and download extension. Same minimal app just calling AssetPackManager.shared.assetPack(withID:), same result: on iOS it works, on macOS the URL override is not permitted.

I'm at 19% right now (copying shared cache symbols from watch). What helped me was making sure Always On is enabled and also, most importantly, changing Return to Clock setting to 1 hour. Probably don't want to let your computer fall asleep. I also read somewhere that you should keep xcode in the foreground!

Thanks for your post. Although you have a comprehensive list of questions, such as tint handling without demonstrating the setup process, it appears that you are using Flutter instead of Xcode. I recommend starting with a tutorial on LiveActivity and configuring it to observe its functionality and the rendering of the Activity UI. This step-by-step approach ensures that you have a thorough understanding of the process and can identify any potential issues. Even thought assumes you are using Xcode. https://developer.apple.com/documentation/activitykit/displaying-live-data-with-live-activities Also I would recommend to go to the 3rd party tool support channel and see if they have a sample or a tutorial to go over the issues. You should check with the support resources provided by the 3rd party to get assistance with their software. Unless another developer in the forums has experience with the third-party and can provide assistance. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post. It is intriguing to note that you are utilizing the AlarmManager property alarmUpdates. Could you please provide the Xcode version you are currently using? Although I have not personally utilized this property, as described in the documentation, it allows you to receive notifications when an alarm alerts, snoozes, or dismisses. Therefore, it is possible to retrieve updates at AlarmManager.shared.alarmUpdates. Could you kindly share a focused sample project that demonstrates the issue you are encountering with obtaining these updates? I recommend referring to the sample provided in the documentation: https://developer.apple.com/documentation/alarmkit/alarmmanager/alarmupdates-swift.property About the focused project: If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

I do use URLsession. From what I could find with research online and even checking with ChatGPT for more specific questions on the topics that seemed to be what I needed to allow the app to connect to a website and use URL links to download docx files for the app. The problem that I am seeing is I am not sure if I am using the URLsession correctly or if there are additional steps I need to take when it comes to accessing this Documents Directory that is on the mobile device itself to access the documents. From my own testing when Io run the app I try checking documents on the mobile device but nothing looks to update so my guess is I am not using the URLsession function correctly. I am a beginner still with using swift and Xcode so I am trying to learn as much as I can for working on this project. My Project is setup with multiple .view scripts to handle different parts of the app itself. They are setup as follows: ContentView This script is used for viewing the app itself where I have buttons displa

Ah, that’s helpful information. We log the message about not permitting development overrides when the app isn’t signed with a development profile. Can you confirm that your app is code-signed for development with a valid provisioning profile when you run it from Xcode? In particular, ensure that it isn’t ad-hoc-signed (i.e., “sign to run locally”).

Thanks again. Resolution has been updated to Potential fix identified - For a future OS update. Could be wrong but this may mean an Xcode update.