“iPhone 16 pro”

When launching an app, AppStore Connect has some very specific requirements to the media (screenshots) used for the store listing. Right now the primary screenshots requires a 6.5 inch size. This is fine, of course, but why doesnt it list which iphones has this size, so I dont have to google my way to this answer? Its such a small thing, but would help so much

Hi everyone, I am an iOS developer from Ecuador and I am writing to ask if there's any way to fix my issue. After some initial struggling with my phone number not being able to receive Apple verification messages, I was able to register an Apple ID and use that Apple ID to enroll into the Apple Developer Program. Currently, I am stuck at the step of paying the subscription fee. When I try to pay for the 99$ enrollment fee, I receive an Order Acknowledgement e-mail from Apple but the payment is never processed. I have tried with multiple debit cards: 2 times with my main crypto debit card emitted from a Hong Kong bank 1 time with a debit card emitted from a local Ecuadorian bank 1 time with a debit card emitted from a US bank In all these cases the result is the same: the same order acknowledgement e-mail but nothing more happens. I even tried asking the support via e-mail (the only method that is supported in my country), but no one replies. Does anyone have any tip on how to overcome this situation?

Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections. What the app does: AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked. The core flow is: A user scans a license plate using their phone camera If the car owner is registered in the app, they receive an anonymous push notification (e.g., Your car with plate XX 1234 XX is blocking someone or Your lights are on) The car owner can then take action Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days. Why I believe it doesn't violate 1.1.1: The app does not expose any personal information. Notifications are fully anony

Hi everyone, I’ve been working on an experimental prototype called FaceBridge that explores whether Secure Enclave–backed biometric authorization can be delegated between macOS and iPhone using only public Apple APIs. The goal of the project was to better understand the architectural boundaries of cross-device trust and approval flows that resemble Apple’s built-in Touch ID / Continuity authorization experiences. FaceBridge implements a local authorization pipeline where: macOS generates a signed authorization request the request is delivered to a trusted nearby iPhone over BLE / Network framework the iPhone verifies sender identity Face ID approval is requested using LocalAuthentication the iPhone signs the approval response using Secure Enclave–backed keys macOS validates the response and unlocks a protected action Security properties currently implemented: • Secure Enclave–backed signing identities per device • cryptographic device pairing and trust persistence • replay

Im working on my laptop with Mac OS 15.7.5 and Im using Xcode 26.0.1 and Im trying to simulate the code I've written. It only allows me to simulate on iPhone 16e but it never finishes loading, I also tried using my personal iPhone as a simulator but that doesn't work either. Could it possibly be my storage on why the simulators don't work?

Area: CoreML / Machine Learning Describe the issue: On iOS 26.4, calling MLModel(contentsOf:configuration:) to load an .mlpackage model hangs indefinitely and eventually kills the app via watchdog. The same model loads and runs inference successfully in under 1 second on iOS 26.3.1. The hang occurs inside eort_eo_compiler_compile_from_ir_program (espresso) during on-device AOT recompilation triggered by MLE5ProgramLibraryOnDeviceAOTCompilationImpl createProgramLibraryHandleWithRespecialization:error:. A C++ exception (__cxa_throw) is thrown inside libBNNS.dylib during the exception unwind, which then hangs inside __cxxabiv1::dyn_cast_slow and __class_type_info::search_below_dst. Swift's try/catch does not catch this — the exception originates in C++ and the process hangs rather than terminating cleanly. Setting config.computeUnits = .cpuOnly does not resolve the issue. MLE5ProgramLibrary initialises as shared infrastructure regardless of compute units. Steps to reproduce: Create an app with an .mlpackage Core