“iPhone 16 pro”

I am experience problem with three iPhone 13 Pro. They are reporting the lowest quality for all points in the depthmap from the Lidar sensor. The readings I get are unusable. If it was just one phone I would consider it a faulty sensor, but in this case it is three phones that gives the same result. I have other iPhone 13 Pro that works as expected. Have any else experienced a similar behavior? I am using iOS 18.4.1 https://developer.apple.com/documentation/avfoundation/avdepthdata/depthdataquality

Hi, An existing app on AppStore have issue with SHA256 Hash only since iOS17.4. And only Pro and Pro Max seems affected by this issue. NSData is read from downloaded file. Hash is calculated with unsigned char *CC_SHA256(const void *data, CC_LONG len, unsigned char *md) And compared with original HASH It appears different only on iOS17.4 and only Pro and Pro Max. But i can't reproduce this issue. Do you have an idea ? Thank you

Hello. In the Xcode 15 we were using this command in the terminal to run our tests on the Rosetta Simulator: xcodebuild -workspace CoreLibraries.xcworkspace -scheme CoreLibraries -destination 'platform=iOS Simulator,name=iPhone 15,arch=x86_64' test` In the Xcode 16 the same command doesn't work anymore. It produces the error: xcodebuild: error: Unable to find a device matching the provided destination specifier: { platform:iOS Simulator, arch:x86_64, OS:latest, name:iPhone 16 } Unsupported device specifier option. The device “iPhone 16” does not support the following options: arch Please supply only supported device specifier options. Running test directly from the Xcode UI using iPhone 16 (Rosetta) still works fine. Does anyone know how to modify the xcodebuild command to make it work again?

I don't get notified of messages (do not disturb is off and settings is set to on). I also can't share my location, and neither can my boyfriend on his phone as well. Please fix this.

Hello everyone, I am reaching out to you today regarding an issue I am encountering with a customer who owns an iPhone 15 Pro. The customer purchased a new screen protector for the device, but there is a problem with the fit of the protector in the corners of the screen. The protector does not adhere properly to the corners, and there is a small gap between the protector and the screen. As a result, there is a concern about damage to the screen in the event of a drop or bump. I have tried several possible solutions, such as thoroughly cleaning the screen and protector before installation, but the problem persists. Do you have any recommendations or possible solutions for this issue? I would appreciate any help you can provide in resolving the problem for the customer.

We are getting unreliable results on XCode Cloud tests. I'm not sure if it's related to the current service outage. I'm running a very simple XCTest UI suite, on some devices it succeds and it others it fails to start. I'm not getting a userful error message. MyApp-Runner encountered an error (Failed to prepare device 'iPhone 16 Pro Max' for impending launch. (Underlying Error: Unable to boot the Simulator. launchd failed to respond. (Underlying Error: Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding)))

Since I have changed of iPhone (yesterday) to run my draft application, I systematically, and instantaneously get a message The application failed to launch., i.e. the application successfully built and was downloaded to the new iPhone (Iphone 17 pro - iOS 26.4). I have checked that this new iPhone is well registered on my list of authorized devices. Could you help me to fix this issue ? Here is the verbose attached to the failure: The application failed to launch. Domain: com.apple.dt.CoreDeviceError Code: 10002 User Info: { BundleIdentifier = com.laurent-guise.ble-laser; DVTErrorCreationDateKey = 2026-03-30 07:59:46 +0000; IDERunOperationFailingWorker = IDELaunchCoreDeviceWorker; } The request to open com.laurent-guise.ble-laser failed. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x3868; } The op

I'm trying to run this example project: https://developer.apple.com/documentation/HealthKit/building-a-multidevice-workout-app When I run it on my device (iPhone 16 Pro and Apple Watch Ultra 2) I get this error: -[SPRemoteInterface _appRecoverAnyExtendedRuntimeSession:]_block_invoke:4350: Got no sessions back from -[CSLSSessionService existingRunningSessions:] or -[CSLSSessionService existingScheduledSessions:] after receiving a PUICInitializeSessionServiceAction I start the workout from my phone, which successfully starts the workout on the watch. But this callback is never triggered on the phone: healthStore.workoutSessionMirroringStartHandler { // not happening } This makes it difficult to learn the mirroring workout technique. I'm using Xcode 16.3 and Mac OS 15.4.1. Any help appreciated!

I noticed a bug on rotation change in my app on iPhone 14 Pro Max simulator. Basically a view in my view hierarchy is hidden when it shouldn't be. In landscape mode there isn't enough room for this view so I hide it on the iPhone (not essential). But when tilting back to portrait mode I unhide it. -(void)viewWillTransitionToSize:(CGSize)size withTransitionCoordinator:(id)coordinator { [super viewWillTransitionToSize:size withTransitionCoordinator:coordinator]; BOOL isIPhone = UIDevice.currentDevice.userInterfaceIdiom == UIUserInterfaceIdiomPhone; BOOL isIPhoneAndGoingLandscapeMode = (isIPhone && size.width > size.height); if (isIPhoneAndGoingLandscapeMode) { self.someView.hidden = YES; } else { self.someView.hidden = NO; } } So this view controller is presented modally (form sheet style). On iPhone 14 Pro Max on orientation -viewWillTransitionToSize:withTransitionCoordinator: is called twice and the size parameter is always: (CGSize) size = (width = 414,

I first applied a snapshot on the main thread like this: var snapshot = NSDiffableDataSourceSnapshot() snapshot.appendSections([.main]) snapshot.appendItems([], toSection: .main) dataSource.applySnapshotUsingReloadData(snapshot) After loading data, I applied the snapshot again using: Task { @MainActor in await dataSource.applySnapshotUsingReloadData(snapshot) } On an iPhone 13 mini, I received the following warning: Warning: applying updates in a non-thread confined manner is dangerous and can lead to deadlocks. Please always submit updates either always on the main queue or always off the main queue However, this warning did not appear when I ran the same code on an iPhone 16 Pro simulator. Can anyone explain it to me? Thank you

whenever i put on this sound https://youtu.be/0RMmDWNLRCk i hear a weird noise. Its not the sound itself, when i put on the sound at max volume and keep holding the volume up button even though its at max- i can hear what seems to be like like a helicopter (noise is hard to describe). I used this sound on my other iphones and i dont hear the weird noise. So im wondering if anyone else with the same iphone as me has this problem

iOS 18.2 (22C152) My phone is currently on lockdown mode and I have gotten alerts from Experian that my information is on the dark web as well as having to reset all my accounts. However this has not fixed the issue. Even if I hard factory reset settings etc the root makes its way very shortly after, if not immediately. Though I recently got these notifications and purchased the phone in Feb. 2024 the has been an ongoing issue for a few years. I can elaborate if needed. To make it short I have a reinstalled root on my phone. Apple nor Spectrum (who I have my phone with) have been able to assist with this issue. I have been able to clarify this ”hijacking” with the Geek Squad who didn’t want their legal team involved when asking for a report so the PD can do an internal cyber investigation. So, I’ve just lived with it. Let me know what your thoughts to resolve this issue would be before spending thousands to find a resolution on my own. Side note before asked: what I’ve been

I purchased an iPhone 13 Pro Max yesterday and traded in my iPhone 12 Pro Max. Prior to trading in, I backed up the 12 to my iMac, in addition to doing nighty iCloud backups. The 12 was running iOS 15.1 very successfully. The 13 won't accept a restore from the iMac because as received, the 13 has 15.0 installed. In the past whenever I have purchased a new iPhone, this problem was addressed by installing the Beta profile on the new phone, updating it to the latest beta, and then performing the restore. In the past it worked because the restore and the new (receiving) phone were both running the same beta version. This time it is not working. I can install the Beta Profile on the new 13 Pro Max but when I start the 15.1 download process, before trying to restore from the iMac, I get an error stating that 15.1 cannot be downloaded to the 13. I've tried several workarounds including but not limited to wiping the 13 Pro Max and starti

Feature request. Please attenuate the keyboard backlight on the latest iteration of the MacBook Pro at the lowest settings (for slightly more dimmign). It's far too bright.