“iPhone 16 pro”

[tldr version: all the point cloud capture apps rushed out an update when the iPhone 15 Pro was released because they were capturing far fewer points on that device. The same is observed with the new M4 iPad Pro. What was the fix for compatibility with these new devices?] I am running an ARKit replay file through Displaying a Point Cloud Using Scene Depth from WWDC20 and recording the ARConfidenceLevel values of the incoming ARDepthData. I am doing this side-by-side on an iPhone 12 Pro and an iPhone 15 Pro. The ARKit replay file was originally recorded on the 12 Pro. We get a certain percentage of points where the ARConfidenceLevel is not .high when running on the iPhone 12 Pro. It's varies a lot by frame but averages about 5% and is the same on all devices prior to the iPhone 15 Pro. The same test using the same iPhone 12 Pro replay file on an iPhone 15 Pro gives abo

I have a third-party app installed on my iPhone 16 Pro Max, and since yesterday I've been getting the following error: An internet connection is required to verify developer trust. Apple Development: Created via API (3GJ3LH6NRW). This app will not be available until it has been verified. Can you help me fix this? I've been told it should work again on its own in 2 to 4 days. I have a Developer account to sign apps and avoid problems; it's never given me any trouble until now.

I want to detect when the Hardware Camer control button is pressed/interacted in the iPhone 16 Does Apple provide any API to detect the Hardware Camera control button in iPhone 16?

This is a big bug connected with status bar show/hide.I have issue, because in my application status bar. always is shown, only when dismissing UIImagePickerController status bar is hidden.And I use prefersStatusBarHidden variable to fix this bug.This solution always works, except Xcode Version 11.4.In Xcode Version 11.4 this solution works nicely, too.But not works on the following simulators or devices iPhone 11, iPhone 11 Pro, iPhone 11 Pro Max.How can I fix this problem.

In my SceneDelegate via 'scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions)' I call the following code to assign a Storyboard: let storyboard = UIStoryboard(name: Main, bundle: nil) let initialVC = storyboard.instantiateInitialViewController() self.window?.rootViewController = initialVC The Initial VC is a UITabBarController. The app crashes when calling 'instantiateInitialViewController': *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' terminating due to uncaught exception of type NSException CoreSimulator 1047 - Device: iPhone 16 Pro (06A3EAF6-6623-49FD-BEFE

My barely 6-month old iphone 13 pro has this colossal camera issue. I think it happened after the latest update but being a professional dancer, I am constantly wanting to record videos (the sole reason I bought this super expensive phone) and thanks to apple and its horrible product, I am unable to do that. Nobody seems to be talking about it and I am amazed

Hello! The minimize behavior was working correctly while I was using Xcode 26 beta 4 with iOS 26 beta 4 simulator — when scrolling down, the Tab Bar would minimize as expected. However, after upgrading both Xcode and iOS simulator to beta 5, the tabBarMinimizeBehavior setting no longer has any visible effect — the Tab Bar stays fixed in place. Code snippet: if #available(iOS 26.0, *) { self.tabBarMinimizeBehavior = .onScrollDown } Steps to reproduce: 1. Create a UITabBarController with at least one tab containing a scrollable view (e.g., UITableView). 2. In viewDidLoad, set tabBarMinimizeBehavior to .onScrollDown. 3. Run on iOS 26 beta 5 simulator. Expected behavior (beta 4): Scrolling down hides/minimizes the Tab Bar with animation. Actual behavior (beta 5): Tab Bar remains fixed; no minimize animation is triggered. Environment: • Xcode 26 beta 5 (Build: 17A5295f) • iOS 26 beta 5 simulator (Build: 1055) – iPhone 16 Pro • Also tested on iPhone 13 mini – iOS 26 (Build: 23A5308g)

I am transferring data from iPhone 14 Pro Max, with IOS 17 beta, to another iPhone 14 Pro Max which is brand new. In order to do that, the new iPhone tells me I need to continue to be in the Beta Program. However, when I try to re-enroll through the new iPhone 14 Pro Max, the re-enrollment fails. There is no other message besides Re-Enroll FAILED. How can I solve this? I am unable to transfer at this point.

When a user swipes up to see the app switcher, I put a blocking view over my app so the data inside cannot be seen if you flick through the app switcher. I do this by receive notifications（UIApplicationDidBecomeActiveNotification, UIApplicationWillResignActiveNotification） But on my iPhone 16 Pro, iOS 18.4.1 test device, Face ID authentication via LAContext may not always result in App lifecycle notifications.This caused my blocking view not to be removed. any ideas about the notification changes caused by Biometric authentication？

I am currently in an iPhone 16 plus, running iOS 18.0 and I want to download the 18.1 beta for apple intelligence , I don’t even see “beta updates” under software updates… can anyone help?

Hello Guys, When using Xcode 14 (RC or 14.0.1) the Native Screen size differ from simulator to real device for the brand new iPhone 14 Pro and Pro Max causing my apps some bugs (because using the real device screen size for some computations). Just after app launch: log.info(Canevas Size: (UIScreen.main.bounds.width) x (UIScreen.main.bounds.height)) log.info(Native Size: (UIScreen.main.nativeBounds.width) x (UIScreen.main.nativeBounds.height)) Result iPhone 14 Pro (Simulator Output): Canevas Size: 393.0 x 852.0 Native Size: 1179.0 x 2556.0 iPhone 14 Pro (Real Device): Canevas Screen Size: 390.0 x 844.0 Native Screen Size: 1170.0 x 2532.0 Does anyone reproduce that? I do not own myself a real iPhone 14 Pro and can't investigate any further sadly. Do you know how I can get the real screensize in pixels?

I recently stumbled upon a peculiar issue that's causing automatic reboots on the iPhone 15 Pro and iPhone 15 Pro Max. It appears that setting an extremely high value for gyroUpdateInterval can lead to this problem, but interestingly, the iPhone 15 doesn't exhibit the same behavior. Here's the code in question: - (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event { self.motionManager = CMMotionManager.new; self.motionManager.gyroUpdateInterval = 3600; // The problematic line [self.motionManager startGyroUpdatesToQueue:NSOperationQueue.mainQueue withHandler:^(CMGyroData * _Nullable gyroData, NSError * _Nullable error) { NSLog(@Gyroscope data: %@, gyroData); }]; } It's worth noting that when I set gyroUpdateInterval to a more reasonable value like 60 (or omit it, as it uses a default value in that case), the reboots don't occur on the affected devices. I have tested this behavior on both the iPhone 15 Pro and the iPhone 15 Pro

Where can I find the documentation of the Genlock feature of the iPhone 17 Pro? How does it work and how can I use it in my app?

I'm unable to reset simulators using the menu or the xcrun simctl tool: == Devices == -- iOS 17.5 -- iPhone SE (3rd generation) (5A06623A-173D-4C96-8DD3-3E9FE39A06F1) (Shutdown) iPhone 15 (iOS 17.5) (F4329E8D-29BB-4EA7-8465-C11A98D04ED7) (Shutdown) -- iOS 18.0 -- iPhone SE (3rd generation) (2DDE8F03-F8E1-4C1B-8E28-CD9B208F3FFA) (Shutdown) iPhone 16 Pro (DE788688-8AC6-40A0-B25C-A56AA423798E) (Shutdown) iPhone 16 Pro Max (1405184C-36A9-40F3-B0D0-4EEB88452883) (Shutdown) iPhone 16 (0CBBA7DB-B20E-4F17-BBC5-910F1F6E1A0A) (Shutdown) iPhone 16 Plus (95421C27-11A0-4FCF-A889-DAAE8557B271) (Shutdown) == Device Pairs == ~/Library`` ❯ xcrun simctl erase 0CBBA7DB-B20E-4F17-BBC5-910F1F6E1A0A An error was encountered processing the command (domain=NSCocoaErrorDomain, code=513): “data” couldn’t be moved because you don’t have permission to access “Deleting-8FEDFF47-5B2F-4534-BCA2-036BBE68CE37”. You don’t have permission. To vi