“missing package product”

[quote='879525022, dispacthMain, /thread/818199?answerId=879525022#879525022, /profile/dispacthMain'] Do you think standard DNSSettings still should work? [/quote] I don’t know, which is why I suggested you try it. It’s definitely counter-indicated by the docs, but I can’t see anything in the code that blocks it. OTOTH the system is complex, so it’s easy for me to miss things. Of course, if it does work then there’s the question as to whether you should relying on this implementation detail. However, it’s only worth digging into that if it actually works. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the download link. I’m not sure what the actual problem is here. I ran your app through (roughly) the process described in Testing a Notarised Product, and everything seemed to work just fine. Specifically: In a fresh macOS 26.3.1 VM, I downloaded that zip archive in a way that sets quarantine. I unpacked it using the Finder. And then I opened the app using the Finder. It passed Gatekeeper, launched, and showed its initial UI. I then ran some basic validity checks, and those also passed with flying colours: % syspolicy_check distribution umldiagrammer.app App passed all pre-distribution checks and is ready for distribution. % codesign -v --deep --strict -vvv umldiagrammer.app … umldiagrammer.app: valid on disk umldiagrammer.app: satisfies its Designated Requirement % spctl -vvvv --assess --type exec umldiagrammer.app umldiagrammer.app: accepted source=Notarized Developer ID origin=Developer ID Application: Humberto Sanchez II (NA8Z96F8V9) Please run through these steps yourself and let me

I heard several years ago that there is a software package or equivalent that lets you create a SwiftUI screen design based a Figma submission.

I presume you looked at implementing code like this, from the documentation: @AppIntent(schema: .system.search) struct ExampleSearchIntent: ShowInAppSearchResultsIntent { static var searchScopes: [StringSearchScope] = [.general] var criteria: StringSearchCriteria func perform() async throws -> some IntentResult { let searchString = criteria.term print(Searching for (searchString)) // ... // Code that navigates to your app's search and enters the search string into a search field. // ... return .result() } } The key type here, ShowInAppSearchResultsIntent, is a clear indication of the intended behavior of showing search results inside of the app. Also, testing your intent in the Shortcuts app is an excellent way to test. Do I need to do AppIntents without the schema and wait until there is a search schema that does not open the app, or should I be using a different schema? What am I missing? It's worth considering the larger picture of what someone does with your intent after the search — in many c

Thanks for the post. This is extremely interesting, but I'm sure is frustrating as well. Are you able to complete the installation if you boot to safe mode? It seems it is almost certainly a corrupted OTA (Over-The-Air) delta update file cached on your system? The process terminates with Failed to prepare the software update or An error occurred while downloading the selected updates.”? When a beta update fails halfway or downloads a corrupted delta package, macOS will continuously try to use that broken file every time you hit Update, resulting in the same error. Can I ask you both to please create a bug for this issue? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Thanks!! Albert Pascual
  Worldwide Developer Relations.

Hi @shirakura, Thanks for reporting the unexpected behavior you've observed in the Sandbox environment. For Apple Pay merchants using the Sandbox payment gateway, the user and device must now be a sandbox tester account. Previously, both production and sandbox tester accounts were supported. Could you please confirm you've configured the device to test against the Apple Pay & Wallet Sandbox? To confirm this, your device should be logged in with a sandbox tester account: Sandbox Testing https://developer.apple.com/apple-pay/sandbox-testing/ If your device is using a sandbox test account for Apple Pay and Wallet, the Apple Pay Server engineering team would need to investigate this issue directly via Feedback Assistant. To submit a bug report, please follow the steps outlined in the post below: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 Once submitted, please reply here with your Feedback ID so I may escala

Thanks for the post and sorry that I have missed it, somehow went over all my filters, no excuses for me, thanks for your patience. Doing a simple request returns correct JSON with curl -v https://app.myloft-stage.com/.well-known/apple-app-site-association But with a simple user-agent we get a security issue: curl -I -A AASA-Bot/1.0 https://app.myloft-stage.com/.well-known/apple-app-site-association So the servers can’t not access the file. When you test the URL in your browser or via cURL, you are using a standard User-Agent. When Apple's CDN fetches the file, it uses a specific bot User-Agent and originates from Apple's IP subnets. Check your server/WAF access logs for requests to the /.well-known/apple-app-site-association path. Look for blocked requests or requests returning a 403/Challenge status for the AASA-Bot User-Agent. Whitelist all User-Agent and IPs in your firewall rules for that specific path. When all that is done, everything will start working in a few hours. Albert Pascual
  Worldw

Hello, You can find most of the answers and details to your points by going through the Supporting offer codes in your app article, but let me give you a summary to your specific questions: You can test offer codes in the sandbox environment for all In-App Purchase product types: consumable, non-consumable, non-renewing subscription, and auto-renewable subscription. To redeem an offer code in the sandbox environment, follow these steps: On your device, sign in using a Sandbox Apple Account. On the Sandbox Account Settings page, tap Initiate Transaction. Select Offer Codes and redeem a sandbox offer code you created in App Store Connect. You can use the information contained in the transaction to identify products purchased with offer codes, you need to check the offer property of Transaction on StoreKit, or the offerIdentifier if you're using the App Store Server API or notifications. If you're not using it yet, we highly recommend using the App Store Server libraries to adopt the App Store

One of these two changes fixe my issue. (1) My CoreDataStack was inside of a package, and the package didn't include .macCatalyst inside of the platforms. Adding it fixed the issue. platforms: [ .macCatalyst(.v26), ], (2) Adding managedObjectContext to the view explicitly inside of a sheet .sheet() { View() .environment(.managedObjectContext, managedObjectContext) }