iOS is the operating system for iPhone.

Posts under iOS tag

200 Posts

Post

Replies

Boosts

Views

Activity

Persistent scroll stutter on iPhone 17 Pro Max, 18 Pro Max and 18 Pro (iOS 27.2), also on Apple Store demo units
Affected devices (all show the same problem): 1x iPhone 17 Pro Max 2x iPhone 18 Pro Max 1x iPhone 18 Pro Many demo iPhones at several Apple Stores Current iOS version: 27.2 Issue: Vertical scrolling inside apps frequently stutters and drops frames. It happens in many, many apps, including Apple's own App Store and Apple Store apps. During a normal flick-and-decelerate scroll, the content repeatedly freezes for one or more frames and then jumps forward. Because this reproduces on four of my own devices and on many Apple Store demo units, I believe it is a widespread, system-level issue, not a defect of a single device or my settings. Impact: I have been living with this for more than six months. I use my iPhone heavily every day, and the constant stutter has made using it genuinely distressing. Everything else about iPhone feels excellent, which makes this problem even harder to accept. Steps to reproduce: Open the App Store app (or almost any app with a scrolling list). Scroll with a normal flick and let it decelerate. Observe repeated hitches during the scroll. Measurements: I filmed the screen with a second iPhone at 4K 120 fps and measured content movement frame by frame: iPhone 18 Pro Max, third-party video feed: about 4 hitches per second of scrolling, about 4% of frames dropped, mostly single-frame drops. iPhone 18 Pro Max, third-party social app list: about 11 hitches per second, about 12% of frames dropped, at a regular rhythm every 6-8 frames. About a third of the stalls last 2-3 frames, and the content does not catch up afterwards. iPhone 17 Pro Max, third-party comment list: about 5 hitches per second, about 8% of frames dropped, including several full freezes of 50-75 ms. Expected: Smooth 120 Hz scrolling, as ProMotion is designed to deliver. Is Apple aware of this issue? I am happy to provide videos, frame-by-frame data, or sysdiagnose logs.
4
2
386
23h
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
0
0
35
1d
ATT prompt not shown and status stays notDetermined: how do you handle it?
Hello, our Unity game (iOS/iPadOS) requests App Tracking Transparency on its first scene, before ads are initialized. Background App Review rejected an earlier build under Guideline 2.1(a) for a blank screen on iPad Air 11-inch (M3), iPadOS 27.0. In that build we called requestTrackingAuthorization right at launch and then waited until trackingAuthorizationStatus was no longer .notDetermined. The status never changed, so the app never left the first screen. Current flow (this build was approved) Wait until UIApplication.shared.applicationState == .active and the app has focus. Call requestTrackingAuthorization(completionHandler:) once and wait for the completion handler. If the completion returns .notDetermined, wait about 4 seconds while the app stays active, then call it one more time. Wait until the status is no longer .notDetermined before loading the next scene. There is no timeout. The first scene runs on every cold launch, so if the status is still .notDetermined, the request is made again on the next launch. [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) { dispatch_async(dispatch_get_main_queue(), ^{ // store status; Unity polls it on the main thread }); }];We have not been able to reproduce the original problem on our own devices. Questions for those who have shipped apps with ATT How many times do you retry requestTrackingAuthorization, and how long do you wait between attempts? Is there any limit you know of? If the status still stays .notDetermined after retrying, do you let the user continue and treat it as not authorized (no IDFA), or keep waiting? If you wait, how long before you let the user continue? If you continue without tracking, did App Review ever flag that? Any experience or pointers to documentation would be appreciated.
0
0
31
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
1
0
49
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
1
0
50
2d
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
0
0
78
2d
iOS and Android
I currently have a iOS app live on the App Store but I also want to release it on Android, the whole code is in Swift so would that be possible or would I have to rewrite my whole apps code in a different coding language.
5
0
4.2k
3d
Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
1
0
106
3d
Client identity selection and chain presentation when an intermediate CA in the identity’s chain is revoked
We deploy client-authentication identities (certificate + private key) to iOS/iPadOS devices for mutual TLS and Wi-Fi EAP-TLS. The identities are installed via MDM configuration profiles and used from Safari, from our app via URLSession client certificate challenges, and by the system for EAP-TLS. The intermediate CA certificate in these identities’ chain (issued by a publicly trusted root) will be revoked. A replacement intermediate certificate with the same subject and public key, but a different serial number, is valid, and the end-entity certificates will not be reissued. The private keys are not exportable. If the revoked intermediate is known to the device through Apple’s distributed revocation data, or only through the root CA’s CRL, does iOS/iPadOS evaluate this when offering the identity for selection in Safari, when handling a URLSession client certificate challenge, or when using it for EAP-TLS? Could the identity be hidden, flagged, or fail to be presented? If we install the replacement intermediate on the device (e.g. via a certificate payload in a configuration profile) and remove the original, will the system build and present the chain through the replacement certificate? For URLSession, if our app supplies the chain explicitly in URLCredential(identity:certificates:persistence:), is any revocation evaluation performed on that chain on the client side? The revocation is scheduled for 2026-11-20T09:00:00Z. Our users rely on this system for patient care in medical institutions, so any guidance before then would be greatly appreciated.
2
5
492
3d
A bug in iOS 27.3 beta 2 where the UIHingeInteraction value is received even though it is not an iPhone Duo device.
The device currently showing the symptom is iPhone SE3, iOS 27.3 Beta 2 version installed. (Same symptom exists in Beta 1 as well.) On screen A When switching to another ViewController (screen B) with pushViewController of UINavigationController Declare UIHingeInteraction on screen A and self.view.addInteraction(hInteraction) I added it like the code above. Hinge value comes in. In the sample code below update.hinge value is not nil The update.hinge!.angle value is also displayed as 0. let hInteraction:UIHingeInteraction = UIHingeInteraction { interaction, update in if update.hinge != nil { let hingeAngle:CGFloat = update.hinge!.angle..... }} In apps installed on other iPhone 17 devices (with iOS 27.2 installed), the value does not appear there. A quick fix is ​​needed. I have also submitted a report via Apple Feedback; please ensure this is addressed in the upcoming Beta 3 release. *** Plus *** The horizontalSizeClass and verticalSizeClass properties are returning "Regular" values, similar to how they behave on the iPhone Duo's internal display. Please fix the above issue as well.
0
0
117
3d
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
8
3
1k
4d
How to Prevent Users from Removing an MDM Enrollment Profile on iOS?
Hello everyone! I'm a software engineer currently working on the development of a Mobile Device Management (MDM) system. I'm trying to implement a restriction that prevents users from manually removing the MDM enrollment profile from their iOS devices. While researching Apple's Device Management documentation, I came across two configurations that seem related to this functionality: PayloadRemovalDisallowed: A Boolean key that appears to control whether users can remove a configuration profile. com.apple.profileRemovalPassword: A payload that allows a removal password to be configured using the RemovalPassword key. However, after attempting to implement these configurations in our .mobileconfig files, I haven't been able to achieve the expected behavior. In some cases, these changes also interfere with our device enrollment process, preventing devices from successfully enrolling in our MDM system. Questions What is the correct way to use PayloadRemovalDisallowed and com.apple.profileRemovalPassword within a .mobileconfig file? Should they be used together, or are they intended for different scenarios? Where exactly should these configurations be placed? Should PayloadRemovalDisallowed be defined at the root level of the configuration profile, while com.apple.profileRemovalPassword is included as a separate payload inside PayloadContent? Can these configurations be included directly in the MDM enrollment profile? Or should they be delivered through a separate configuration profile after successful enrollment? Do these configurations require the device to be supervised? Is it possible to prevent profile removal on manually enrolled devices, or is Automated Device Enrollment (ADE) required? Why might these configurations interfere with device enrollment? Are there any restrictions on combining an MDM payload (com.apple.mdm) with a profile removal password payload? Does setting PayloadRemovalDisallowed to true actually prevent removal of the MDM enrollment profile itself, or does it only apply to regular configuration profiles? Is there any supported way to make an existing MDM enrollment profile non-removable after enrollment? Could someone provide a working .mobileconfig example demonstrating the correct implementation of these configurations? Expected Behavior Once a device has been successfully enrolled in our MDM system, the user should not be able to remove the MDM enrollment profile manually through the device settings. Ideally, this restriction should not interfere with the initial enrollment process or subsequent communication between the device and our MDM server. Current Behavior When attempting to configure PayloadRemovalDisallowed and com.apple.profileRemovalPassword, the expected removal restriction does not work correctly, and the enrollment process may fail. I'm trying to understand whether this is caused by incorrect placement of the configuration keys, limitations imposed by the enrollment method, or specific Apple device management requirements. Any guidance, official documentation, or working implementation examples would be greatly appreciated. Thank you in advance for your help!
3
0
2k
4d
SwiftUICore.tbd is missing previous entries on ios 17 and below
Toolchain Xcode 26.2 (17C52), iOS 26.2 SDK Also reproduced in the iOS 27.2 SDK (Xcode 27.2): the same six symbols are missing redirects there too Swift 6.2.3 (swiftlang-6.2.3.3.21) macOS 26.6.2 Deployment target: iOS 15.0 Crash confirmed on: iOS 17.5 simulator (plus App Store crash reports from iOS ≤ 17 devices) Missing $ld$previous entries in SwiftUICore.tbd static AlignmentID.combineExplicit(childValue::into:) ZIndexTraitKey: type metadata accessor, nominal type descriptor, protocol witness table protocol witness table for _FixedSizeLayout protocol witness table for Never (as View) Third-party packages that referenced them (context only) PackageVersionModulepurchases-ios-spm (RevenueCat)5.88.0RevenueCatUIOSInAppBrowserLib-iOS2.3.2OSInAppBrowserLibion-ios-camera2.0.0IONCameraLibSymptoms Without a workaround: dyld Library not loaded: /System/Library/Frameworks/SwiftUICore.framework/SwiftUICore at launch on iOS ≤ 17. With -weak_framework SwiftUICore: the app starts, but EXC_BREAKPOINT in swift_getAssociatedTypeWitness when a SwiftUI view that uses these symbols is presented.
0
0
30
5d
iOS 27b3 SDK: iOS App on Mac crashes on UISearchBar focus
Our app crashes when compiled with the iOS 27 beta 3 SDK and run as an iOS app on Mac, on both macOS 26 and macOS 27, as soon as a UISearchBar receives focus. The crash is due to this exception: *** Assertion failure in BOOL _screenBasedFocusUnsupported(void)(), UIScreen.m:3.725 Accessing the focus system through UIScreen is no longer supported. ( 0 CoreFoundation 0x000000018bea31c0 __exceptionPreprocess + 176 1 libobjc.A.dylib 0x000000018b91e91c objc_exception_throw + 88 2 Foundation 0x000000018e092644 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] + 0 3 UIKitCore 0x00000001c5dae8ec _screenBasedFocusUnsupported + 272 4 UIKitCore 0x00000001c5dae960 -[UIScreen _preferredFocusedWindow] + 24 5 UIKitCore 0x00000001c4ea3a60 -[UIScreen _mainSceneReferenceBounds] + 200 6 UIKitCore 0x00000001c4ea3914 -[UIScreen _mainSceneBoundsForInterfaceOrientation:] + 40 7 UIKitCore 0x00000001c5708134 +[UINavigationBar defaultSizeForOrientation:] + 76 8 UIKitCore 0x00000001c6222c88 -[_UISearchPresentationController _layoutPresentationWithSize:transitionCoordinator:] + 704 9 UIKitCore 0x00000001c622296c -[_UISearchPresentationController containerViewWillLayoutSubviews] + 84 10 UIKitCore 0x00000001c549304c block_destroy_helper.13 + 25112 11 UIKitCore 0x00000001c549344c block_destroy_helper.13 + 26136 12 UIKitCore 0x00000001c4ea26a8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1648 13 QuartzCore 0x0000000196103dbc _ZN2CA5Layer15perform_update_EPS0_P7CALayerjNS_17LayerUpdateReasonEPNS_11TransactionE + 460 14 QuartzCore 0x000000019610390c _ZN2CA5Layer17update_if_needed_EPNS_11TransactionENS_17LayerUpdateReasonE + 692 15 QuartzCore 0x0000000196035d2c _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 608 16 QuartzCore 0x0000000195e69520 _ZN2CA11Transaction6commitEv + 652 17 AppKit 0x0000000190fe116c __37+[NSDisplayCycle currentDisplayCycle]_block_invoke.7 + 44 18 CoreFoundation 0x000000018be34ad0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 19 CoreFoundation 0x000000018be34a10 __CFRunLoopDoBlocks + 396 20 CoreFoundation 0x000000018be33e54 __CFRunLoopRun + 2356 21 CoreFoundation 0x000000018bf06234 _CFRunLoopRunSpecificWithOptions + 532 22 HIToolbox 0x0000000198c1f560 RunCurrentEventLoopInMode + 320 23 HIToolbox 0x0000000198c228bc ReceiveNextEventCommon + 488 24 HIToolbox 0x0000000198dac14c _BlockUntilNextEventMatchingListInMode + 48 25 AppKit 0x00000001909163d0 _DPSBlockUntilNextEventMatchingListInMode + 228 26 AppKit 0x000000019026a084 _DPSNextEvent + 576 27 AppKit 0x0000000190dff96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 28 AppKit 0x0000000190dff678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72 29 AppKit 0x000000019025d13c -[NSApplication run] + 368 30 AppKit 0x00000001902357b0 NSApplicationMain + 880 31 AppKit 0x000000019047c958 +[NSWindow _savedFrameFromString:] + 0 32 UIKitMacHelper 0x00000001aa2651bc UINSApplicationMain + 972 33 UIKitCore 0x00000001c4e1aed4 UIApplicationMain + 144 34 UIKitCore 0x00000001c548bda0 block_destroy_helper.31 + 8880 35 DigitalConcertHall.debug.dylib 0x0000000106e41bd8 $sSo21UIApplicationDelegateP5UIKitE4mainyyFZ + 128 36 DigitalConcertHall.debug.dylib 0x0000000106e41b4c $s18DigitalConcertHall11AppDelegateC5$mainyyFZ + 32 37 DigitalConcertHall.debug.dylib 0x0000000106e4afc0 __debug_main_executable_dylib_entry_point + 28 38 dyld 0x000000018b9ac4e4 start + 6992 ) I could not test with the iOS 27 beta 4 SDK due to this blocking issue: https://developer.apple.com/forums/thread/839012 However, when I tried to set up a simple sample project, I could not reproduce the issue. Does anybody know what might be causing this? I filed feedback FB24201508
8
2
2.1k
5d
In Review already 7 days
Hi i've uploaded my first app! Awesome, but already 7 days in review :( i had ~4 rejections for my beta regarding 3rd-party content. I passed the beta after explaining it was these were not a valid rejection. they agreed. i already asked for status update on the official app review, but got no response. is more than 7days normal? and are there more things i can do? Cheers, Max Zijlstra
1
0
43
5d
Error 90068: iOS 11 build accepted in early September, now MinimumOSVersion 11.0 is rejected
Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that: the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date; iOS 11 builds were still being accepted in early September, including the build that was released on September 10; the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027; the upload now fails completely before the build reaches App Store Connect or TestFlight. Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing: the successful August 28 upload with the iOS 13 / iOS 15 warnings; the current Error 90068 rejection; the support case history. Could Apple please clarify: On what exact date did the MinimumOSVersion 13 requirement begin being enforced? Was this enforcement date announced anywhere before it became a hard upload requirement? Is there any supported way to upload one final bug-fix build for existing legacy iOS users? Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team? Thank you.
5
0
1.1k
6d
Is it possible to run an iPadOS virtual machine inside an iOS app?
Hi everyone, I am researching the technical feasibility of a project named Kairavox. The goal is to run a genuine, unmodified iPadOS installation as a guest VM inside a standalone app on an ordinary, unjailbroken iPhone. Our first research target is iPadOS 27.2.1 on an iPad 9th-generation (A13) guest. This is not an iPadOS-style interface or a remote desktop. We want to boot and run actual iPadOS in the guest. Proposed approach Apple’s public virtualization and hypervisor documentation appears to cover Mac hosts, not iPhone hosts. We are therefore investigating a native software AArch64 interpreter inside a normal iOS app. JIT is not assumed; we would consider it only if Apple confirms an applicable, supported development path. We are considering personal development signing and sideloading tools such as AltStore or SideStore. App Store distribution is not a project requirement. We understand that these tools do not themselves grant Apple entitlements, and that free Personal Team provisioning has limits. We are also investigating Apple’s documented Increased Memory Limit and Extended Virtual Addressing entitlements. We do not know whether either is available for this app and signing route, or what memory budget would actually be available to guest RAM. Projects such as Henge and GetMoreRam are useful points of comparison, but we understand that they do not establish an Apple-supported route for an iPadOS guest. We will not rely on private APIs, unauthorized entitlements, Secure Boot bypasses, or firmware patches. Questions Is there a documented iOS API or entitlement that lets a third-party iPhone app host a virtual CPU or VM? If not, is a native software interpreter a supported way for an app to interpret AArch64 guest instructions? Does Apple permit that interpreter to run an unmodified iPadOS guest in a sideloaded development app? Are there specific code-execution or licensing restrictions we should review? Apple documents virtual hardware identities and restore workflows for macOS VMs. Is there an analogous supported guest identity and image-personalization process for iPadOS, including an iPadOS 27.2.1 guest? Does Apple document a virtual SEP model, or another supported way to meet SEP-dependent boot, storage, and platform-service requirements for an iPadOS guest? Development Signing & JIT: For development on our own stock iPhone, can free Personal Team signing support this kind of application? Are there documented JIT permissions available through this signing route? If not, does JIT require a different signing arrangement or entitlement? Can an independent developer request the Increased Memory Limit entitlement for an iOS app through a documented process? How should we distinguish that process from Extended Virtual Addressing and the development-only Increased Debugging Memory Limit entitlement? If these questions are better directed to Developer Technical Support or another Apple team, please point us to the appropriate channel. We are looking for a documented, authorized path and will not assume one exists. Thanks for any guidance.
1
0
246
6d
iOS 27 Simulator: “Describe a Shortcut” stuck on “Preparing support”
I'm trying to test the new “Describe a Shortcut” feature in iOS 27 using an iPhone 17 Simulator. When I open Shortcuts and tap “Describe a Shortcut”, it stays on: “Preparing support for describe a shortcut” and the text field remains disabled. I cannot enter anything or create the shortcut. My setup: Mac: MacBook Pro macOS: 27 Xcode: 26.5 (17F42) Simulator: iPhone 17 iOS: 27 I also have a physical iPhone 14 Pro, but I understand that it doesn't support Apple Intelligence, so I'm trying to test this using the iPhone 17 Simulator. Do I need to enable/download anything for Apple Intelligence on the Mac or Simulator? Or is “Describe a Shortcut” currently unsupported/not working in the iOS 27 Simulator? Any guidance on the correct setup would be appreciated.
2
1
843
6d
CPU spike when using RealityView in iOS
CPU spikes to over 100% and stays in that range when realityView (even without content) is added to an iOS view in SwiftUI. On device, it takes approximately 20 seconds before you see this behavior. How are developers getting around this in iOS apps? Is it getting past app review? Xcode 27.2, iOS27.2.1
0
0
81
1w
Persistent scroll stutter on iPhone 17 Pro Max, 18 Pro Max and 18 Pro (iOS 27.2), also on Apple Store demo units
Affected devices (all show the same problem): 1x iPhone 17 Pro Max 2x iPhone 18 Pro Max 1x iPhone 18 Pro Many demo iPhones at several Apple Stores Current iOS version: 27.2 Issue: Vertical scrolling inside apps frequently stutters and drops frames. It happens in many, many apps, including Apple's own App Store and Apple Store apps. During a normal flick-and-decelerate scroll, the content repeatedly freezes for one or more frames and then jumps forward. Because this reproduces on four of my own devices and on many Apple Store demo units, I believe it is a widespread, system-level issue, not a defect of a single device or my settings. Impact: I have been living with this for more than six months. I use my iPhone heavily every day, and the constant stutter has made using it genuinely distressing. Everything else about iPhone feels excellent, which makes this problem even harder to accept. Steps to reproduce: Open the App Store app (or almost any app with a scrolling list). Scroll with a normal flick and let it decelerate. Observe repeated hitches during the scroll. Measurements: I filmed the screen with a second iPhone at 4K 120 fps and measured content movement frame by frame: iPhone 18 Pro Max, third-party video feed: about 4 hitches per second of scrolling, about 4% of frames dropped, mostly single-frame drops. iPhone 18 Pro Max, third-party social app list: about 11 hitches per second, about 12% of frames dropped, at a regular rhythm every 6-8 frames. About a third of the stalls last 2-3 frames, and the content does not catch up afterwards. iPhone 17 Pro Max, third-party comment list: about 5 hitches per second, about 8% of frames dropped, including several full freezes of 50-75 ms. Expected: Smooth 120 Hz scrolling, as ProMotion is designed to deliver. Is Apple aware of this issue? I am happy to provide videos, frame-by-frame data, or sysdiagnose logs.
Replies
4
Boosts
2
Views
386
Activity
23h
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
Replies
0
Boosts
0
Views
35
Activity
1d
ATT prompt not shown and status stays notDetermined: how do you handle it?
Hello, our Unity game (iOS/iPadOS) requests App Tracking Transparency on its first scene, before ads are initialized. Background App Review rejected an earlier build under Guideline 2.1(a) for a blank screen on iPad Air 11-inch (M3), iPadOS 27.0. In that build we called requestTrackingAuthorization right at launch and then waited until trackingAuthorizationStatus was no longer .notDetermined. The status never changed, so the app never left the first screen. Current flow (this build was approved) Wait until UIApplication.shared.applicationState == .active and the app has focus. Call requestTrackingAuthorization(completionHandler:) once and wait for the completion handler. If the completion returns .notDetermined, wait about 4 seconds while the app stays active, then call it one more time. Wait until the status is no longer .notDetermined before loading the next scene. There is no timeout. The first scene runs on every cold launch, so if the status is still .notDetermined, the request is made again on the next launch. [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) { dispatch_async(dispatch_get_main_queue(), ^{ // store status; Unity polls it on the main thread }); }];We have not been able to reproduce the original problem on our own devices. Questions for those who have shipped apps with ATT How many times do you retry requestTrackingAuthorization, and how long do you wait between attempts? Is there any limit you know of? If the status still stays .notDetermined after retrying, do you let the user continue and treat it as not authorized (no IDFA), or keep waiting? If you wait, how long before you let the user continue? If you continue without tracking, did App Review ever flag that? Any experience or pointers to documentation would be appreciated.
Replies
0
Boosts
0
Views
31
Activity
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
Replies
1
Boosts
0
Views
49
Activity
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
Replies
1
Boosts
0
Views
50
Activity
2d
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
Replies
0
Boosts
0
Views
78
Activity
2d
iOS and Android
I currently have a iOS app live on the App Store but I also want to release it on Android, the whole code is in Swift so would that be possible or would I have to rewrite my whole apps code in a different coding language.
Replies
5
Boosts
0
Views
4.2k
Activity
3d
Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
Replies
1
Boosts
0
Views
106
Activity
3d
Client identity selection and chain presentation when an intermediate CA in the identity’s chain is revoked
We deploy client-authentication identities (certificate + private key) to iOS/iPadOS devices for mutual TLS and Wi-Fi EAP-TLS. The identities are installed via MDM configuration profiles and used from Safari, from our app via URLSession client certificate challenges, and by the system for EAP-TLS. The intermediate CA certificate in these identities’ chain (issued by a publicly trusted root) will be revoked. A replacement intermediate certificate with the same subject and public key, but a different serial number, is valid, and the end-entity certificates will not be reissued. The private keys are not exportable. If the revoked intermediate is known to the device through Apple’s distributed revocation data, or only through the root CA’s CRL, does iOS/iPadOS evaluate this when offering the identity for selection in Safari, when handling a URLSession client certificate challenge, or when using it for EAP-TLS? Could the identity be hidden, flagged, or fail to be presented? If we install the replacement intermediate on the device (e.g. via a certificate payload in a configuration profile) and remove the original, will the system build and present the chain through the replacement certificate? For URLSession, if our app supplies the chain explicitly in URLCredential(identity:certificates:persistence:), is any revocation evaluation performed on that chain on the client side? The revocation is scheduled for 2026-11-20T09:00:00Z. Our users rely on this system for patient care in medical institutions, so any guidance before then would be greatly appreciated.
Replies
2
Boosts
5
Views
492
Activity
3d
A bug in iOS 27.3 beta 2 where the UIHingeInteraction value is received even though it is not an iPhone Duo device.
The device currently showing the symptom is iPhone SE3, iOS 27.3 Beta 2 version installed. (Same symptom exists in Beta 1 as well.) On screen A When switching to another ViewController (screen B) with pushViewController of UINavigationController Declare UIHingeInteraction on screen A and self.view.addInteraction(hInteraction) I added it like the code above. Hinge value comes in. In the sample code below update.hinge value is not nil The update.hinge!.angle value is also displayed as 0. let hInteraction:UIHingeInteraction = UIHingeInteraction { interaction, update in if update.hinge != nil { let hingeAngle:CGFloat = update.hinge!.angle..... }} In apps installed on other iPhone 17 devices (with iOS 27.2 installed), the value does not appear there. A quick fix is ​​needed. I have also submitted a report via Apple Feedback; please ensure this is addressed in the upcoming Beta 3 release. *** Plus *** The horizontalSizeClass and verticalSizeClass properties are returning "Regular" values, similar to how they behave on the iPhone Duo's internal display. Please fix the above issue as well.
Replies
0
Boosts
0
Views
117
Activity
3d
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
Replies
8
Boosts
3
Views
1k
Activity
4d
How to Prevent Users from Removing an MDM Enrollment Profile on iOS?
Hello everyone! I'm a software engineer currently working on the development of a Mobile Device Management (MDM) system. I'm trying to implement a restriction that prevents users from manually removing the MDM enrollment profile from their iOS devices. While researching Apple's Device Management documentation, I came across two configurations that seem related to this functionality: PayloadRemovalDisallowed: A Boolean key that appears to control whether users can remove a configuration profile. com.apple.profileRemovalPassword: A payload that allows a removal password to be configured using the RemovalPassword key. However, after attempting to implement these configurations in our .mobileconfig files, I haven't been able to achieve the expected behavior. In some cases, these changes also interfere with our device enrollment process, preventing devices from successfully enrolling in our MDM system. Questions What is the correct way to use PayloadRemovalDisallowed and com.apple.profileRemovalPassword within a .mobileconfig file? Should they be used together, or are they intended for different scenarios? Where exactly should these configurations be placed? Should PayloadRemovalDisallowed be defined at the root level of the configuration profile, while com.apple.profileRemovalPassword is included as a separate payload inside PayloadContent? Can these configurations be included directly in the MDM enrollment profile? Or should they be delivered through a separate configuration profile after successful enrollment? Do these configurations require the device to be supervised? Is it possible to prevent profile removal on manually enrolled devices, or is Automated Device Enrollment (ADE) required? Why might these configurations interfere with device enrollment? Are there any restrictions on combining an MDM payload (com.apple.mdm) with a profile removal password payload? Does setting PayloadRemovalDisallowed to true actually prevent removal of the MDM enrollment profile itself, or does it only apply to regular configuration profiles? Is there any supported way to make an existing MDM enrollment profile non-removable after enrollment? Could someone provide a working .mobileconfig example demonstrating the correct implementation of these configurations? Expected Behavior Once a device has been successfully enrolled in our MDM system, the user should not be able to remove the MDM enrollment profile manually through the device settings. Ideally, this restriction should not interfere with the initial enrollment process or subsequent communication between the device and our MDM server. Current Behavior When attempting to configure PayloadRemovalDisallowed and com.apple.profileRemovalPassword, the expected removal restriction does not work correctly, and the enrollment process may fail. I'm trying to understand whether this is caused by incorrect placement of the configuration keys, limitations imposed by the enrollment method, or specific Apple device management requirements. Any guidance, official documentation, or working implementation examples would be greatly appreciated. Thank you in advance for your help!
Replies
3
Boosts
0
Views
2k
Activity
4d
SwiftUICore.tbd is missing previous entries on ios 17 and below
Toolchain Xcode 26.2 (17C52), iOS 26.2 SDK Also reproduced in the iOS 27.2 SDK (Xcode 27.2): the same six symbols are missing redirects there too Swift 6.2.3 (swiftlang-6.2.3.3.21) macOS 26.6.2 Deployment target: iOS 15.0 Crash confirmed on: iOS 17.5 simulator (plus App Store crash reports from iOS ≤ 17 devices) Missing $ld$previous entries in SwiftUICore.tbd static AlignmentID.combineExplicit(childValue::into:) ZIndexTraitKey: type metadata accessor, nominal type descriptor, protocol witness table protocol witness table for _FixedSizeLayout protocol witness table for Never (as View) Third-party packages that referenced them (context only) PackageVersionModulepurchases-ios-spm (RevenueCat)5.88.0RevenueCatUIOSInAppBrowserLib-iOS2.3.2OSInAppBrowserLibion-ios-camera2.0.0IONCameraLibSymptoms Without a workaround: dyld Library not loaded: /System/Library/Frameworks/SwiftUICore.framework/SwiftUICore at launch on iOS ≤ 17. With -weak_framework SwiftUICore: the app starts, but EXC_BREAKPOINT in swift_getAssociatedTypeWitness when a SwiftUI view that uses these symbols is presented.
Replies
0
Boosts
0
Views
30
Activity
5d
iOS 27b3 SDK: iOS App on Mac crashes on UISearchBar focus
Our app crashes when compiled with the iOS 27 beta 3 SDK and run as an iOS app on Mac, on both macOS 26 and macOS 27, as soon as a UISearchBar receives focus. The crash is due to this exception: *** Assertion failure in BOOL _screenBasedFocusUnsupported(void)(), UIScreen.m:3.725 Accessing the focus system through UIScreen is no longer supported. ( 0 CoreFoundation 0x000000018bea31c0 __exceptionPreprocess + 176 1 libobjc.A.dylib 0x000000018b91e91c objc_exception_throw + 88 2 Foundation 0x000000018e092644 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] + 0 3 UIKitCore 0x00000001c5dae8ec _screenBasedFocusUnsupported + 272 4 UIKitCore 0x00000001c5dae960 -[UIScreen _preferredFocusedWindow] + 24 5 UIKitCore 0x00000001c4ea3a60 -[UIScreen _mainSceneReferenceBounds] + 200 6 UIKitCore 0x00000001c4ea3914 -[UIScreen _mainSceneBoundsForInterfaceOrientation:] + 40 7 UIKitCore 0x00000001c5708134 +[UINavigationBar defaultSizeForOrientation:] + 76 8 UIKitCore 0x00000001c6222c88 -[_UISearchPresentationController _layoutPresentationWithSize:transitionCoordinator:] + 704 9 UIKitCore 0x00000001c622296c -[_UISearchPresentationController containerViewWillLayoutSubviews] + 84 10 UIKitCore 0x00000001c549304c block_destroy_helper.13 + 25112 11 UIKitCore 0x00000001c549344c block_destroy_helper.13 + 26136 12 UIKitCore 0x00000001c4ea26a8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1648 13 QuartzCore 0x0000000196103dbc _ZN2CA5Layer15perform_update_EPS0_P7CALayerjNS_17LayerUpdateReasonEPNS_11TransactionE + 460 14 QuartzCore 0x000000019610390c _ZN2CA5Layer17update_if_needed_EPNS_11TransactionENS_17LayerUpdateReasonE + 692 15 QuartzCore 0x0000000196035d2c _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 608 16 QuartzCore 0x0000000195e69520 _ZN2CA11Transaction6commitEv + 652 17 AppKit 0x0000000190fe116c __37+[NSDisplayCycle currentDisplayCycle]_block_invoke.7 + 44 18 CoreFoundation 0x000000018be34ad0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 19 CoreFoundation 0x000000018be34a10 __CFRunLoopDoBlocks + 396 20 CoreFoundation 0x000000018be33e54 __CFRunLoopRun + 2356 21 CoreFoundation 0x000000018bf06234 _CFRunLoopRunSpecificWithOptions + 532 22 HIToolbox 0x0000000198c1f560 RunCurrentEventLoopInMode + 320 23 HIToolbox 0x0000000198c228bc ReceiveNextEventCommon + 488 24 HIToolbox 0x0000000198dac14c _BlockUntilNextEventMatchingListInMode + 48 25 AppKit 0x00000001909163d0 _DPSBlockUntilNextEventMatchingListInMode + 228 26 AppKit 0x000000019026a084 _DPSNextEvent + 576 27 AppKit 0x0000000190dff96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 28 AppKit 0x0000000190dff678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72 29 AppKit 0x000000019025d13c -[NSApplication run] + 368 30 AppKit 0x00000001902357b0 NSApplicationMain + 880 31 AppKit 0x000000019047c958 +[NSWindow _savedFrameFromString:] + 0 32 UIKitMacHelper 0x00000001aa2651bc UINSApplicationMain + 972 33 UIKitCore 0x00000001c4e1aed4 UIApplicationMain + 144 34 UIKitCore 0x00000001c548bda0 block_destroy_helper.31 + 8880 35 DigitalConcertHall.debug.dylib 0x0000000106e41bd8 $sSo21UIApplicationDelegateP5UIKitE4mainyyFZ + 128 36 DigitalConcertHall.debug.dylib 0x0000000106e41b4c $s18DigitalConcertHall11AppDelegateC5$mainyyFZ + 32 37 DigitalConcertHall.debug.dylib 0x0000000106e4afc0 __debug_main_executable_dylib_entry_point + 28 38 dyld 0x000000018b9ac4e4 start + 6992 ) I could not test with the iOS 27 beta 4 SDK due to this blocking issue: https://developer.apple.com/forums/thread/839012 However, when I tried to set up a simple sample project, I could not reproduce the issue. Does anybody know what might be causing this? I filed feedback FB24201508
Replies
8
Boosts
2
Views
2.1k
Activity
5d
In Review already 7 days
Hi i've uploaded my first app! Awesome, but already 7 days in review :( i had ~4 rejections for my beta regarding 3rd-party content. I passed the beta after explaining it was these were not a valid rejection. they agreed. i already asked for status update on the official app review, but got no response. is more than 7days normal? and are there more things i can do? Cheers, Max Zijlstra
Replies
1
Boosts
0
Views
43
Activity
5d
Error 90068: iOS 11 build accepted in early September, now MinimumOSVersion 11.0 is rejected
Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that: the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date; iOS 11 builds were still being accepted in early September, including the build that was released on September 10; the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027; the upload now fails completely before the build reaches App Store Connect or TestFlight. Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing: the successful August 28 upload with the iOS 13 / iOS 15 warnings; the current Error 90068 rejection; the support case history. Could Apple please clarify: On what exact date did the MinimumOSVersion 13 requirement begin being enforced? Was this enforcement date announced anywhere before it became a hard upload requirement? Is there any supported way to upload one final bug-fix build for existing legacy iOS users? Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team? Thank you.
Replies
5
Boosts
0
Views
1.1k
Activity
6d
Is it possible to run an iPadOS virtual machine inside an iOS app?
Hi everyone, I am researching the technical feasibility of a project named Kairavox. The goal is to run a genuine, unmodified iPadOS installation as a guest VM inside a standalone app on an ordinary, unjailbroken iPhone. Our first research target is iPadOS 27.2.1 on an iPad 9th-generation (A13) guest. This is not an iPadOS-style interface or a remote desktop. We want to boot and run actual iPadOS in the guest. Proposed approach Apple’s public virtualization and hypervisor documentation appears to cover Mac hosts, not iPhone hosts. We are therefore investigating a native software AArch64 interpreter inside a normal iOS app. JIT is not assumed; we would consider it only if Apple confirms an applicable, supported development path. We are considering personal development signing and sideloading tools such as AltStore or SideStore. App Store distribution is not a project requirement. We understand that these tools do not themselves grant Apple entitlements, and that free Personal Team provisioning has limits. We are also investigating Apple’s documented Increased Memory Limit and Extended Virtual Addressing entitlements. We do not know whether either is available for this app and signing route, or what memory budget would actually be available to guest RAM. Projects such as Henge and GetMoreRam are useful points of comparison, but we understand that they do not establish an Apple-supported route for an iPadOS guest. We will not rely on private APIs, unauthorized entitlements, Secure Boot bypasses, or firmware patches. Questions Is there a documented iOS API or entitlement that lets a third-party iPhone app host a virtual CPU or VM? If not, is a native software interpreter a supported way for an app to interpret AArch64 guest instructions? Does Apple permit that interpreter to run an unmodified iPadOS guest in a sideloaded development app? Are there specific code-execution or licensing restrictions we should review? Apple documents virtual hardware identities and restore workflows for macOS VMs. Is there an analogous supported guest identity and image-personalization process for iPadOS, including an iPadOS 27.2.1 guest? Does Apple document a virtual SEP model, or another supported way to meet SEP-dependent boot, storage, and platform-service requirements for an iPadOS guest? Development Signing & JIT: For development on our own stock iPhone, can free Personal Team signing support this kind of application? Are there documented JIT permissions available through this signing route? If not, does JIT require a different signing arrangement or entitlement? Can an independent developer request the Increased Memory Limit entitlement for an iOS app through a documented process? How should we distinguish that process from Extended Virtual Addressing and the development-only Increased Debugging Memory Limit entitlement? If these questions are better directed to Developer Technical Support or another Apple team, please point us to the appropriate channel. We are looking for a documented, authorized path and will not assume one exists. Thanks for any guidance.
Replies
1
Boosts
0
Views
246
Activity
6d
iOS 27 Simulator: “Describe a Shortcut” stuck on “Preparing support”
I'm trying to test the new “Describe a Shortcut” feature in iOS 27 using an iPhone 17 Simulator. When I open Shortcuts and tap “Describe a Shortcut”, it stays on: “Preparing support for describe a shortcut” and the text field remains disabled. I cannot enter anything or create the shortcut. My setup: Mac: MacBook Pro macOS: 27 Xcode: 26.5 (17F42) Simulator: iPhone 17 iOS: 27 I also have a physical iPhone 14 Pro, but I understand that it doesn't support Apple Intelligence, so I'm trying to test this using the iPhone 17 Simulator. Do I need to enable/download anything for Apple Intelligence on the Mac or Simulator? Or is “Describe a Shortcut” currently unsupported/not working in the iOS 27 Simulator? Any guidance on the correct setup would be appreciated.
Replies
2
Boosts
1
Views
843
Activity
6d
CPU spike when using RealityView in iOS
CPU spikes to over 100% and stays in that range when realityView (even without content) is added to an iOS view in SwiftUI. On device, it takes approximately 20 seconds before you see this behavior. How are developers getting around this in iOS apps? Is it getting past app review? Xcode 27.2, iOS27.2.1
Replies
0
Boosts
0
Views
81
Activity
1w