Hello, I want to use universal links in my application, for which I need to get the TeamID and BundleId, for apple-app-site-association file. Can you please tell me, do I have to buy an Apple Developer Account at the time of development to do this, or can I get it all for free at the time of development?

Hello everyone, I am experiencing a similar issue to the one reported by aarshps: "I hope someone has encountered this specific pattern and resolved it, or can point me in the right direction to escalate the issue." In my case, my iOS Apple Developer account (Case ID: 102929769930) has been pending for 40 days. I have met all of Apple's requirements, but support staff stated they could not verify my subscription or enrollment. The only potential detail on my end is that the payment was made using my son's credit card (Felipe Silva Ferraz), while the developer account was registered under my own name (Ademir Gomes Ferraz). I have sent multiple emails through the support portal, and my account still hasn't been approved. If anyone has faced this pattern or knows how to properly escalate it, please let me know.

Gerstart Apple inteligente

When switching to a SwiftUI app (built with Xcode 26.5) from an app with an active keyboard, the target app's tab bar incorrectly floats above the keyboard safe area. This layout issue occurs even though the target app does not display a keyboard and contains only a tab bar and scroll views.

Dear Apple Developer Support, I am requesting assistance regarding my Organization enrollment, which has been stuck in "Being Processed" for an extended period. I have already contacted Apple Developer Support three times through the Contact Us page. Each time, I received only the automatic acknowledgment email with a Case ID. Unfortunately, I have never received any follow-up from a support representative. Because of this, our company is currently unable to complete Organization Verification and cannot publish our iOS application on the App Store. Could you please: Check the status of my enrollment. Confirm whether my previous support requests were actually received by the Enrollment team. Escalate this case to the appropriate team if necessary. For your reference, my previous Case IDs are: Case ID: 102916885584 If you require any additional information or documentation from our company, please let me know. I will provide it immediately. Thank you for your time and assistance. I would greatly appreciate any update regarding the status of our Organization Verification. Kind regards, Dev UXUI Enrollment ID: WDF7RSUZ7P Company: Patana Intercool Company Limited

My device is Hong Kong version iPhone 16e with HK Apple ID. After updating to iOS 27 Beta 1, the "Apple Intelligence & Siri" menu is completely missing from Settings. Only the legacy "Siri" icon appears in that location. There is no option to join the "Try New Siri" waitlist, and none of the AI features are accessible. What I've tried (all failed): · Multiple reboots · Reset All Settings · Reset Location & Privacy · Toggling Siri language between English (US) and Traditional Chinese · Removing and re-adding keyboard languages Hardware eligibility: The device meets all requirements for Apple Intelligence (A17 Pro or later, 8GB RAM). The issue appears to be a system-level configuration loading bug that prevents the OS from recognizing the device as eligible, despite being a Hong Kong unit with a Hong Kong Apple ID. Feedback Assistant ID: FB23733608 Has anyone else with a non-US region device encountered this on iOS 27 Beta 1? Any temporary workaround would be greatly appreciated. Otherwise, I'll wait for Beta 2.

On the IOS 27.0 on my IP 16PM, I see it reduce heat significantly and after the next update, I see many bugs like keyboard stuck on tiktok app and heat more than 27.0. May I know it is the tiktok app issue or bug?

Since upgrading to iOS 26, my iPhone 15 Pro (A17 Pro) exhibits persistent battery drain and thermal issues. Console.app analysis via Mac reveals a cluster of related kernel and daemon errors that appear to stem from a driver-level regression rather than a hardware fault. Observed errors (continuous, since boot): thermalmonitord fails to read the cpu-avg-limiter-input-w2r property every 5 seconds indefinitely. This leaves the thermal throttling subsystem unable to regulate CPU load using its primary input sensor. The kernel logs SPMI bus faults on nub-spmi1 at a perfectly regular 30-second interval (codes 0x72040C01, 0x75E40C3B, 0x72D80C33), alongside aop-spmi0 faults (0x7A000830). The strict periodicity strongly suggests a driver retry loop rather than a dead hardware component. appleh16camerad (ISP driver) fails to initialize endpoint 1 (fISPEndpoints[1] is not ready) and retries every ~4 seconds, while the ANE driver (ANE0) cannot register its memory unwire timer. Both run in permanent retry loops consuming CPU cycles. AppleSMCFamily logs kSMCKeyNotWritable errors on SMC write attempts — the key exists but is flagged non-writable, suggesting incomplete driver initialization rather than a missing component. A single AppleSARService coredump request for the baseband was also observed. Why this appears to be a driver issue and not hardware: The system remains stable with no kernel panics or forced reboots. The SPMI faults occur on a precise 30-second schedule consistent with a kernel timer, not random hardware failures. The SMC error is kSMCKeyNotWritable (key present, wrong state) rather than kSMCKeyNotFound. All symptoms appeared immediately after the iOS 26 update with no physical event on the device. Device: iPhone 15 Pro — A17 Pro iOS version: 26.0 Reproduced: persistent across reboots, not tied to any specific app or usage pattern Has anyone observed the same pattern on A17 Pro devices? And has Apple acknowledged any SPMI / thermalmonitord regression in iOS 26 for this chip family?

I’m seeing a Bluetooth call audio routing issue on a new iPhone 17 Pro running iOS 26.5.1, build 23F81. Bluetooth media audio works normally. Music and video audio stay on Bluetooth headphones without issues. The problem appears only when the device switches into call audio / HFP mode. Tested with multiple earbuds: Samsung, OPPO, Huawei and CMF Buds Pro 2. The behavior is similar with all of them. There are no other Bluetooth devices connected. Call Audio Routing is already set to Bluetooth Headset in Accessibility settings. The issue affects cellular calls, FaceTime Audio, Telegram and Signal. In some cases the earbuds seem to switch into call mode, but the call audio route falls back to the iPhone receiver or speaker instead of staying on the Bluetooth headset. After the call ends, Bluetooth media audio returns normally. I captured a sysdiagnose right after reproducing the issue. Relevant observations from the logs: Device: iPhone18,2 iOS: 26.5.1 Build: 23F81 Sysdiagnose time: 2026-06-03 11:22:03 +0300 In Bluetooth/CoreCapture/bluetooth_status.txt, Bluetooth was ON 3 paired devices were present 1 device was connected Connected device at the time: CMF Buds Pro 2 So the headset was not simply disconnected from the phone. In the powerlog, before the call the audio route was HeadphonesBT for media playback. Around the FaceTime Audio test, HeadsetBT / PhoneCall appeared, but then the route moved to ReceiverAndMicrophone / Speaker instead of staying on HeadsetBT. During a later cellular call, the active PhoneCall route was also ReceiverAndMicrophone rather than HeadsetBT. After the call ended, the route returned to HeadphonesBT for media playback. This looks like the Bluetooth connection remains alive, but call audio / HFP routing fails. The same sysdiagnose also contains CentauriFirmwareEvent entries under crashes_and_spins from the previous day. They show: subsystem = BT host-reason = firmware crash BTMAIN panic faulting_task = link_manager_thread LMAC_5G watchdog expired SCAN watchdog expired These firmware crash events do not happen at the exact same timestamp as the call test, so I’m not claiming that every call directly crashes Bluetooth firmware. But the sysdiagnose shows both incorrect Bluetooth call audio routing and separate BT firmware crash events. Has anyone seen similar behavior on iPhone 17 / iOS 26 with Bluetooth HFP call audio? Could this be a known iOS 26 / Apple N1 / Bluetooth firmware issue, or does it look more like a hardware defect of this particular device?

Hi everyone, I’ve been stuck on an issue with iOS Universal Links for about a week and could really use some help. The problem When tapping a Universal Link on iOS, my Flutter app opens correctly (desired behavior) — but immediately afterward, Safari opens the same link in the browser. So both the app and the browser open. This only happens on iOS. On Android everything works as expected. What works If the link is simply the domain, like: https://mydomain.com …then the app opens without triggering the browser afterward. This is the correct behavior. What doesn’t work If the link includes a path or parameters, like: https://mydomain.com/path https://mydomain.com/path?param=value …then the app opens, and then the browser opens immediately after. What I’ve tried Verified my AASA file using Branch’s validator: https://branch.io/resources/aasa-validator/ → The AASA file is valid. Universal Links do open the correct screen inside the app — the issue is the unwanted second step (Safari opening). Behavior is consistent across different iOS devices. Extra details Using Flutter. Universal Links set up with the standard configuration (associatedDomains, AASA hosted at /.well-known/apple-app-site-association, etc.). Question Has anyone encountered this issue where Universal Links with paths/params open the app and then open Safari? What could cause iOS to trigger the browser fallback even when the AASA file is valid and the app handles the link correctly? Any insights, debugging tips, or known edge cases would be incredibly appreciated!

Hi, I'm having a strange issue with my new MacBook Pro M5. My iPhone 17 is connected via USB. The phone appears in Finder, so the Mac clearly detects it, and I can access it there. However, the Xcode doesn't see the iPhone at all. Both the MacBook Pro and the iPhone are running version 26.5. What's confusing is that the exact same iPhone and the exact same USB cable work perfectly with my older Intel-based MacBook Pro. Has anyone else experienced this, or have any suggestions on what I should check?

I recently updated my iPhone SE (2020) to the iOS 27 beta, and initially the experience was excellent. The phone felt noticeably faster and more responsive, and I was genuinely impressed with the update. However, after about a day of usage, I started experiencing a charging-related issue. One night, I left my phone connected to the charger before going to sleep when the battery was at 55%. The next morning, I found that the battery had dropped to 42% instead of charging. I checked all connections and confirmed that the charger, cable, and power source were properly connected. When I disconnected and reconnected the charger, the charging lightning bolt icon would briefly appear, then turn grey after about two seconds, and finally disappear completely a couple of seconds later. The phone would not charge. Assuming it might be a faulty charger or cable, I tested with: A different Apple charger A different Lightning cable The same issue persisted. Next, I connected the phone to my Mac. Surprisingly, it started charging, and Finder recognized the device normally. Over the next few days, the behavior became inconsistent: Sometimes the phone would charge. Sometimes it would not charge at all. Connecting to the Mac worked most of the time, but occasionally even that failed. I also noticed another unusual behavior: If I unplugged the Lightning cable from the iPhone and plugged it back in, the charging symbol would briefly appear. However, if I left the cable connected to the iPhone and unplugged/replugged only the USB end from the power adapter, there would be no response whatsoever—no charging sound, no charging icon, nothing. I cleaned the charging port, cable connectors, and charger contacts, but the issue remained. At that point, I realized the problem started immediately after installing the iOS 27 beta. To verify whether it was software-related, I restored the device back to iOS 26.5. After downgrading, the charging issue completely disappeared, and the phone began charging normally again with the same charger and cable. Based on my testing, this appears to be a software-related issue introduced in the iOS 27 beta rather than a hardware problem. I am posting this in case other iPhone SE (2020) users are experiencing similar charging behavior after updating to the beta. Device: iPhone SE (2020) Issue: Intermittent charging failure after updating to iOS 27 beta Status: Resolved after restoring to iOS 26.5

Environment: MacBook Air M4 macOS 27 Golden Gate Beta Xcode 27 Beta iPhone running iOS 27 Beta Apple Watch 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.

How can I get in touch with Apple Engineering since this doesn’t seem to work despite being told it’s the only way? I made this post in the appropriate forum several days ago. No responses. https://developer.apple.com/forums/thread/834948

I’ve found nothing about the waitlist, like when are there expected openings, how does an opening occur, and do I need to do anything else except join the waitlist? It’s been indexing for the same amount of time that I’ve been waiting for Siri, so is that a factor?

I am requesting technical clarification and a formal feature addition regarding the availability of per-frame calibration data for Standard RAW captures on iPhone 17 and 17 Pro. The Technical Gap: Currently, AVCaptureVideoDataOutput provides a direct path to the AVCameraCalibrationData object, allowing real-time access to the Intrinsic Matrix, Radial/Tangential Distortion coefficients, and Lens Shading Maps. However, this same level of geometric transparency is missing from the AVCapturePhoto RAW/ProRAW delegate. While standard RAW files contain some metadata, they lack the physics sidecar required for precision manual alignment. Because the lens assembly in the iPhone 17 Pro is dynamic shifted constantly by Optical Image Stabilization (OIS) and high-speed Voice Coil Motors (VCM) for focus a static or factor calibration is mathematically insufficient for high-precision workflows. The Problem: Without the 1:1 hardware state at the millisecond of exposure, we cannot perform accurate geometric reconstruction from RAW stills. We are forced to choose between the high dynamic range of a RAW sensor dump and the geometric precision of the video pipeline. Final Questions: Is there a documented, supported method to force the inclusion of the AVCameraCalibrationData object or a raw metadata sidecar in the AVCapturePhoto workflow? If not, can Apple provide parity between the Video and Photo APIs so that the "rawest" data (RAW) is accompanied by the "rawest" physics (Calibration Data)? Providing the pixels without the lens geometry limits the utility of the RAW format for any technical workflow requiring sub-pixel geometric integrity.

Hello, After adapting Liquid Glass for iOS 26.5, I encountered an issue: the leftBarButtonItem(s) shift right, leaving a large space on the left after launching and dismissing the camera. I tried adding a negative spacer and setting leading space, but neither worked. This only happens when launching the camera; it does not occur during photo selection.

If some Siri AI features work on cloud why not for older device? Apple Devs mentioned that the Siri AI is available for iPhone 15 and later devices and we can use iCloud+ Subscription to use it more on Apple’s Private Cloud Compute (PCC). So if it can run some functions on Private Cloud why not for people with older device? Or will Apple make it compatible with older devices on upcoming beta updates? Also, I noticed that other Phone companies have these features in phones that are way less powerful than iPhone 11 (Which is a oldest device support iOS 27) I tested some ai models from 3rd party apps that are less than 300MB and it worked very well than the old siri so can We add some Siri features to older iPhone? So we can avoid people from switching to other phones. Because I don’t want my friends leaving iPhone.

Hi there, Hope you are all well. I would like to know on how I am able to develop/build for both current software, like iOS 26 and iOS 27 at the same time. If it is possible, please let me know how. This is also my first WWDC as a developer, so I may have many questions. Sorry in advance lol. Thanks, Jason

We've 10 CoreML models in our app, each encrypted with a separate key generated in XCode. After opening and closing the app 6-7 times, the app crashes at model initialization with error: 2021-04-21 13:52:47.711729+0300 MyApp[95443:7341643] Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=com.apple.CoreML Code=9 "Failed to generate key request for 08494FB2-B070-440F-A8A5-CBD0823A258E with error: -42905" UserInfo={NSLocalizedDescription=Failed to generate key request for 08494FB2-B070-440F-A8A5-CBD0823A258E with error: -42905}: file MyApp/Model.swift, line 43 Looks like iPhone is blocking the app for suspicious behavior and the app fails to decrypt the model. We noticed that after ~10 hours the app is unlocked, it successfully decrypts and initializes the model. Opening and closing the app many times in a short period of time is indeed unnatural, but the most important question is how to avoid blocking? Would Apple block the app if a user opens and closes it 10 times during a day? How does the number of models in the app affect probability that the app will be blocked? Thanks!

Our organization is attempting to retrieve the External Version Identifier (EVID) history for all published versions. This data is required so that we can pass the exact externalVersionIdentifier integer to our deployment framework to pin specific app versions on our managed devices. We currently have an active App Store Connect account, but our attempts to fetch this data via standard publishing APIs return a 401 Unauthorized error. To help us resolve this technical blocker, please provide explicit engineering guidance on the following four points: API Endpoint Architecture: Is the enterprise Apps and Books for Organizations API (apple.com) the only platform that exposes the externalVersionId history for all versions? If so, what is the exact endpoint path we must call to return the full version-based EVID array? Account Requirements: Can these version-specific EVIDs be retrieved using our existing App Store Connect developer credentials, or is an Apple Business Manager (ABM) account strictly mandatory to bypass the 401 gate? ABM Portal Setup for EVIDs Only: If an ABM account is mandatory, what are the minimum technical steps required inside the ABM dashboard to fetch only the EVID data? Specifically, do we need to "purchase" a volume license for the target app to make its version history accessible via the API? Authentication Parameters: What is the correct token structure for this endpoint? Do we need to pass a specific location server token (sToken / itvt cookie) generated inside ABM alongside our signed developer JWT header? Thank you for your time and technical guidance. We look forward to your engineering team's response.