iPhone 16 pro

I coded my mobile app using Cursor and have recently been building and submitting for TestFlight using XCode version 16.1. I am testing using my Iphone via the downloaded build from TestFlight. My onboarding flow goes smoothly, but when I reach the checkout page I receive an error that says Error Loading Products. When I select OK and then try to click one of my available products I receive another error that says Products Not Available. I am signed out of my main Apple ID and signed into a Sandbox user that is valid. I have all of my application agreements signed and valid. I believe everything is configured properly, but I have been receiving purchase errors for the past week with no progress. I had one semi-successful attempt where the Apple payment screen appeared, but have not had that since. Even on that attempt, there was a payment failure afterwards as well. Any help would be greatly appreciated. I would like to get a build submitted for app store review as soon as possible. I've attached scr

Hello, I programmed a universal app and is was released on the App Store: https://apps.apple.com/app/ble-scout/id6752802063 I think I did all necessary settings in XCode: It also shows both architectures in the Archive view: But when trying to install it on my M3 MacBook Air I get this error message: On the apps page in the App Store it shows that it would run on this Mac. Strangely I can install it on my older Intel MacBook Pro and a friend can even install it from the App Store on his M4 MacBook Pro. All run either MacOS 15.6.1 or 15.7. Another friend cannot install on M3 MacBook. Anyone having any clue what's missing? It's my first app to distribute on the App Store, so sort of new into this. Thanks, ER!K

open var isAnimating: Bool { get } /// The preferred treatment to use for HDR images. By default the image view will defer to the value from its traitCollection. open var preferredImageDynamicRange: UIImage.DynamicRange /// The resolved treatment to use for HDR images. open var imageDynamicRange: UIImage.DynamicRange { get } This attribute is not marked as being applicable only in iOS 17+ versions. When viewing the UIImageView code in Xcode, the @available(iOS 17.0, *) annotation was not added, which resulted in successful compilation but caused a crash on iOS 16 devices.

Hello, my call blocking app was incorrectly rejected under Guideline 2.5.12 for using SMS Fraud Extension, but my app is a call blocker that only uses CallKit framework exclusively for blocking unwanted phone calls. There's no SMS functionality or SMS/Message frameworks at all and no pre-made spam lists. I've submitted an appeal, but this is a time-sensitive update that needs to be released as soon as possible (used an Expedited Review request already). I had a previous appeal for another app that was delayed for 11 days, and it was only resolved after posting here. I cannot afford another 11-day delay for this time-sensitive update. Any suggestions to make the process faster? Thank you.

Hello ! Currently, we have customers who use about 5,000 devices. In the case of ios26, the phone number is not acquired overall, and 18.x, 17.x, and 16.x are all acquired in half and not acquired in half. https://developer.apple.com/documentation/devicemanagement/deviceinformationcommand/command-data.dictionary/queries-data.dictionary It seems that it is the right behavior not to acquire it on the specification sheet. However, I wonder when it became impossible to acquire. (There are devices that can be acquired and devices that can't be acquired in the same os version.) Will the devices that are being acquired be blocked someday? When it was developed in 2019, it was in a state that could be acquired in full. I would also like to ask if there is an alternative way to get your phone number. Thank you.

Hello everyone, I'm implementing the new AVInputPickerInteraction API on iOS 26 to allow users to select their microphone from a custom settings menu before recording. The implementation seems correct, but I'm encountering a strange issue where the input selection immediately reverts to the previous device. The Situation: The picker is presented correctly via a manual call to .present(). I can see all available inputs (e.g., iPhone Microphone and AirPods). The current input is iPhone Microphone. I tap on AirPods. The UI updates to show AirPods as selected for a fraction of a second, then immediately jumps back to iPhone Microphone. The same thing happens in reverse. It seems like the system is automatically reverting the audio route change requested by the picker. My Implementation: My setup follows the standard pattern discussed in the WWDC sessions. Setup Code: This setup is performed once before the user can trigger the picker. @available(iOS 26.0, *) var inputPickerInteraction:

Hi, in the Human Interface Guidelines, Apple writes: Avoid using a segmented control in a toolbar. Toolbar items act on the current screen — they don’t let people switch contexts like segmented controls do. Along with this image: Source I'm confused by this example. The screenshot seems to be showing a segmented control in a toolbar. Is this saying that the Phone app's All/Missed toggle is different from a segmented control? Under iOS 26 it seems to take a different style compared to a regular segmented control. If so, which component is used to create this filter? Could you please clarify the guidelines? Thank you.