show when run

I see the community bringing this up from time to time, and so would like to take this chance to hopefully get it sorted. For the clarify of the discussion, I'd split this question into three parts: Does App Review guideline allow a keyboard extension to launch its container app? If yes, is there any API to do so? Is there any API for the container app to bring the host app back to the foreground? The first part is about App Review policy, and so only the App Review team has the final answer, but looking into the App Review Guideline, you can see the following related to keyboard extensions: 4.4.1 Keyboard extensions have some additional rules. ... They must not: Launch other apps besides Settings; Here the guideline uses other apps, rather than simply apps or any app. I believe that means to say that launching the container app is allowed. To make sure my understanding is correct, I've reached out my App Review colleague, and they've confirmed that launching the container app from a keyboard extension (to do

Below is compilable code: struct ContentView: View { var body: some View { Text(Text) .onAppear() { print(test) } } } test is printed in the console after a new build, and when I go to the Home Screen and return to the app, but if I swipe up from the bottom, and then swipe up from the menu of apps to close the app, it does not print upon opening the app again. What would be an example of code that does run under the circumstance of fully quitting the app and opening it again?

Hey @DevForumPstr, Thanks for your questions. Please take a look at Optimize for the spatial web from WWDC24. This session introduces you to showing spatial photos on the web the using the element.requestFullscreen() method invoked by a user event. Additionally, you'll want also watch What’s new for the spatial web from WWDC25. This session covers presenting immersive video. You can embed this media on your website using the existing video element. For 180º, 360º, and wide field-of-view media, the file should conform to APMP. To learn more about APMP, watch Learn about the Apple Projected Media Profile. Let me know if you have additional questions, Michael

Thanks for your post. It appears that you are experiencing difficulties downloading the iOS 26 simulator runtime, which is hindering your ability to compile and test your code. Are you utilizing the most recent version of Xcode from the App Store? The versions on your log file show that you are. The issue seems to be related to a network connection. As it seems can dns com.apple.MobileAsset.iOSSimulatorRuntime? Please ensure that your network connection is stable and that there are no firewalls or network settings obstructing access to Apple’s servers. The error messages indicate a failure to establish a connection to a host, which may be attributed to network-related issues. Although your setup appears compatible, it is advisable to verify that macOS 26.1 and Xcode 26.2 are fully updated. Occasionally, point updates can resolve unforeseen issues with downloads or simulator installations. Attempt restarting your router, modem, and Mac to eliminate any temporary network glitches that may be interferin

Thank you for your post. May I request that you create a focused sample that developers in the forums can run and observe the results? When running a SwiftUI app designed for iPad on Mac Catalyst, it can be challenging to ensure that the UI scales appropriately and fills the available screen space. However I am confused your iPad target is an iPhone 17? Ensure that your main view is set to expand and fill the available space. You can try using to understand the available space and adjust your layout accordingly. Mac Catalyst provides specific modifiers and environment values you can leverage to better adapt your UI. Ensure that the Mac Catalyst app’s window toolbar isn’t consuming excessive space or causing layout issues. Test your app with different Mac resolutions or window sizes to confirm whether the layout issue is specific to certain dimensions or more general. Since you are using Xcode 26.2 (17C52), ensure that you are also on the latest version of macOS. I look forward to seeing your

// StoreView.swift import StoreKit import SwiftUI struct StoreView: View { @ObservedObject private var storeController = StoreActor.shared.productController var hasPro: Bool { storeController.isEntitled } var body: some View { if let product = storeController.product, !storeController.isEntitled { // Pro features available to the user TO PURCHASE if(product.displayName == ProductNames.pro.humanReadablePurchaseLevel()) { // Show the product in a nice way, using the properties of the `product` variable ProductRow(product: product) } } if(hasPro) { // The user has already purchased the pro version, so show the pro features } } } struct ProductRow: View { @ObservedObject private var storeController = StoreActor.shared.productController var product: Product var body: some View { Text(Upgrade to (product.displayName)) Text(product.description) // Purchase button Button { Task(priority: .userInitiated) { await storeController.purchase() } } label: { Text((product.displayPrice)) } } }