“file uri scheme”

@_lilpit and @Russ_T, Thank you for filing these Feedback reports. We are looking into them.

@e5johnson Please file a code-level support request including your Team ID for assistance.

@ohadh123 he remaining request is for a ShieldAction extension, which handles button taps from the shield UI.This entitlement is currently blocking our business's beta testing, so we’re trying to understand whether this is just normal queue delay or if the request might be stuck. Please file a code-level support request including your Team ID for assistance.

@lateef Our app is almost ready to launch and this capability is critical for us. Both the main app and an extension depend on Family Controls, so we’re currently blocked from moving forward. Did you also submit a separate request for the extension? If you didn't, please file one for your extension. For more information, see Requesting the Family Controls entitlement .

Please file a code-level support request including your Team ID for assistance.

I'm glad to hear that helped, @rozanski. @DaeLee, let us know here once you've got that bug report filed and its number so we can look into your situation. — Ed Ford,  DTS Engineer

Please file a code-level support request including your Team ID for assistance.

I saw this post, but have not found anything there about the one file works, separate files crashes aspect. So I submitted a post. But in general yes, it is also about sorting on optional nested relationships. @nilsn26: Thanks for your feedback report and confirmation. I don't have a clear answer about why putting the models and the sort logic in a same Swift file avoids the crash either, but I think the technical nature here is that KeyPath.appending can't forward optionality, which is a known issue under the investigation of the Swift team. Best, —— Ziqiao Chen  Worldwide Developer Relations.

What's the best way of being careful about this, or do you just mean by using the item replacement directory where possible? As far as I know, there are only two ways of getting a temp directory: Everything you've described sounds like you're on the right track. The big thing is just not making assumption about the relationship between directories (/tmp/ and home are on the same volume) or capabilities (home directories are ALWAYS on volumes that support cloning). The killer here is the long tail, as there are just SO many different edge cases. LibZip is much faster on a volume that supports cloning Interesting. Are you primarily editing the contents of the zip file (so you end up modifying the data inside, but don't really change it's overall size or structure)? Cloning is a huge help if you can clone the contents and then modify but if your modifications end up changing the fundamental contents, then I wouldn't expect the difference to be nearly as large. At large scale, this eventually devolves to

A few brief clarifications and comments: I am seeking clarification on whether the various driverkit entitlement families (com.apple.developer.driverkit.family.*) are available for development on my local Mac without requesting entitlements from Apple. Making the more explicit, they Development Only entitlement variants do two things: They match against a VERY broad hardware configuration, basically letting you match any hardware. Their ONLY available to Development signed builds. Note that the second criteria heavily restricts distribution, as development builds will ONLY run on machines which were registered with your developer account at the point the signing profile was generated. This is largely invisible when using automatic signing (Xcode will just generate a new profile), but can be easy to overlook with manual signing. At WWDC2022 Apple stated that In MacOS... In fact, all DriverKit family entitlements are now available to use for development. On these very forums, Eskimo himself also suggested this

Hi, We need some more diagnostics to be able to help you resolve the issue. Could you please file a feedback request for this and post the feedback number here? You can file Xcode Cloud specific feedback using these steps. Thanks

Quinn is helping this, which is great. I am just curious if the com.apple.developer.icloud- is really com.apple.developer.icloud-container-identifiers. I am guessing that the provisioning profile on your machine, either your notebook or Mac Mini, is not up to date, which leads to the different behaviors. Maybe you can try the following: Be sure your developer account is correctly set up in Xcode Settings > Apple Accounts, and your Mac has the access Apple's developer portal. Uncheck the Automatically manage signing box, and check it back. This tells Xcode to refresh the provisioning profile. If that doesn't help, try to remove the iCloud capability – You are not using any iCloud feature, and so don't really need the capability just yet. If you do need the iCloud capability, check one of the services, and pick an iCloud container if the service you checked is iCloud Documents or CloudKit. This is how folks use the capability. If everything goes well, the .entitlements file in your project should ha

Hi! Thanks for the detailed writeup. This doesn't look right, and is probably a bug. Can you please file a bug report and include all this info you posted here (and feel free to link the post as well) these code sample these video recording to the following link? https://developer.apple.com/bug-reporting/ We may also need logs. I think simulator logs get logged to the Mac's system so the steps on the site might help you capture logs from your Mac when you file. Otherwise, if you have a physical device that is running this code, those logs may be even better. You can reply what the Feedback ID is for this issue and I'll make sure it gets to the right team to investigate.

You should definitely file a bug against the App Store validator. There’s nothing fundamentally wrong with using square brackets in your app name. Please post your bug number, just for the record. On the workaround front, the idea of setting your app’s on-disk name to something without the square brackets and then applying the square brackets at the display level seems reasonable. However, it’s not as simple as setting CFBundleDisplayName. Rather, you have to go through the localisation subsystem. macOS does support localised app names but there are complications: The bundle name (CFBundleName) must match the file name on disk (without the .app extension, obviously) [1]. If they do match, it checks for LSHasLocalizedDisplayName. And if that’s set, it tries to get the localised version of CFBundleDisplayName. Note There are further complications related to CFBundleDisplayName, but I didn’t explore those in depth. My goal was just to get anything to work (-: So, consider this app: % plutil -p

Oof, good luck with ReactNative. I haven't used any IAP ReactNative library, so I'll speak in terms of native StoreKit. On a somewhat relieving note, I also have this issue in my Swift-native iOS app, and I made a post about it on the forums, too. It happens both in Sandbox and production, but NOT when using Local StoreKit Testing configuration files. There are multiple ways for you to observe StoreKit updates. You can observe transactions with Transaction.updates, and also just the subscription updates themselves with SubscriptionStatus.updates. Technically, these are different, but of course a new transaction means potential for a subscription status update. Basically, I had to implement logic to de-duplicate subscription updates that were redundant. For every Subscription update I get, I map it to an array for what I see as active subscriptions. The rest of my app will watch for if my array of active subscriptions changes. If it changes, then we will enabled/disable features. Duplicate transaction