We are developing UTipping, a digital tipping application, and are seeking technical guidance before implementation. Our intended experience is: The recipient opens the app and activates “Receive Tip”. The sender selects a tip amount and “Send Tip”. Both authenticated apps are unlocked, online, and in the foreground. The two iPhones are brought into very close physical proximity. The proximity interaction exchanges or resolves only a short-lived, opaque session identifier. No funds, card credentials, cryptograms, or payment-authorization data are exchanged through NFC. The sender confirms the resolved recipient and amount. Payment is processed separately through the backend and licensed payment infrastructure. Standard Core NFC appears to provide reader functionality for supported tags/protocols, but not a general application-controlled iPhone-to-iPhone peer/tag-emulation channel. We would appreciate guidance on: whether this interaction can be implemented using Core NFC; whether NFC & SE Platform or HCE / CardSession could provide the presenter role; whether one third-party iPhone can present a temporary application-controlled identifier to another third-party iPhone; whether both apps must remain foreground; and whether Nearby Interaction with BLE / Multipeer Connectivity is the recommended alternative for very-close-proximity recipient identification. The NFC/proximity interaction would only identify the intended recipient. The financial transaction is completely separate. Apple Developer Support previously referred us to engineering under case 102948761329. We have also submitted the detailed technical architecture through Feedback Assistant: FB24517831 Any guidance from Apple framework engineers regarding the supported architecture and entitlement path would be greatly appreciated.

I submitted my app in August 13, 2026. But till today the app is still showing submitted for review. todays marks day 13 waiting for review. Is there anything else I should do other then expedite of which I did today (26 August 2026).

Anyone with the similar experience? Would appreciate the advice: Timeline: Initial submission: ~4 weeks ago First review: Completed after ~2 weeks after we have sent the expedited review request Fixes applied: Completed within 24 hours Resubmission: August 12, 2026 Current status: Still in review - no activity for ~2 weeks We have a planned launch date that's now at risk due to this review delay. The lack of any reviewer interaction on the resubmission is particularly concerning. Any insights or advice would be greatly appreciated

Hi everyone! I'm back again! 😄 A few months ago I posted here after submitting my first iOS app, after previously publishing it on Google Play. That experience was really helpful, so I'm hoping to get some advice from the community again. I've just submitted my new app, Vaqui, and it's currently Waiting for Review. Vaqui is an expense-sharing app for groups, mainly designed for trips. For example, three friends travel together and pay for different things: Pepe pays for the hotel. Sandra pays for groceries. Marcos pays for dinner. Everyone participates in different expenses. Vaqui calculates the resulting balances and suggests who should transfer money to whom. The app supports multiple currencies and stores the exchange rate used when an expense is recorded. The important part is that Vaqui does not process or hold money. It doesn't provide a wallet, banking account, payment processing, cards, or financial transactions. If someone owes another person money, Vaqui simply tells them something like: "Marcos owes Sandra $15,000." They make the actual transfer themselves using their bank or payment provider, outside Vaqui. The users can then mark the payment as made/received inside the app so the group knows what has already been settled. This made me wonder about something before the review starts: Would an app like Vaqui normally be considered a financial-services app by App Review, simply because it calculates debts/balances between users? Or is it generally treated as an expense-management / expense-sharing utility as long as it doesn't actually process, hold, or transfer money? I'm asking because I want to make sure I've understood the relevant App Review guidelines correctly rather than discovering during review that I've misunderstood something obvious. 😅 The current App Store Connect information is: App: Vaqui Bundle ID: mobi.todoapp.vaqui Apple ID: 6802352647 Status: Waiting for Review Platform: iOS / Flutter If anyone has submitted an app with similar functionality, I'd really appreciate hearing about your experience. Thanks! Greetings from Córdoba, Argentina 🇦🇷 And yes... once again I'm waiting for that little "In Review" notification. 🤞😂

For iOS 27 Betas 1-5, when there was an incoming phone call, the call screen would display "Identified by XXX Mobile", where XXX is the name of the carrier of the sim. But with beta 6 and now 7, this is no longer the case. Is this an accidental regression bug or intentional removal of the attribution? If so, then why was it present in the earlier betas?

Our first submission for a new app has been sitting in "Waiting for Review" for 10 days and has never moved to "In Review". App: Space Heroes: Galactic War (Apple ID 6484163845) Version 1.0, build 57 — submitted 13 August 2026 The submission contains 1 app version and 4 in-app purchases. All five items are in "Ready for Review". Everything on our side is complete: review screenshots for each IAP, price schedules, localizations, privacy policy URLs for both locales, age rating declaration, and App Review contact details with notes explaining that no demo account is needed (the game opens straight into the main menu). We have had no rejection, no information request, and no message in Resolution Center. What makes this difficult to read as ordinary queue time is that other apps on the same developer account, submitted in the same period, were all reviewed quickly: Stepster submitted 6 Aug -> released 6 Aug (8 hours) Bulls & Cows submitted 6 Aug -> released 8 Aug (1.5 days) Codex Numbers submitted 9 Aug -> released 11 Aug (2 days) Okey Masasi submitted 15 Aug -> released 18 Aug (2.7 days) Okey Masasi was submitted two days AFTER Space Heroes and has been live for almost a week. We understand that a first submission is reviewed more thoroughly than an update and takes longer. Our question is whether 10 days without ever entering review is expected here, or whether something is holding this particular submission in the queue. Could someone check whether anything on our side is blocking it, or whether it needs to be re-queued? We would rather wait than cancel and resubmit, since cancelling would also reset our in-app purchase versions. Thank you.

Hi, We recently updated our app icon, but the push notification icon has not been updated on some devices. It still shows the old icon on: • iPhone 16 Pro — iOS 26 • iPhone 14 — iOS 26 • iPad Pro 11” (M4) — iOS 18.6.2 • iPhone 16 Plus — iOS 18.5 After restarting these devices, the push notification icon is refreshed and displays the new version correctly. Could you advise how we can ensure the push notification icon updates properly on all affected devices without requiring users to restart? Thank you.

Settings , Apps , Phone , Announce -- does not work on hearing aids linked to iPhone via Bluetooth

Hello, We are developing an enterprise iOS application for cellular network benchmarking, performance validation, and network analytics. After reviewing the publicly available iOS frameworks and APIs, including CoreTelephony, we have not identified a supported public API that provides access to the following cellular RF and network measurements: • ARFCN • Band • Bandwidth (BW) • Cell ID • PCI (Physical Cell Identity) • CQI (Channel Quality Indicator) • RSRP (Reference Signal Received Power) • RSRQ (Reference Signal Received Quality) • SINR / SNR • RSSI • TAC (Tracking Area Code) • TA (Timing Advance) As an example, we are interested in obtaining information similar to the following: { "arfcn": "", "band": "", "bw": "", "cellId": "", "cqi": "", "pci": "", "rsrp": "", "rsrq": "", "sinr": "", "rssi": "", "ta": "", "tac": "" } Could Apple please clarify whether any of these measurements are available through an officially supported mechanism, including but not limited to: • Public iOS frameworks or APIs • Special entitlements • Carrier partner programs or integrations • Apple-approved diagnostics or measurement frameworks • Any other Apple-supported programs or access mechanisms We are not seeking to use private APIs, reverse-engineering techniques, or unsupported approaches. Our objective is solely to determine whether Apple provides a legitimate and supported method for an application to access any of these cellular network metrics on iOS devices. If access to any subset of these measurements is supported, we would greatly appreciate guidance regarding the relevant documentation, framework, entitlement, carrier program, or enrollment process. Our use case is limited to: • Cellular network benchmarking • Performance validation and testing • Network quality analytics Thank you for your guidance and assistance.

iOS 18 (22A3354) will not offer a option in settings (> Apps > Phone) after calling openSettings to enable live caller id lookup extension. iPhone and MacBook are in the same network. The PIRService runs on MacBook and is reachable via iPhone Safari (via http://MacBookPro:8080/). Hummingbird print log: hb_method=GET hb_uri=/ [Hummingbird] Request. After deploying the application via Xcode to the iPhone no requests are printed in the terminal. The extension was added like documented and bundle id is also checked multiple times. issuerRequestUri in service-config.json is http://MacBookPro:8080/issue. As far as I can tell, everything has been set up in accordance with the Testing Live Caller ID instructions. Is there something missing?

I'm developing an iOS custom keyboard extension and need to intercept external Bluetooth hardware keystrokes in the background. Can I capture these events within a UIInputViewController (e.g., using UIKeyCommand), or does iOS strictly route them directly to the host app? Are there any specific APIs or workarounds for this, or is it completely blocked by Apple's sandboxing policies?

Environment: MacBook Air M4 macOS 27 Golden Gate Beta Xcode 27 Beta iPhone running iOS 27 Beta Apple Watch Series 10 paired to the iPhone Steps to Reproduce: Install macOS 27 Beta and Xcode 27 Beta. Pair an Apple Watch with an iPhone running iOS 27 Beta. Enable Developer Mode on the iPhone. Connect the iPhone to the Mac and launch Xcode. Open Window → Devices and Simulators. Attempt to locate the paired Apple Watch or enable Developer Mode on the watch. Expected Result: The paired Apple Watch appears in Xcode for development purposes. A Developer Mode option is available on the Apple Watch. Xcode is able to recognize and communicate with the watch through the paired iPhone. Actual Result: The Apple Watch does not appear in Xcode. No Developer Mode option is visible on the watch. The iPhone is successfully paired and running iOS 27 Beta, but the watch remains unavailable for development workflows. Additional Notes: The iPhone and Apple Watch are already paired and functioning normally. Developer Mode is enabled on the iPhone. Restarting devices and reconnecting the iPhone did not resolve the issue. Unsure whether this is a limitation of the current beta builds or a regression in Xcode/watchOS development tooling.

I’m seeing inconsistent UISegmentedControl background-color behavior on certain devices running iOS 26. The same code works as expected on other devices and iOS versions, but on affected devices the control does not display the assigned backgroundColor. The issue occurs using standard UIKit colors and does not depend on custom fonts, images, or appearance extensions. Here is a simplified example using only public UIKit APIs: private let segmentedControl = UISegmentedControl(items: ["Card", "Email"]) private func setupSegmentedControl() { segmentedControl.selectedSegmentIndex = 0 guard let cardIcon = UIImage( systemName: "creditcard.fill", withConfiguration: UIImage.SymbolConfiguration( pointSize: 14, weight: .semibold ) ), let emailIcon = UIImage( systemName: "envelope.fill", withConfiguration: UIImage.SymbolConfiguration( pointSize: 14, weight: .semibold ) ) else { return } segmentedControl.setImage( cardIcon, forSegmentAt: 0 ) segmentedControl.setImage( emailIcon, forSegmentAt: 1 ) segmentedControl.backgroundColor = .systemGray5 segmentedControl.selectedSegmentTintColor = .systemBlue segmentedControl.layer.cornerRadius = 8 segmentedControl.clipsToBounds = true let font = UIFont.systemFont( ofSize: 14, weight: .medium ) segmentedControl.setTitleTextAttributes( [ .foregroundColor: UIColor.label, .font: font ], for: .normal ) segmentedControl.setTitleTextAttributes( [ .foregroundColor: UIColor.white, .font: font ], for: .selected ) segmentedControl.addTarget( self, action: #selector(segmentChanged(_:)), for: .valueChanged ) view.addSubview(segmentedControl) } @objc private func segmentChanged( _ sender: UISegmentedControl ) { print("Selected segment: \(sender.selectedSegmentIndex)") } UISegmentedControl Apple Documentation

Apple's 8 June 2026 announcement states that developers in the EU will not be able to test or use the new Siri AI features in their apps for iOS 27, iPadOS 27 or watchOS 27. I am an EU-based developer building apps for users in multiple markets. App Intents Testing, simulator checks and unit tests can validate parts of an implementation, but they do not appear to replace end-to-end validation of Siri AI behaviour on supported iPhone and iPad hardware. What is Apple's supported route for an EU-based developer to validate the following for users in supported markets? • intent discovery and invocation • parameter resolution and follow-up interaction • error handling and confirmation flows • Siri's presentation and completion of an action • behaviour on supported physical devices Is an official remote-device environment, controlled developer testing mode or another Apple-supported arrangement available or planned? I am not asking for a way to bypass regional restrictions. I am looking for documented, compliant testing guidance for developers serving a global App Store. I have filed Feedback Assistant report FB24276767 about this testing-access issue. Apple source: https://www.apple.com/newsroom/2026/06/due-to-dma-siri-ai-delayed-in-eu-for-ios-27-and-ipados-27/

Hi Team, I'm trying to understand the behavior of the following API: HTTPCookieStorage.shared.setCookies(_:for:mainDocumentURL:) Specifically, does this API persist cookies synchronously, or does it perform the storage asynchronously in the background? Our use case is storing FCAP (frequency capping) cookies so they persist across app sessions. We call setCookies(_:for:mainDocumentURL:) and want to know whether the cookies are guaranteed to be written before the method returns, or if the actual persistence happens asynchronously. I couldn't find documentation describing the persistence semantics of this API, so I'd appreciate any clarification or guidance from Apple or anyone familiar with its implementation. Thanks

I am building an iOS text composer with an attachment panel. When its UITextField is first responder and the system keyboard is visible, tapping the attachment button should present a panel that can extend into the region occupied by the keyboard. When the panel closes, the user should return to the same keyboard state without a visible dismissal and re-presentation. The required continuity is: The same UITextField remains first responder. The active input mode remains alphabet, 123, or Emoji. Emoji preserves its selected category, search state, and scroll position. The composer remains positioned above the keyboard throughout the transition. I have investigated the public UIKit approaches: A normal app-window overlay cannot render above the remotely hosted system keyboard. inputAccessoryView remains in the accessory region and cannot cover the keycaps. Resigning first responder visibly dismisses the keyboard and loses continuity. Assigning a custom inputView to the same UITextField and calling reloadInputViews() publicly replaces the keyboard. However, restoring inputView to nil reconstructs the system keyboard and does not preserve the exact Emoji or keyplane state. UIKeyboardLayoutGuide provides geometry but no presentation control. Is there a supported public API or recommended architecture that allows an app to: Temporarily obscure or visually hide the system keyboard while keeping it active and preserving its state? Present app-owned content in a layer above the keyboard keycaps? Temporarily replace the keyboard and restore the same mode, Emoji category, and scroll position? If these are unsupported, what is Apple's recommended way to create an attachment panel that visually occupies the keyboard region while maintaining input continuity? This occurs on iOS 26.x in Simulator and on a physical iPhone using a UIKit-backed text field inside a SwiftUI interface. I am specifically looking for a public API solution and do not want to access private keyboard windows or views.

We are seeing a low-volume but persistent crash on iOS 26 that surfaces inside Foundation's base64 encoder, and we would like to see if and how we could prevent that crash 2026-08-14_10-47-14.9181_-0500-5b74aa117551b30ab7696e1d90c129b97ab1e42f.crash - (nonnull NSString *)pnd_UTF8Base64 { NSData *encodedData = [self dataUsingEncoding:NSUTF8StringEncoding]; if (encodedData == nil || encodedData.length == 0) { return @""; } NSData *safeData = [NSData dataWithBytes:encodedData.bytes length:encodedData.length]; return [safeData base64EncodedStringWithOptions:0]; } Questions: Is our reading correct that _xzm_xzone_malloc_freelist_outlined indicates the freelist was ALREADY corrupted before this allocation (double-free / use-after-free / buffer overflow somewhere else), and that this base64 malloc is merely the first allocation to detect it (a 'canary'), not the cause? Did the iOS 26 xzone allocator add/strengthen freelist integrity checks such that latent corruption that previously went unnoticed now traps here? What is the recommended way to pin down the real corruptor in a shipping app where this reproduces only occasionally on end-user devices (MallocStackLogging, Guard Malloc / libgmalloc, MallocScribble, Address Sanitizer, MallocNanoZone settings)? Are any of these usable/meaningful against the xzone allocator? Is there any process-level or per-allocation API to validate heap integrity that is safe on the xzone allocator (e.g. malloc_zone_check behavior on iOS 26)? Any guidance on interpreting this signature and isolating the root cause would be appreciated. Thanks.

Hello everyone. I’m trying to submit my first auto-renewable subscription with my iOS app, but can’t associate the subscription with my app version in App Store Connect. Setup: app version 1.0.7 with build attached, subscription group “Premium” with weekly, monthly, yearly. All metadata complete; paid apps agreement active, bank details set, admin access confirmed. Problem: “In-App Purchases and Subscriptions” section is missing on my app version page, so I can’t attach my subscription. Draft error says, “Unable to submit for review. Add an app version for the selected platform.” The draft only lists my weekly plan, not the app version. Questions: why might that section be missing? Are there prerequisites? Has anyone seen this? Any guidance or suggestions would be greatly appreciated.

I'm about to start losing all my phone's biome data and my mind with it. I need help from guru engineers. Hope someone could help me. Published Biome research covers reading the SEGB artifacts, but I can't find anything on sync/sync.db and the merge logic. Hoping someone here has looked at it. Setup: iPhone16 Pro on iOS 26.6 paired with a MacBook Air on macOS 26.6. Same Apple ID. Reading my own devices, read-only. What happened My Macbook stopped receiving phone's in_focus biome stream after a large tombstone purge. In ~/Library/Biome/sync/sync.db, table CRDTLocation has rows of (stream, site, day, state). For my iPhone's AppLaunch stream there is a contiguous band of 27 days, 30 June to 29 July, with state = 4. Every other day is state = 2. Other streams on the same device have bands of only 1-2 days. Data behaviour lines up exactly with that band: -every day at or below 29 July: the phone offers batches, zero records ever land -every day after 29 July: records land normally, but only 2-3 per hour, the gap is widening every day. I am now on the 1st of Aug. -14 out of 14 date buckets observed over a week follow this, no exceptions Media.NowPlaying on the same phone has its own state=4 day at 23 July, and it has delivered nothing since 22 July. Over a week it re-offered ~8,900 records spanning 21 June to 16 July, all refused, and it never offers anything dated after its 23 July mark, even though newer data exists on the phone. The 27-day band was created on 30 July: two tombstone segments written over 6 seconds at 08:14 UTC containing ~18,000 deletion records covering 2-24 July. On the Mac those days now show 0 live records and several thousand dead slots. TombstoneBookmark still points at that segment. Questions What do CRDTLocation.state values mean? I'm fairly confident 4 = deleted and 2 = present/known, since days marked 2 sync fine including ones with no data yet. Is that right, and are there other values? Is the refusal rule what it looks like: an incoming batch is dropped if its day is at or below the highest state=4 day for that (stream, site)? Is the comparison meant to be inclusive? Is a tombstone for a day supposed to bar re-delivery of the entire day permanently, or only the specific records that were deleted? Mine appears to bar everything, including records that were never deleted. Is there any supported way to clear a state=4 band, or reset the sync relationship for one stream, without erasing the device? Has anyone seen a tombstone burst like this, ~18,000 deletion records in under 6 seconds while both devices were idle? Normal pruning on my device is ~700/day. Is there a known trigger? Would it be possible to repoint tombstone bookmark manually? The source records still exist on the phone but Biome retention is ~28 days, so they age out within days... please help Thank you!

Hi I don’t know if I come to correct place but fingers crossed we can get somewhere I am currently receiving some software bugs on my new device model iPhone 17 pro recently brought also I have been on social media and I have noticed a few people have mentioned the same thing about the same situation as I thought it was a bit normal to have them type of issues so i thought I’d look into it and see if this problem could be resolved a manner