iPhone 16 pro

Thanks so much, @tbartelmess1—this is super helpful, and really appreciated a bit more context from our app: App context (what we store) The blobs we persist will be user-generated cruise photos, we would downsize those to more manageable size as iphone format photos can be quite big, but they would still be in the 1-3 mb after downsizing Realistic volume per active user: a few hundred images/year; heavy users could reach low thousands over time. Decision: use Core Data Binary Data + “Allows External Storage” We’ll keep originals as Binary Data (Allows External Storage) so Core Data handles externalization transparently, my philosophy has always been to offload as much work to the system services as possible. We’ll keep thumbnails as well inline in coredata (let coredata decide but likely will be inline (blob)). CloudKit mirroring We’ll rely on NSPersistentCloudKitContainer mirroring; we understand CloudKit decides when an attribute becomes a CKAsset independently of Core Data’s externalization thres

After quite a lot of testing, I found an elegant workaround. I believe the issue is that WebKit on phones has strict memory limits, and YouTube's playlist mode accumulates memory by preloading/caching multiple videos simultaneously, causing the WebContent process to crash on the second or third video. So Instead of loading a YouTube playlist directly, I fetch the playlist's video IDs once, then load and play individual videos one at a time using loadVideoById(), preventing memory accumulation and eliminating crashes.

It is unfortunate that this is a consumer question about how to save space on an iPhone. While I can provide my personal opinion, I must admit that I am not an expert in this area. If you are running out of space on your device due to photos and videos, you can go to the settings -> iPhone storage and implement one of the recommended ways to save space. One option is to keep images and videos on iCloud storage instead of on the iPhone, and only see a thumbnail. However, other forum members may have more effective suggestions. Albert Pascual
  Worldwide Developer Relations.

Hi! I am not getting an error, the watch is simply not shown in the Devices view. I see my iphone, not the watch. The watch is properly connected to my iphone. I've gone through all the usual suspects (restart all, remove trust, remove this and that, restart again, etc.)

Hi, thanks for mentioning the .exp file approach. This works well with the scenario I explained above (dynamic framework depending on static libs). However, when I tried this with a slightly different project configuration, I faced linker errors. I replaced the static libs with dynamic libs. So, now I have a dynamic framework with 3 target dependencies, each being a dynamic library. This project builds and runs fine when tested on the iOS simulator. But according to our other discussion here, when I test this on a real iPhone, it builds fine but fails at runtime with a linker error: 0_abort_with_payload and Xcode shows the following assembly instructions specifying the error Thread 1: signal SIGABRT - dyld`: 0x1aa0a15f8 <+0>: mov x16, #0x209 0x1aa0a15fc <+4>: svc #0x80 -> 0x1aa0a1600 <+8>: b.lo 0x1aa0a1620 ; <+40> 0x1aa0a1604 <+12>: pacibsp 0x1aa0a1608 <+16>: stp x29, x30, [sp, #-0x10]! 0x1aa0a160c <+20>: mov x29, sp 0x1aa0a1610 <+24>: bl 0x

Hi @377632523@qq.com, I'm unable to reproduce the issue, as reported, in my own Xcode project. Because the provided example above will not build successfully due to missing types, I replaced your implementation with the following: import SwiftUI struct PhotosMainView: View { @State private var searchText: String = var body: some View { TabView { Tab(Library, systemImage: photo.on.rectangle) { NavigationStack { scrollView(colors: [.red, .orange, .yellow]) .navigationTitle(Library) } } Tab(Albums, systemImage: square.grid.2x2) { NavigationStack { scrollView(colors: [.yellow, .green, .teal]) .navigationTitle(Albums) } } Tab(Search, systemImage: magnifyingglass, role: .search) { NavigationStack { scrollView(colors: [.blue, .purple, .pink]) .navigationTitle(Search) .searchable(text: $searchText) } } } .tabBarMinimizeBehavior(.onScrollUp) .tabViewStyle(.sidebarAdaptable) .tabViewBottomAccessory { TimelineAccessoryView() } } // Trivial helper view to visualize scrolling. @ViewBuilder func scrollView(colors: [Color]

If you ask for a user action, there may be some possibilities: https://support.apple.com/en-gb/guide/iphone/iph3ff83f3b1/ios But I do not see if white lists are possible or only black lists.