“iPhone 16 pro”

Thanks Kevin. I've closed the feedback report as I don't have any new information to share, but I have to say I'm disappointed in the outcome. I don't think this answer actually holds up. Here is how I understand it: I plug in a monitor. Its default resolution is 4k at 240Hz. Fine, I shouldn't be able to plug in another monitor. I change the one monitor to 4K at 120Hz. Now the laptop has one monitor plugged in, running at 4K at 120Hz. I plug in another monitor. Its default resolution is 4k at 240Hz. I understand this is a problem because it would require both of the two display 'pipes' as you described above. But why should this be my problem to deal with as the customer? I have no qualms running the second monitor at 4K 120Hz, same as the first monitor. Why isn't the MacBook Pro M5 dropping this second monitor to 4K 120Hz? It's a resolution and refresh rate that's fully supported by the monitor. Alternately, why can't I set up a display profile that's unique to the monitor, at the supported 4k 120Hz

Albert, thanks for the reply. Remote hosted Live Activities I believe is a iOS 26.x system feature → No developer adoption. My steps: Preparation: Make sure iPhone and Mac (and/or Watch) are signed in with the same AppleID New iOS Project New Widget target, using standard template (In the new target UI also check that you want the live activity) Build and run to a physical iPhone Notice Live Activity exists on iPhone, Mac and Apple Watch [Example: From macOS, iOS Live Activity appears] In this case, I haven't built for any other platforms at all. I believe this is a feature, but I'm attempting to understand what I need to do to make it stop showing up in places that don't make sense for this app. Just made a simple project using the Xcode templates provided, then start the live activity on app launch. https://github.com/ioloro/LiveActivityWillTravel Thanks, John Marc

Thank you for your post. I must admit that I am not entirely clear on your question regarding creating a Live Activity for a remote hosting environment. I believe I may have misunderstood your inquiry. Could you please provide me with additional details to clarify your objectives? As currently, Live Activities are designed primarily for iOS devices, and they appear on the Lock Screen and Control Center. December 16, 2025 Updated guidance for all platforms, and added guidance for macOS and CarPlay. https://developer.apple.com/design/human-interface-guidelines/live-activities/ If you want to bring Live Activities to Apple Watch: https://developer.apple.com/videos/play/wwdc2024/10068/ Including the documentation for the live activities guide. The widget configuration api to position a widget: https://developer.apple.com/documentation/swiftui/widgetconfiguration/disfavoredlocations(_:for:) Thanks, Albert Pascual
  Worldwide Developer Relations.

I am testing my iOS app on iOS 18. I performed 50 tests, and in 43–44 of them, the app successfully detects beacons, relaunches in the background, and continues BLE communication. Testing how? What are the details of the process you're actually using to test this? That is, are you: Artificial Testing” -> Laying the phone on a desk next to the beacon and toggling the beacon (or shielding the phone) on/off to simulate entry and exit. VS. Real World Testing” -> Carrying the phone around in your pocket and seeing what happens. Beyond that, what are the broader parameters of the test itself? How far is the device from the beacon? How long is the device exposed to the beacon? What's the broader use case you're trying to implement? Most importantly, what, if anything, do you know about EXACTLY what was happening when the failure occurred? I want to understand why beacon triggers are inconsistent in iOS. What are the common reasons behind iOS not relaunching the app for beacon events,

Thank you so much! Very helpful! I put a watch screen shot on a watch device (Band and face) along with an iPhone shot as one of the iPhone screen shots. Then the watch screeshots are just the barebones screen shot from the device itself. I appreciate the advice!

There have been some behavioral changes on N1 chip devices; especially in areas where the BT spec has not had a single way of interpreting things. We have been observing these changes and changing them back if appropriate and are considered regressions. So, the first thing you should do is to test all this in the latest iOS 26.3 and see if anything has changed from your earlier observations. Also, there would have been some changes on patterns of use that were never meant to work, but just happened to work, and those would have been corrected. For example, scanning without services is not supposed to work, and was never expected to work in the background. If you are scanning in the background without services, and whatever the Flutter library may have been doing to work around that limitation (if anything), and that has stopped working, you can consider that a bug that has been fixed. Similarly, advertising packets in the background have always been on a best effort basis. Also, it has always been possible th

Whether iOS provides any mechanism or API that allows iPhone apps to trigger or request parental re-approval after the application has already been installed PermissionKit has that for you: https://developer.apple.com/documentation/PermissionKit/SignificantAppUpdateTopic Also from which iOS version this capabilities will work & how to handle lower iOS version which is not supporting. The APIs seem to only be supported in iOS 26.2 and above. The laws say that A developer shall verify through the app store's data sharing methods.... Since Apple has not provided any data sharing method for users on iOS versions before 26.2, my interpretation is that we do not need to do any age verification for users on older versions of iOS, but I can not be sure at this time and this is not legal advice. I doubt Apple will provide any recommendation since doing that could be considered legal advice. The only way we will know for sure though is for the deadlines to pass, a law to come into effect, a relevant law su