iPadOS 17.7.7

On XCode 14.3.1, downloading support files for iPadOS 17, fails with message: **Could not locate device support files You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com. [missing string: 869a8e318f07f3e2f42e11d435502286094f76de]** on XCode 15.0 beta (15A5160n), iPad does not show up. Have rebooted Mac, iPad, Settings > Clear Trusted Computers => no iPad in XCode 15 => missing support files message on XCode 14.3.1 Am stuck. How to get unstuck quickly?

Under iPadOS 18, I would like the main content to remain the same size regardless of whether the tab bar is hidden or visible. Is there an easy way to do this?

Sample Project In iPadOS 26 beta4, when a UISplitViewController transitions to compact layout and proposes the secondary view controller, a crash occurs: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Layout requested for visible navigation bar, ; layer = > delegate=0x102826600, when the top item belongs to a different navigation bar. topItem = title='Detail' style=navigator rightBarButtonItems=0x600000011e10, navigation bar = ; layer = > delegate=0x102826000, possibly from a client attempt to nest wrapped navigation controllers.' When we show the primary view, there is no crash. Similarly, there is no crash on beta-3. To reproduce the crash in the demo project: Launch the project on an iPad. Try the Demo Tap List-Detail Pattern To trigger the crash, select any of the list items and switch the app to a compact layout. The crash occurs because the app will attempt to propose the secondary view controller. To avoid the crasah, refrain from selecting an

Question asked during the 6-6-23 UIKit Q&A Slack session of WWDC 2023 My iOS / iPadOS / Catalyst app has a thumbnail extension with a QLThumbnailProvider subclass that implements the provideThumbnail(for:_:) method providing the thumbnail for a document created in my app, by drawing the thumbnail image into the current context. That implementation successfully updates the thumbnail for the document, but sometimes the thumbnail's displayed image (in, for instance, the Files app or my app's own UIDocumentBrowserViewController on iPhone or iPad) is slow to update. (This update slowness seems especially to be a problem for documents stored in iCloud Drive, rather than in local storage.) (1) Am I correct in presuming that the displayed thumbnail images are cached somewhere, and the reason the displayed thumbnail images are slow to update is because either (a) the thumbnail cache is slow to update and/or (b) the system only periodically calls the provideThumbnail(for:_:) method? (2) If so, is there som

I’m following the example code from Apple to implement the new iPadOS 18 TabView() with the new Tab(). While the tabbing itself is working fine, I can’t get it to show up a (large) navigation title in the sidebar (like the Home or Files app). I’ve tried placing .navigationTitle(App Name) at the TabView, but that doesn’t work. Is it possible to do this in any way or is this not recommended to show? TabView { Tab(Overview, systemImage: film) { Text(Put a OverviewView here) } TabSection(Watch) { Tab(Movies, systemImage: film) { Text(Put a MoviesView here) } Tab(TV Shows, systemImage: tv) { Text(Put a TVShowsView here) } } TabSection(Listen) { Tab(Music, systemImage: music.note.list) { Text(Put a MusicView here) } Tab(Podcasts, systemImage: mic) { Text(Put a PodcastsView here) } } } .tabViewStyle(.sidebarAdaptable) .navigationTitle(App Name) .navigationBarTitleDisplayMode(.large) I know that there is also the .tabViewSidebarHeader() modifier, but that adds any view above the scroll view content. Neither

We are developing driver for our USB device. Our approach is to run and test driver on macOS first and then verify on iPadOS 16. In the driver we add custom property -kUSBSerialNumberString into default properties: OSDictionary * Driver::devicePropertiesWithSerialNumber() { kern_return_t ret; OSDictionary *properties = NULL; OSDictionary *dictionary = NULL; OSObjectPtr value; const IOUSBDeviceDescriptor *deviceDescriptor; deviceDescriptor = ivars->device->CopyDeviceDescriptor(); ret = CopyProperties(&properties); value = copyStringAtIndex(deviceDescriptor->iSerialNumber, kIOUSBLanguageIDEnglishUS); Log(Serial number: %{public}s, ((OSString *)value)->getCStringNoCopy()); dictionary = OSDictionary::withDictionary(properties, 0); OSSafeReleaseNULL(properties); if (value) { OSDictionarySetValue(dictionary, kUSBSerialNumberString, value); OSSafeReleaseNULL(value); } return dictionary; } next in kern_return_t IMPL(Driver, Start) we call SetProperties: ret = SetProperties(devicePropertiesWit

Hi, in the Run your iPad and iPhone apps in the Shared Space session video, it is mentioned that all suitable iOS/iPadOS apps will be made available in the visionOS app store by default. I'm wondering if someone could share the criteria that will be used to determine if an iOS/iPadOS application is suitable for visionOS?