Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Dear Richard, Thank you for reply! Yes, I would like external device (MacBook) to display the same content as iOS device. I use fully programmatical approach. Sorry for the misleading information provided, by saying window has already been created I meant that the instance of UIWindow and its rootViewController has already been created, before I enabled Screen Mirroring. After enabling Screen Mirroring I see the instantiation of second UIWindowSceneDelegate and willConnectToSession of the second instance is supplied with new scene instance. For my app this is actually the same as creating new instance of my app. To avoid creating second instances I've placed the following code: if(connectingSceneSession.role == UIWindowSceneSessionRoleExternalDisplayNonInteractive) { return nil; } in AppDelegate's configurationForConnectingSceneSession method. But this is not documented, and I am not sure if this will work for all cases. In willConnectToSession. It takes place after connecting to the AirPlay receiver

@kelin Hello, my friend, I have also encountered the same problem. However, for my new Icon, I used a normal PNG image and the full-size format. But when I published it to the AppStore build, it still reported an error indicating that the resource was missing and could not be found.

We tried to use the same exact sample project with the same bundle id instead of using our own bundle id now we get this error: mapError unexpected error domain NEVPNConnectionErrorDomainPlugin code 7 Received filter status change: serverSetupIncomplete We tried to follow this guide for the log but https://download.developer.apple.com/iOS/iOS_Logs/VPN_Logging_Instructions.pdf But it doesnt work on this step: . Trigger a sysdiagnose by simultaneously pressing and releasing both volume buttons + Side (or Top) button. Notes: The sysdiagnose is triggered upon button release. On an iPhone you will feel a short vibration when a sysdiagnose is successfully triggered Also I attached the console log here Console log

App Store URLs change with renames but old links redirect so ASO impact is minimal

Hello, you’re absolutely right. The same thing is happening to me on iOS 26.2.1 as well. If I tap it quickly while the subview is still loading, the menu shoots up toward the top of the screen. I’ve tried everything, but it’s caused by the time it takes for the view to process. If you disable it for 1 second until the view is fully loaded, it no longer misbehaves. If I put it in a ToolbarItem positioned at .topBarTrailing, no matter how quickly I tap it, it doesn’t behave strangely. Weird

Thanks for providing this, do you have the same results when you run it on a newer simulator as it seems like you still using 18.5 and 26.0? Have you tried a simulator in 26.2? I believe this was an issue on previous versions, please do update Xcode, macOS and use the latest simulators. Albert Pascual
  Worldwide Developer Relations.

Will definitely file bug for clarification. Actually, I verified for another flow where FilterDataProvider is responding with NEFilterNewFlowVerdict.allow() & TransparentProxyProvider is responding with NO. So both FilterDataProvider & TransparentProxyProvider are not interested in this flow, still we see the log line (NetworkExtension) [com.apple.networkextension:] provider rejected new flow TCP headless_shell[{length = 20, bytes = 0xe69023e655b6065e1a2f94fa508807fa43f6ac8a}] remote: 100.72.0.3:443 interface utun9 posted by NetworkExtension framework. Is this logline faulty or not to be taken at its face value ?? This really causes confusion amongst customers when they are trying to debug any network issues.

Hey @DTS Engineer thanks for your reply. I am using the release version, no Beta. Xcode Version 26.2 (17C52) Simulator iPhone 13 mini, iOS 18.5 Version 26.0 (1062.1) SimulatorKit 954.5 CoreSimulator 1051.17.7

Hi @SuyashBel, To run Foundation Models in Simulator, ensure that macOS is up to date. Utilizing Foundation Models framework in the Simulator requires macOS Tahoe, with Apple Intelligence enabled on the Mac. (System Settings -> Apple Intelligence) This will trigger a download of the model, which can also take a little time. Additionally, make sure the simulator is running 26 or later. It can also be helpful to ensure you're using the latest version of Xcode. If everything is updated and you're still having trouble, try restarting your Mac. If all that still fails, let us know and also please file Feedback so we can track this issue. Best, -J

Thanks for your post. Please check this post about this issue here: https://developer.apple.com/forums/thread/807280 Last Update? beta or release? Can you provide the version of Xcode and Simulator? What's that simulator iOS version? Albert Pascual
  Worldwide Developer Relations.