Dear team, I am reaching out to inquire about potential daily usage limits for the CoreLocation geocoding services. While I understand that there is a known limit of approximately 50 requests per minute, I have received information suggesting there may also be a daily cap of 25,000 requests. Could you please confirm whether such a daily limit exists? Additionally, I would appreciate any recommendations you might have for increasing the allowable number of daily geocoding requests, if possible. Thank you in advance for your support.

I would like to inquire about an error that has started occurring while debugging AppStore billing. (In sandbox environment) This error occurs after entering a password and completing the purchase process, and in this case, no completion alert appears. The error doesn't seem to depend on the purchase item, sandbox account, or device, and shows unstable behavior - sometimes succeeding and sometimes failing. Additionally, this error started occurring after special debugging where the network was disconnected during the purchase process. Moreover, the same error occurs in the TestFlight version of our already released normal (supposedly) version. I think this might be a sandbox-specific error where the system has temporarily become unstable, but what do you think? If so, how can I resolve this issue? I would appreciate your insights on the cause and appropriate response. Error details below: <SKPaymentQueue: 0x283b3d070>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x28364d770 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed" UserInfo={NSLocalizedDescription=Purchase Failed, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unauthorized_message"; failureType = ""; "m-allowed" = 0; pings = ( ); }, NSLocalizedFailureReason=Server canceled the purchase}}, storefront-country-code=JPN, client-environment-type=Sandbox}

I was update my phone 12 promax to ios 26 and the back camera can’t use anymore

After doing a software update I can only view iMessages older than 12hrs (from a single contact) if the other person replies to and older message. Every time I leave the Massages app and go back in the issue occurs again.

After the last OS26 developer beta update the watch series 6 battery drains fast, in less than two hours life. I visited Apple Store , they said the battery was dead so I had to buy new watch series 10 The same issue happened in the new watch, the battery meter shows 50% after 1 hour Right now I’ve downgraded my update version to beta 11 until I can find a solution

we’ve identified that our PDF rendering pipeline leverages the native CGPDFDocument APIs to convert PDF pages into images. However, in the latest release of iOS 18, the provided document fails to render even at the CGPDFDocument level. Our analysis suggests that the issue may stem from the embedded custom fonts not being correctly processed in this version of the iOS platform. This appears to be consistent with several other reports and discussions around font rendering problems introduced in iOS 18, particularly involving subset fonts. We’ve attached a collection of relevant community threads and references, including: Apple Developer Discussion: Subset Font Rendering Issue in iOS 18 Given that our implementation is tightly coupled with Apple’s native PDF rendering APIs, this issue presents a blocking limitation for us. With your permission, we would like to use this document as a sample case to formally report the issue through the appropriate Apple Developer forums and feedback channels.

iPadOS 26 Dev Beta 1 - need to do a restore via DFU mode. I made sure iPad in normal mode shows up in Finder and I can see device details. When I boot into DFU mode (I have kept the ipad connected to mac), it does not show up in Finder. No matter what combination of plugging/unplugging cables, rebooting, again into DFU mode, it will not show up in Finder. Looking for steps to resolve this, or do I need to wait until beta 2 to resolve this?

Every time I go into the iOS software update settings to make sure my iPhone is fully updated to iOS 26, I keep getting an error message that says unable to check for update, an error occurred while checking for a software update. Please fix this bug?

I recently updated iOS 26 beta and now my SingPass keeps crashing when I tried to open it. can I revert back to iOS 18?

Hi everyone, We're facing an issue with Universal Links on iOS 18 and above. The problem seems related to how iOS handles redirects before reaching a Universal Link. ✅ Working Link (direct): When we open this direct Universal Link, the app opens as expected: 👉 https://dl.punchh.com/deeplinks/logansroadhouse/ ❌ Not Working (redirected link): This marketing/tracking link eventually redirects to the above Universal Link, but on iOS 18+, it opens the App Store or a browser instead of the app: 👉 https://ip2.loyalty.logansroadhouse.com/ls/click?upn=... The same redirect link works fine on iOS 17 and below — it opens the app.

Hi everyone, I updated my iPhone 16 Pro to iOS 26 beta and my Apple Watch to watchOS 26 beta because I wanted to test out the new features. After a few days of testing, I found the iOS 26 beta too unstable and laggy for daily use, so I downgraded my iPhone back to iOS 18.5 stable. Now my Apple Watch is still running watchOS 26 beta. I tried resetting it to factory settings, hoping that would help, but now I can’t pair it back to my iPhone because it requires iOS 26 again — which I don’t want to reinstall and don't want to use it till it's stable. Is there any way to downgrade my Apple Watch back to a stable version or somehow pair it again with my iPhone running iOS 18.5? Thanks in advance for any help!

An error occurred while checking for a software update after the iOS 26 update. Is anyone else facing a similar issue?

Hello all, We are in the process of deploying EAP-TLS Wi-Fi authentication across our corporate environment for both Windows and macOS devices. All endpoints are managed via Workspace ONE. As part of our macOS configuration, we are pushing device certificates to the login keychain of managed MacBooks. For testing purposes, we have explicitly set the Access Control List (ACL) of the associated private key to allow all applications access. This includes: eapolclient, which handles the EAP-TLS handshake for Wi-Fi panGPS, which is responsible for establishing the GlobalProtect VPN connection (we are using certificate-based authentication with pre-logon enabled) Additionally, we have configured and deployed a Wi-Fi profile via Workspace ONE to prevent users from having to manually select their device certificate - basically the identity preference card in Keychain Access. Despite these settings, we are still encountering Keychain Access prompts when eapolclient attempts to access the private key. This happens even though the key is configured to allow all applications access. This behavior is unexpected, and we’re trying to understand why these prompts persist. Has anyone encountered similar behavior on macOS, or is there something we're missing in terms of permissions or keychain configuration that could be causing this? We would greatly appreciate any insight or guidance. Thank you, Kyo

Right now, Apple’s iCloud Keychain (where saved passwords are stored) relies on the same authentication methods as your iPhone in general: Face ID or device passcode. This means: • If Face ID fails, it falls back to the device passcode. • Anyone with your passcode can unlock not only your phone but also your saved passwords by allowing the phone to go into the “enter iPhone password to view passwords” on the password app. Why this matters if someone knows or coerces your device passcode, they could potentially: • Bypass Face ID • Access sensitive password data • Compromise multiple accounts and could access all passwords I have saved on the password app. So, Let’s say my girlfriend knows my phone passcode, she pretty much then has access to all other password and backup codes I have saved on the password app. For this security vulnerability I believe it would be beneficial to introduce more advanced security options for accessing the Password section on iPhone. Specifically, 1. The ability to require Face ID only, without fallback to device passcode. 2. An option to set a dedicated password just for accessing the Passwords section (separate from the phone passcode). 3. Additional optional layers of protection, such as two-factor authentication or a biometric lock, that would prevent access even if someone knows the device passcode. These features would provide an extra level of security for users who are concerned about unauthorized access if someone gains access to their phone passcode.

System: OS: macOS 15.5 CPU: (10) arm64 Apple M1 Pro Memory: 82.02 MB / 16.00 GB Shell: 5.9 - /bin/zsh` IDEs: Xcode: 16.1/16B40 - /usr/bin/xcodebuild Managers: CocoaPods: 1.15.2 - /Users/liuxiwei/.rvm/gems/ruby-3.3.5/bin/pod SDKs: iOS SDK: Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1 Android SDK: Not Found i use react-native to build ios app . when archive than it happens: ld: Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5184.

After updating to iPad iOS26 , the software update area shows that it cannot check for updates. Is this normal?

Hello Apple Developer Community, I'm encountering a persistent issue while attempting to create a new partition on my Mac, and I'm hoping to get some assistance or insights from anyone who might have faced a similar problem. Issue Description: I'm trying to partition my internal drive. I initially used Disk Utility.app for this purpose. The partitioning process starts, but consistently freezes when it reaches approximately 10-20% completion. I've left it running overnight (for over 9 hours), but there was no progress, and the application remained unresponsive at that percentage. After several attempts with Disk Utility, I decided to try using the diskutil commands in Terminal to see if that would yield a different result. I used commands such as diskutil apfs resizeContainer and diskutil partitionDisk. Unfortunately, these commands also result in the same behavior: the process starts, reports progress up to about 10-20%, and then completely freezes without any further output or completion, requiring me to force-quit Terminal. Mac Model: Apple M4 Pro MacOS Version: Sequoia 15.6

Hey there, Just writing here to say how I do enjoy the latest update, but I can’t seem to run it on my iPhone 14 Pro well because it tends to overheat. i can deal with the stuttering issues and app crashes, that’s understandable, but for some reason the hardware seem to really heat up after normal use (scrolling on social media platforms). oh also, I do think rolling back your phone‘s software should be a simpler process as well. It’s not impossible, but the demand of a computer in reinstating a previous backup when iCloud backups your device through WiFi seems like a missed opportunity. Okay. Thank you for reading.

There seems to be a broken USB sync and Finder recognition issue. Is there a fix to this?

When I startAdvertising, my localName is long，Will not be truncated and the type is 0X09; self.advertisementData = @{CBAdvertisementDataLocalNameKey: localDevName, CBAdvertisementDataServiceUUIDsKey: @[[CBUUID UUIDWithString:serviceUUID]] }; [self.peripheralManager startAdvertising:self.advertisementData]; IOS 18.5: The service uuids in ADV_IND occupies 24 bytes, the local name in SCAN_RESP is 20 bytes in size and has not been truncated, and there is no manufacturer specific data in SCAN_RESP;You can view the following image： But in IOS26, why is the local name truncated to only 6 bytes for the same message, and why does SCAN_RESP always contain Manufacturer Specific Data; Why is there such a big difference, and what changes has iOS 26 made for broadcasting? Is it necessary to include Manufacturer Specific Data in the IOS 26 SCAN.RESP message? What documents are available for reference? Is there any way to ensure that the local name is not truncated? Is there a maximum length limit Are there other ways to broadcast longer data? Does anyone know why? thank