A Summary of the WWDC25 Group Lab

OK. Lemme start you out with a couple of links: On File System Permissions explains the different subsystems that all contribute to file system permissions on macOS. BSD Privilege Escalation on macOS describes the various ways to escalate privileges on macOS. In this case you’re dealing with two types of file system permissions: App Sandbox BSD You can get around the first with the coöperation of the user, that is, by having them select the relevant directory in an open or save panel. The issue you’re bumping into in the second. Consider the permissions on the Applications folder: % ls -ld /Applications drwxrwxr-x 89 root admin 2848 Sep 17 14:06 /Applications To remove application you need to be able to write to this directory. But you can only do that if you’re running as a user in the admin group. The directory is read-only for standard users. To get around this you need to escalate privileges. However, the App Review Guidelines specifically proscribe that (clause 2.4.5(v)) I’m only aware of one ex

Hello - When offering in-app purchase subscriptions, it is common to offer different subscription periods for the same level of access - where the only differences are price and duration of subscriptions (e.g. monthly, quarterly, and annual.) If the access entitled by various subscriptions is the same (that is, a monthly subscriber has access to all of the same content, features, etc. as an annual subscriber), it is best practice to assign all of those subscription products to the same subscription group in App Store Connect, as documented here - including the assignment of subscription levels. This will ensure correct handling of upgrades, crossgrades, and downgrades, as documented here, and prevent customers from having more than one active subscription at a time. While developers can control how and when to merchandise subscription products in their app, it is not possible to restrict customers from switching between available products in the same subscription group from their Manage Subs

The Advanced Commerce API utilizes two generic product identifiers that you configure within App Store Connect. A Consumable Product Type, which can be utilized for all one-time purchase products. An Auto-Renewable Subscription, which represents all your products in your catalog (also known as SKU). The reporting through App Store Connect provides the SKU. The SKU are available in Summary Sales Report & Financial Report. Note: A SKU can represent the in-app purchase product that you offer in the app. Therefore, ensure that you provide the identifier of the product that you offer customers to purchase.

Hello - First, to answer the question you asked in the video: how is it possible for subscribers to change from one plan to another? We can see that you have set up one subscription group with ten different products - eight of which are currently Ready for Sale (active.) When a customer subscribes to any product, they can at any time switch to a different product in the same group as documented here. See attached screenshot specific to your app and its available products. If your app is not presenting upgrade/downgrade/crossgrade options, then customers are switching from their Manage Subscriptions page. Any changes from one subscription to another can only be completed by the customer. Developers must ensure that the ordering and grouping of individual subscription products within a subscription group is addressed to meet their business needs, as documented here, under the section titled Assign subscription levels. This setup is completed in App Store Connect. Please let u

Thank you. Setting preferredPlacement to fixed was the missing piece. I already had allowsHiding set to false and I’m not using any tab groups. The Edit button no longer appears in the sidebar. But I have discovered an iOS 26 (and iOS 18) bug in the process. I need to file a bug report but here’s the issue. I present the tab bar controller as a modal view controller on an iPad. If I resize the app window from full screen to a size that is horizontally compact while the tab bar controller is in view, the tab bar controller of course changes from showing a sidebar to showing an old style tab bar on the bottom with a More tab. Selecting the More tab now shows an Edit button. But only in this case. If the tab bar controller is presented after the app window is made horizontally compact, then the More tab does not show the Edit button.

The 'Edit' button will show up in the sidebar as long as editing is supported in UITabBarController for the current set of tabs. Editing is supported if any of the following are true: Any tab has a customizable preferredPlacement (i.e. not .fixed or .pinned) If a tab can be hidden: allowsHiding = true If a tab group can be reordered: allowsReordering = true By default , the preferredPlacement is automatic which does support editing. Set it to .fixed to disable customization for them.

Log Comparison Details for Bug Report Detailed Log Analysis: iOS 18.4 vs iOS 26 RC Complete Test Scenario Log Comparison Test Case: Type あ → Press Enter → Type あ → Delete → Type A iOS 18.4 / Xcode 16 (Correct Behavior) // Step 1: Type first あ === stringRange: 0[any]..<0[any], currentText: , replacementText: a changedText: a, allowChange: true === // Note: IME shows a first, then converts to あ // Step 2: IME converts a to あ === stringRange: 0[utf16]..<1[utf16], currentText: あ, replacementText: あ changedText: あ, allowChange: true === // Result: Text = あ, Count = 1 ✓ // Step 3: Press Enter (No additional delegate call - composition confirmed correctly) // Result: Text = あ, Count = 1 ✓ // Step 4: Delete あ === stringRange: 0[utf16]..<1[utf16], currentText: あ, replacementText: changedText: , allowChange: true === // Result: Text = , Count = 0 ✓ // Step 5: Type A === stringRange: 0[any]..<0[any], currentText: , replacementText: A changedText: A, allowChange: true === // Result: Text = A, Count = 1 ✓ Fina

Here's what we said in WWDC25 Platforms State of the Union: As you evaluate your app's UI and the time you need to adopt the new design, we're providing an option to continue to use your app's current design with Xcode 26. We intend this option to be removed in the next major release. — Ed Ford,  DTS Engineer

You could try adjusting the edge effect using UIScrollEdgeEffect and specifying a different style. That said, starting in iOS 26, the recommendation is to reduce your use of custom backgrounds in navigation elements and controls. Any custom backgrounds and appearances you use in the navigation bar might overlay or interfere with Liquid Glass or other effects that the system provides, such as the scroll edge effect. To learn how to update your app to adopt Liquid Glass, see the following resources: Adopting Liquid Glass WWDC25 session 356: Get to know the new design system WWDC25 session 284: Build a UIKit app with the new design.

This is a customer setup, and we are unable to reproduce the issue locally in our lab. The customer is experiencing unusual behavior they report that VPN performance is fine when connecting to a nearby VPN server, but it slows down when connecting to a server in a distant location. We have asked them to check their network and infrastructure on their end, as we believe this may not be a VPN issue, they are looking into it. For the first issue where the VPN fails, our investigation suggests that the socket enters a bad state once the device is locked and extension goes to sleep. It is neither timing out nor sending data, which indicates the socket enters a bad state and the resource is not accessible. Note: Both issues are not reproducible on iOS 18.

There is a way to tell different views that they should be part of the same liquid glass group. i don't remember how it's called exactly and if it will help but you could give it a shot. Apple talked about that API in one of the WWDC videos

[quote='858251022, DTS Engineer, /thread/800521?answerId=858251022#858251022'] I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP. [/quote] I repeated the test described above with Xcode 26 RC and iOS 26.0, and things continue to work. Here’s a summary of my results: Xcode | iOS | Result ----- | --- | ------ 16.4 | iOS 18.6.2 | OK 26.0 RC | iOS 18.6.2 | OK 26.0 RC | iOS 26.0 | OK This is all running on macOS 15.6.1, using a unique bundle ID each time. At this point I’m pretty much convinced that the root cause of this issue is resolved and that the remaining problems are caused by Xcode caching bad state. Unfortunately it’s hard for me to test solutions to that because I’ve never managed to reproduce the problem. [quote='858275022, totofrechou, /thread/800521?answerId=858275022#858275022, /profile/totofrechou'] The answer from Muslim Ismailov in Stack Overflow worked for me [/quote] Cool. That’s very like what I described earlier. Share and Enjoy — Quinn “The Eskimo!” @ Deve