Date Free RAM at event TGOnDeviceInferenceProviderServi usage Sep 17 ~50 MB ~395 MB Sep 19 ~1.46 GB not in top processes Sep 20–22 ~215–246 MB not in top processes Sep 24 ~28 MB ~480 MB (highest so far) The pattern: the process appears to accumulate memory over ~3-5 days, then either gets cleared (reboot?) or briefly disappears from the top consumers, only to reappear and grow even larger than before. This has led to multiple Jetsam kill events (system processes like FindingUI, tipsd, cryptexd being terminated due to memory pressure) and noticeable UI lag when swiping between Home Screen pages / opening the App Switcher. Steps already taken (no lasting effect): • Confirmed Apple Intelligence + all related sub-toggles (Priority Notifications, Siri Suggestions per-app) are off • Multiple reboots (temporarily clears the issue, recurs within days) • Uninstalled unrelated resource-heavy apps (unrelated, but ruled out as a contributing factor) • Submitted Jetsam reports via Feedback Assistant (no response, as expected for that channel) Question: Has anyone else seen TGOnDeviceInferenceProviderServi retaining/growing memory usage on iOS 27.0 even with Apple Intelligence disabled? Is this a known on-device model caching issue, and is there a way to force it to release memory without a full reboot?

Dear Apple Team, Regarding the Central Kurdish keyboard, In the recent iOS updates, the layout of the letters was changed significantly, which has made typing extremely difficult and uncomfortable for us. We kindly request that you fix this issue as soon as possible by reverting the keyboard layout to the previous version. Thank you.

I am experiencing a severe Photos Search/People indexing problem on a Mac Studio running the final release of macOS 27. I first reported this during the macOS 27 beta cycle and have provided extensive diagnostics and updates through Feedback Assistant. Feedback: FB24521305 Resolution: Open Recent Similar Reports: More than 10 My iCloud Photos library contains approximately 164,000 items and is synchronized between my Mac, iPhone, and iPad. The photographs themselves are present on the Mac, and newly taken photographs synchronize normally. However, Photos Search and People & Pets on the Mac remain severely incomplete. Direct searches of the same synchronized library currently give: Frequently photographed Person A Mac Photos Search: 3 results Mac People & Pets: 6 images iPhone Photos Search: 2,390 results The 3 images returned by Mac Search are different from the 6 images in the People & Pets album. Person B Mac Photos Search: 0 results Mac People & Pets: 2 images iPhone Photos Search: 66 results Location search — Costa Rica Mac Photos Search: 37 results iPhone Photos Search: 350 results After installation of macOS 27 final, Mac Photos Search briefly showed substantial rebuilding activity. For example, a search for "2026" increased from 566 results to 4,455, and "Deer" increased from 79 to 908. Searches that had previously displayed an indefinitely spinning progress indicator also began returning results. However, that apparent rebuilding has not progressed to completion. Nearly two weeks later, People recognition/association remains extremely incomplete, location Search remains incomplete, and the Mac and iPhone return dramatically different results from the same synchronized iCloud Photos library. I have left Photos running for extended periods to allow background analysis to complete. Previous controlled tests also established that the Mac receives photographs and their correct date/time metadata and can index some newly received assets almost immediately. At this point the evidence appears to indicate a problem with the Mac Photos analysis/Search/People indexing process rather than iCloud Photos synchronization or missing assets. Could an Apple engineer please confirm whether FB24521305 has been routed to the appropriate Photos engineering team? I would be happy to provide additional diagnostics or perform specific controlled tests if requested.

Subject: Developer Account not activated after payment (More than 48 hours) Hello everyone, I registered for an Apple Developer Account and the enrollment fee was successfully deducted from my card on the 15th of this month. Although the confirmation page mentioned that activation usually takes up to 48 hours, my account is still not activated yet. I have already submitted a request/email to Apple Developer Support, but I haven't received a response so far. Is this delay normal, or is there a specific step I should take to expedite the process? Thank you in advance for your assistance!

Every macOS update fails during preflight personalization on my MacBook Pro (Mac15,6, Apple Silicon), currently on 27.0 build 26A5378j. It's failed on every build from beta 5 (26A5406e) through beta 7. Identical failure via Software Update and via startosinstall. It fails LOCALLY, before contacting Apple (gs.apple.com and gdmf.apple.com are both reachable with valid certs). Error (install.log + unified log): reaches PREFLIGHT_PERSONALIZE (~0.15), then aborts MobileSoftwareUpdateErrorDomain Code=1259 "failed to copy firmware identity" "could not obtain device identity information through SFR installer" SUMacControllerErrorPreflightPersonalizeFailed=7723 Root cause I've traced: an orphaned volume-group boot-policy directory in /System/Volumes/iSCPreboot/. ls shows two volume-group UUID dirs — the live one (matches diskutil info /) and an orphan (3D3287DE-...) with no corresponding APFS volume group (diskutil apfs list shows only one live group). Both date to Feb 2024. The preflight can't reconcile the System Recovery boot policy in the orphaned dir. Note: NOT caused by Erase All Content and Settings (unlike the commonly reported case). The orphan predates the beta, so any pre-existing second volume-group boot-policy directory reproduces it. It was harmless for ~2 years; macOS 27's stricter preflight rejects it. Ruled out (no effect): disk space, VPN, DNS, clock, Apple Account, refreshing the beta seed entitlement, reboot, Time Machine, re-downloading the installer, and Recovery reinstall (same 1259). Filed as FB24342236 — no response across beta 5, 6, 7. Questions: Is this a known issue with a planned fix, and in which build? Any supported recovery path that does NOT require a second Mac? (Recovery reinstall fails the same way.) Or is DFU Revive/Restore the only option? Will the public 27.0 release install on this machine, or hit the same preflight?

test

test

Hi, I am currently trying to accept an Account Holder transfer for our Apple Developer account. My ID verification has already been completed successfully in the Apple Developer app. The issue is with the address verification step. I receive an “Action not allowed” error when I try to continue. I have already tried: The business address used for our Apple Developer account registration. My current personal residential address. A previous personal residential address linked to my Apple Account. None of these addresses are being accepted, even though my ID verification is successful. Has anyone experienced this issue before, or does anyone know what Apple specifically validates the address against during an Account Holder transfer? This is currently preventing us from completing the transfer and is blocking an App Store submission. Thank you.

I use Siri daily on iPhone and Mac, and it fails at basic things: It doesn't understand follow-up questions or context. For most questions it just shows web results instead of answering. It misunderstands simple requests, and I have to repeat them. It can't chain two actions in one request. Meanwhile, other AI assistants handle all of this without problems. As a developer and daily user, I would like to know: Is there a public roadmap for Siri improvements? Will developers get better APIs to make Siri useful inside our apps (beyond App Intents)?

I’m just a learning

Heads up if you're on the fence — Golden Gate is straight up not playing nice with Premiere Pro yet. I updated for testing content and immediately regretted it: crashes on launch, choppy playback, exports failing halfway. No word from Adobe on a fix. If Premiere's part of your workflow (editors, this means you), hold off on updating until they patch it. Not worth breaking your pipeline for a few UI tweaks.

你好，我想报告更新到 iOS 27 后出现的兼容性问题。 我使用的是iPhone 17 Pro Max。更新到 iOS 27 后，我在访问某个第三方视频网站时遇到了严重的冻结问题。 浏览网站时不小心点击了视频缩略图，缩略图顶部会出现一个灰色加载条。加载完成后，会自动弹出视频预览，整个设备随后完全失去响应。唯一的恢复方法是强制重启iPhone。该期大约有10次尝试中能重现8到9次。 这个问题在升级到 iOS 27 之前没有出现。 我还有iPhone XR和iPad。在这些设备上访问同一个网站时，一切正常，视频预览也不会让设备卡死。 我还用iPhone 17 Pro Max上的其他浏览器测试了同一网站，设备依然无响应。不过，到目前为止我在测试其他视频网站时还没遇到过同样的问题。 目前我无法判断这是我设备特有的问题，还是网站兼容性问题，还是iOS 27或WebKit的问题。 我希望苹果能调查并记录这个问题。如果需要更多信息或确切的网站网址以便调查，我可以通过合适的支持渠道提供。 如果苹果社区有人在升级到 iOS 27 后遇到类似问题，欢迎分享你的经历或任何可能原因的信息。 谢谢。

I’m Ashutosh Kahlon, a developer and community builder from India. I’m building Devvrats — a community for people who are curious about technology and want to learn, create, contribute, and Thrive together. The idea is simple: bring people with different experiences, skills, and perspectives into the same space. Devvrats isn’t meant to be only for experienced developers. Whether someone is just beginning, exploring their first programming language, building projects, contributing to open source, or already working as a professional engineer, there should be a place for them to learn and contribute. We’re working toward an ecosystem around: Culture — building a community with its own character and values Ideas — sharing thoughts, experiments, and things worth exploring Learn — learning together and helping people who are finding their direction Create — turning ideas into projects and experiences Together — connecting people across different backgrounds and skill levels We’re starting from India, with the ambition to connect people across India and eventually beyond. For me, Devvrats is less about creating another developer club and more about creating a space where people can come together, learn from one another, and build things that matter to them. I’m also interested in connecting with other Apple developers and communities, particularly around Swift, SwiftUI, app development, design, and the culture of building for Apple platforms. If you’re building something, learning something, running a community, or simply curious about what others are creating, I’d love to connect. Culture. Ideas. Learn. Create. Together. — Ashutosh Kahlon Founder, Devvrats.

Hello, I would like to report a compatibility issue that appeared after updating to iOS 27. I am using an iPhone 17 Pro Max. After updating to iOS 27, when accessing a specific third-party video website through a VPN, accidentally tapping a video thumbnail causes a gray loading bar to appear. Once the loading finishes, a video preview immediately pops up, after which the entire device becomes completely unresponsive and can only be recovered by force restarting the iPhone. The issue can be reproduced approximately 8–9 times out of 10 attempts. This issue did not occur before updating to iOS 27. I also have an iPhone XR and an iPad, and the same website works normally on both devices without automatically displaying the video preview. On the iPhone 17 Pro Max, I also tested the website using other browsers, and the device still became unresponsive. However, I have not encountered the same issue when testing other video websites so far. Relevant websites: https://up.9p58b.com/ (accessible directly in mainland China) https://91porn.com (requires a VPN) I am a user in mainland China. Due to the sensitive nature of these websites, I would prefer that other users not be asked to visit them specifically for testing purposes. At this point, I cannot determine whether this is an issue specific to my device, a website compatibility issue, or an issue with iOS 27 itself. I hope Apple can investigate and record this issue. If this is confirmed to be a known iOS 27 or system compatibility issue, I hope it can be addressed in a future software update. If it is determined to be an issue with the website’s own compatibility, it would also be helpful to know that, so that the source of the problem can be better understood. I would appreciate it if someone could respond to this post and let me know whether this issue has been encountered by others or is already known to Apple. Thank you.

Now that Apple has apparently removed the web interface from CUPS from MacOS27 (though there's no mention of it in the Release Notes); what is the sanctioned method of configuring print queues and setting their defaults? Have we got to use lpadmin and lpoptions? #progress

Every time I edit anything in the editor Xcode crashes. I did some research and found that if I disable code completion I dont get this issue but code completion is a huge time saver so I dont want to lose that. I have tried clearing my build folder, deleting derived data switching from Xcode 27.2 to 27 and 27.1 but I keep getting the same issue. This is a known issue in 27.2 (186939138) but it isn't listed anywhere else, am I the only person getting this bug? Anything else I should try? This just started happening today, my Mac updated to 27.2 last night. Mac OS 27.2, M4 Pro

Hi Apple Developer Forums, I’m a heavy user of the Shortcuts app and the new multiple timers in iOS have been incredibly helpful. However, there is one limitation that makes them hard to use in automations. Right now, the “Start Timer” action in Shortcuts does not let you set a Label for the timer. This means when a timer created by a shortcut goes off, I can’t tell what it was for (for example, a 15‑minute laundry timer vs. a 15‑minute tea timer), even though labeled timers already work perfectly in the Clock app. Feature request: please add a Label field to the “Start Timer” action in Shortcuts so automations can create named timers, just like in the Clock app. This would make multiple timers much more practical for automation and for power users. Thank you for considering this improvement.

Try out Reboot UI buttons and let me know if you would use it. https://testflight.apple.com/join/5wPEf15k

I’m trying to determine whether this is a known macOS/firmware issue, a hardware issue, or something else in the Apple-silicon sleep/power-management path. Hardware / software: MacBook Pro 14-inch (Nov 2023), M3 Pro Model identifier: Mac15,6 11-core CPU, 14-core GPU, 18 GB RAM macOS Tahoe 26.6.2 (25G83) SoC T6030, revision 11 iBoot / firmware: mBoot-18000.161.10 Symptom: The Mac intermittently performs a full reset/reboot while the lid is closed and it should be asleep. I usually discover this when I open the lid and find that the machine has rebooted rather than waking normally. A particularly disruptive aspect is that this happens when I transport the Mac while the lid is closed. If I put the sleeping MacBook in a backpack and carry it, or even simply carry it in my hands with the lid closed, I can later find that it has reset (the startup sound plays) and booted to the startup disk selection / startup options screen instead of remaining asleep. This behavior makes normal closed-lid transport unreliable. The correlation with movement while the lid is closed is one of the reasons I initially suspected something involving the lid sensor, sleep-state handling, or another hardware/power-management component. However, I can also reproduce the reset with the computer completely stationary on a desk, so physical movement is not required to trigger the failure. The failure is strongly correlated with clamshell sleep/dark-wake transitions. It can happen shortly after closing the lid or several minutes later. This is not just an application crash. Multiple reproductions have generated ResetCounter reports and PMU watchdog/reset fault data. Most recent reproduction (verified Safe Mode): I booted using Apple-silicon Safe Mode and personally verified that “Safe Boot” was displayed before testing. I then closed the lid normally and left the Mac alone. It rebooted after a few minutes, while the lid was closed. Immediately afterward macOS created a new type-115 ResetCounter report. Relevant fields: Boot failure count: 1 Boot faults: rst btn_rst,btn_seq_reset target_off_shutdown Boot stage: 0x40 socId: 6030 socRevision: 11 DumpPanic then read auxiliary PMU fault data containing: wdog,reset_in_1 rst_in,reset_in_1_deassert During the same boot, the AppleSPMIPMU driver logged: rst crash,crash_in wdog,reset_in_1 rst_in,reset_in_1_deassert and another PMU entry contained the same sequence plus: rst btn_rst,btn_seq_reset target_off_shutdown I am not assuming undocumented meanings for every PMU flag. For example, I am not treating btn_rst as proof that a physical power button was pressed. The important point is that the same low-level watchdog/reset pattern has occurred repeatedly. Also, DumpPanic successfully read 3,145,728 bytes from the panic area, but reported: it did not contain any paniclog data (buffer was all zeros) No paniclog data found in local device So there is no normal surviving kernel panic report to inspect. Earlier controlled reproduction after reinstalling macOS: I performed an in-place reinstall of macOS from Recovery. The machine was confirmed to be running 26.6.2 (25G83) afterward. Immediately after the reinstall I ran another controlled test while recording kernel/powerd/powerexperienced/DumpPanic logs. I closed the lid once and did not touch the machine. The logs showed a normal physical close sequence: SMC HID Event: 03 01 00 PMRD: Clamshell closed clamshell closed 1 sleep reason Clamshell Sleep macOS then entered the clamshell sleep path. Shortly afterward it transitioned from dark wake to full wake due to HID activity, even though I had not physically reopened the lid. A corresponding low-level Clamshell opened event was not present in the captured stream, and the kernel continued to report: clamshell closed 1 It then attempted clamshell sleep again and entered dark wake with: DarkWake: sleepASAP 1, clamshell closed 1 The machine later reset. On the following boot a new ResetCounter reported Boot failure count: 1, and the auxiliary PMU fault data again contained: wdog,reset_in_1 rst_in,reset_in_1_deassert The kernel PMU log also contained crash,crash_in. DumpPanic again read 3,145,728 bytes and found the panic buffer all zeros. There was another earlier controlled reproduction with the same PMU watchdog/reset class, so this is not a single isolated event. Lid-angle / clamshell testing: I separately monitored the low-level lid events while deliberately opening and closing the display. Normal physical movements produced coherent pairs such as: SMC HID Event: 03 01 00 / PMRD: Clamshell closed and: SMC HID Event: 03 00 01 / PMRD: Clamshell opened I did not observe simple spontaneous open/close flickering while the display was stationary. This does not completely rule out an intermittent lid sensor/flex/magnet issue, but it does not look like a straightforward continuously-failing lid sensor. Other troubleshooting: Apple Diagnostics reports no issues. The issue survived an in-place macOS Recovery reinstall. The issue reproduces in verified Safe Mode. I have not found a conventional kernel panic payload for these failures. I am not attributing the issue to Wi-Fi, Bluetooth, Chrome, ANE, or any other subsystem based only on incidental log messages. Previous Apple repair: Earlier this year Apple serviced the machine for the same exact symptoms. The service summary says the following parts were replaced: Logic board — symptom category: System Startup/Stability/Unexpected Restart/Shutdown Lid Angle Sensor — symptom category: System Startup/Stability/Will Not Sleep Touch ID board MagSafe 3 board The same closed-lid reset problem continues after that repair. What I’m trying to understand: Is this PMU watchdog/reset pattern known on M3 Pro / T6030 systems during clamshell sleep or dark wake? Are there specific sysdiagnose, power-management, PMU, or firmware logs that would be useful to Apple engineering? Would a DFU firmware Revive be a meaningful next isolation step given that Recovery reinstall, Safe Mode, diagnostics, and a prior logic-board/lid-sensor replacement have not resolved it? I can provide sanitized ResetCounter output and relevant unified-log excerpts. I have intentionally omitted serial numbers, repair identifiers, CrashReporter keys, account information, and other identifying details here.

We have had a difficult time getting our developer account approved and it has been many months. The orginator has left the company, and even though she has tried from her current role to get a resolution, nothing seems to work. We have made many, many calls and emails, and nothing seems to help. Anyone have any ideas?