iPhone 16 pro

I do not think it is related to China as I live in Europe and get the same problem on my work MacBook Pro. The weird thing is that I get mixed results from a playground in Xcode (see attached pictures). Both ready to go and Model assets are unavailable. My managed macBook Pro has a profile that blocks only two things from Apple Intelligence: Allow integration with external intelligence services (macOS 15.2 or later) Allow Apple Intelligence: external intelligence workspace IDs (macOS 15.3 or later) I'm on Tahoe 26.0.1 and Apple M2 Pro. Any suggestion to allow me to run Foundation Models on my Mac? (At home, on my private MacBook Pro, everything works as expected)

interferon, It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. You wrote: How much should I worry about this error? That depends on what the backtrace looks like. If the backtrace leads to your code, that’s something you should worry about. If the backtrace only shows system code, that makes this log noise, as defined here. [quote='860615022, pi80223, /thread/802423?answerId=860615022#860615022, /profile/pi80223'] I've seen this error message too when running a very simple SwiftUI app [/quote] I tried that here in my office and didn’t see the log. Specifically: Using Xcode 26.0.1 on macOS 15.6.1, I created a new project from the macOS > App target, choosing SwiftUI as the language. I ran that on my iOS 26.0 (23A341) test device (by a strange coincidence, it’s also an iPhone 16). I waited for 10 seconds. Then swiped up from bottom to send it to the background. And it’s a bummer I can’t reproduce it because I might be

[quote='856112022, Evozi, /thread/73148?answerId=856112022#856112022, /profile/Evozi'] How about iOS 26? [/quote] AFAICT the limits are unchanged on iOS 26. If you’d like to see bigger limits, the best way to get that feedback in front of the folks who have the power to enact change is file it in Feedback Assistant. Make sure include details about what you’re trying to do and why the current limits are negatively affecting your users. Please post your bug number, just for the record. Also, keep in mind that iOS 26 runs on old devices which are significantly more memory constrained than the shiny new hardware you might be using. My daughter may one day have to give up her iPhone SE (2nd generation), and thus accepted the new reality of Face ID, but today is not that day (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860505022, jameseasylog, /thread/799838?answerId=860505022#860505022, /profile/jameseasylog'] I would guess this is because iOS 16 and earlier doesn't have Sectigo root certificates loaded [/quote] It’d be better to check rather than guess. Which brings me back to this comment: [quote='857543022, DTS Engineer, /thread/799838?answerId=857543022#857543022'] There’s a bunch of links … in Networking Resources. [/quote] Networking Resources include various links to the Apple Support articles that explain which root certificates are installed on which versions of iOS. I’m not able to speak for Sectigo, obviously, but a quick ’net search for Sectigo Public Server Authentication Root R46 suggests that they are in the process of transitioning from one root to another. If iOS 16 compatibility is important to you, I recommend that you discuss this with them. It’s possible that they might have some advice for how to tweak your server to be compatible. Share and Enjoy — Quinn “The Eskimo!” @ Deve

func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) { let deviceType = UIDevice.current.userInterfaceIdiom == .pad ? iPad : iPhone let tokenString = deviceToken.map { String(format: %02.2hhx, $0) }.joined() print(🎉 didRegisterForRemoteNotificationsWithDeviceToken CALLED on (deviceType)!) print(✅ APNs device token registered on (deviceType): (tokenString)) Messaging.messaging().apnsToken = deviceToken // Give Firebase a moment to process the APNs token DispatchQueue.main.asyncAfter(deadline: .now() + 0.5) { [weak self] in self?.fetchFCMToken(reason: apnsRegistered) } } This method is not being called. Tested device: Ipad Air - iOS 26.0(Simulator) also in real iPad. xcode 26.0.1

Although the code may not be using the best or latest practices, that is not the main concern. It seems that most methods that modify the layout of the tableView, either directly or indirectly, results in the strange auto scrolling behavior. Or maybe the issue is triggered when the tableView does not fill the entire view. The mechanics of the bug are not fully known. The conditions behind this do not seem to make sense. navigationControllerWithVC.navigationBar.isTranslucent = false for example, may not be using best practices, but why does that cause the table to start auto scrolling when being reloaded? The same can be asked for the safeArea top anchor scenario in the original code. Disregarding all of the navigation bar stuff, consider another case where we may want to present a label or some other content above the tableView. If the setupTableView() function is replaced with the code below, this will also trigger the auto scrolling issue: func setupTableViewWithLabelAbove() { tableView.delegate = self tabl

I've seen this error message too when running a very simple SwiftUI app (built using Xcode 26.0 (17A324)) on my device (iPhone 16 running iOS 26.0 (23A341)): Start the app Wait 10 seconds Send the app to the background. No other user interaction is necessary. The LLDB statement you provided does catch the location of the error message. But the stack trace is not helpful, as non of my code is involved. But what I've seen is that the error message is written to the console when the app is sent for the first time to the background. It doesn't appear anymore afterwards. The call stack I've captured is: #0 0x00000001a74e1280 in os_log () #1 0x00000001914d4218 in ___lldb_unnamed_symbol7481 () #2 0x000000018b2855c0 in ___lldb_unnamed_symbol14749 () #3 0x00000001914dc944 in ___lldb_unnamed_symbol7669 () #4 0x00000001914dce24 in ___lldb_unnamed_symbol7677 () #5 0x00000001de688520 in partial apply forwarder for closure #1 (Swift.UnsafeMutablePointer>) -> τ_0_0 in Observation.generateAccessList&l