You can’t use any of the Apple Intelligence features on the simulator. You have to use a physical device.

Fixed in iOS 18.2 beta 2

This issue continues to be present in iOS 18.1 beta 7. Your documentation says it can be used with TextField, but it doesn't seem to work. Any idea when this will be fixed?

Feedback ID: FB15281821

Fixed in beta 4!

Solved in the latest Xcode 16 beta

@B347 the old site had a full list of tags that existed on the site, which contain discussions about very specific parts of the APIs. The search bar is not a sufficient alternative for this and doesn't even have autocomplete. This was how it looked on the old site: On the new site, the topics are less specific. For example, the network extension discussions are grouped alongside other networking discussions in a general networking topic. The tags to the specific networking APIs should be shown on the networking sub-topic at least.

Is there no way to browse by tag anymore? That's one thing I liked about the old site.

This is still happening with Xcode 15.3 RC 2. Any update from Apple regarding this issue?

Is “Make iPhone and iPad apps available on Apple Vision Pro” enabled for the testing group?

Noticed this as well. But IAPs are working in the simulator.

I have noticed on this page that the app icon can be changed on visionOS. But when I try to use UIApplication.shared.setAlternateAppIcon I get an error on the log saying the feature isn’t supported. Could anyone from Apple please clarify this?

At the moment you cannot mention Vision Pro in your iOS or macOS store listing. You can only mention it for your native visionOS listing. Since your app will run on the Vision Pro as an iPad app it is considered part of the iOS listing and not visionOS.

Go to Xcode build settings and change Base SDK to visionOS.

What are your logs showing? I'm having issues as well on both iOS 17 and watchOS 10. The most interesting part is this: ("CoreData: CloudKit Setup"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this. Also, do you see your app contacting iCloud servers in app privacy report?