show when run

The same happens when using Xcode 16.x and Xcode 26.x. It's a shame. I have to run apps with debugger detached, but it's suboptimal.

Have you also declared files in their lproj folders, for each language (en.lproj, it.lproj, fr.lproj…? They should contain at least the following files in each: May read this for further explanations: https://mixable.blog/why-does-the-ios-app-store-show-more-languages-than-my-app-supports/

Framework compatibility: My app uses Foundation Models and Apple Pencil. The app runs great through Xcode; however, due to Apple Pencil support, it has to be run on a physical device. However, Swift Playgrounds on iPad doesn't support iOS 26. I was just wondering if this is something that can be mentioned in submission notes. eg. The app needs to be compiled in Xcode but run on a physical device.” Or should we expect iPadOS 26 support for Swift Playgrounds by the time of submission? Thank you!

Here is a more step by step breakdown of the problem I have a iOS library that exposes a C function. This function is marked with default visibility and used via attribute tags to prevent the compiler/linker from stripping it #ifdef __cplusplus #define DYLIB_EXPORT extern C __attribute__((visibility(default))) __attribute__((used)) #else #define DYLIB_EXPORT __attribute__((visibility(default))) __attribute__((used)) #endif DYLIB_EXPORT bool say_hello_world(); #import helper_functions.h #import bool say_hello_world() { NSLog(@Hello WORLD 🟢!); return true; } From a dynamic library, called sdk, I want to call this function. In this example it's a Rust lib unsafe extern C { fn say_hello_world() -> bool; } #[unsafe(no_mangle)] extern C fn sdk_init() -> i32 { unsafe { say_hello_world(); } return 0; } When the app is compiled and launched from Xcode (either on debug or release schemes) then this works, the following snippet works and prints the hello WORLD message: #import OpacityObjCWrapper.h #import helper

Hi @1729k, currently Foundation Models does not support images as input. But depending on your app's needs you could consider pairing it with Vision, a computer vision framework that also runs on-device. Best, -J

I've been dealing with this for weeks now with no luck. I've been able to install iOS 17 on another machine running an older OS but the second I get into Tahoe, no simulators install.

The LaunchViewController removed and all orientations added on the general tab. any other settings? Your screenshot only shows the checkbox areas for the orientations. The section on the General tab for the Launch screen is scrolled out of view. You want it to look identical to the configuration you'd get if you selected File > New Project, so you can use that to compare the values you have set. Further, I can't see the contents of the Info tab, where you'd set the keys for UILaunchScreen. — Ed Ford,  DTS Engineer

@Vision Pro Engineer Thanks for the reply, Michael Is the following based off what you've heard or do you have videos and files that show the behavior? Mostly based off user testimonial. I think we have recorded a couple instances of this during onboarding sessions, but in those cases, we suspected that screen sharing itself could be contributing to the issue. Do you have any logging in place that is capturing any RoomCaptureSession.CaptureError errors in production? Yes - we track all fatal scanning errors. We haven't noticed an uptick in those. It seems like another developer was able to improve performance by resolving a memory leak. Have you profiled the application when performing multiple scans in a row? We have done some profiling over the years, but it's difficult because the act of profiling itself severely degrades scanning performance. We have noticed that RoomPlan itself seems to cache/retain resources after scanning even if we have no active references to it. I believe we reproduced this