Yesterday I checked the screen time of the previous day and I thought it was 7h.But it is presented to be 10h and a half today.I'm confusing why the ended screen time could change.

Since download, having trouble with messaging uploads and email uploads across both Mac book and iPhone. Anyone having same issues.

I'm having issues with my phone overheating every time I’m on a FaceTime call and phone is charging in a well ventilated room. Is anyone else having this issue?

Core Objectives Automate supply-chain transactions Automate service-ticket follow-up Remove location-dependent logic Reduce human intervention and phone/email follow-ups Provide real-time visibility Subjects of Concern/Proposal :- Create a Unified Workflow Engine Instead of region-specific processes: Define global workflow templates. Use configurable business rules. Allow country/region exceptions only through parameters. Example: Process Current State Improved State Order Approval Different by location Single workflow with configurable rules Vendor Onboarding Manual emails Automated onboarding journey Service Escalation Local team dependent Rule-based escalation engine ⸻ Make the Portal Location-Neutral Avoid: Hardcoded country workflows Region-specific approval chains Manual routing by geography Use: Role-based access control (RBAC) Business-unit based routing Product-category routing Service-priority routing Instead of: “Send to Singapore team” Use: “Send to Inventory Operations Manager role” This allows teams to change without changing processes. ⸻ Introduce Self-Service Tracking Provide users with: Order status Shipment status Inventory availability Service request status SLA countdown Escalation history This reduces: Phone calls Emails Chat follow-ups ⸻ Automate Service Follow-Up Implement automated actions: Trigger Examples Event Action Ticket created Auto acknowledgement No update for 24h Reminder SLA breach risk Escalation Resolution completed Customer validation request Customer silent for 7 days Auto-close workflow ⸻ Use AI-Powered Assistance Introduce: Virtual service assistant Knowledge-base search Automated ticket classification Suggested resolutions Automated case summaries Benefits: Less manual communication Faster resolution Consistent handling ⸻ Event-Driven Integration Connect portal with: ERP CRM Logistics systems Inventory systems Vendor systems Using APIs and events: Purchase Order Created ↓ Inventory Updated ↓ Shipment Triggered ↓ Customer Notified ↓ Service Monitoring Started No manual status updates required. ⸻ Centralized Dashboard Provide a single dashboard showing: Supply Chain KPIs Order cycle time Inventory levels Supplier performance Shipment delays Service KPIs Open tickets SLA compliance Resolution time Customer satisfaction ⸻ Digital Communication Instead of Manual Talk Replace phone calls with: Portal notifications Automated emails In-app messaging Workflow comments Audit trail Every action becomes traceable. ⸻ Governance and Auditability Maintain: Complete transaction history Approval logs Change tracking Automated compliance reporting This is especially important for large-scale global operations. ⸻ Suggested Future-State Architecture Apple Account Portal │ ├── Identity & Access Management ├── Supply Chain Workflow Engine ├── Service Management Module ├── AI Assistant ├── Notification Engine ├── Analytics Dashboard └── API Integration Layer │ ├── ERP ├── CRM ├── Logistics └── Vendor Systems The key principle is to move from location-based processes and manual communication to role-based automation, event-driven workflows, self-service visibility, and AI-assisted follow-up. This creates a scalable global portal that operates consistently regardless of geography. Proposal: Automated Versioned Escalation Framework for Apple Support Portal Objective Enhance the Apple Support and Apple Developer support portals by introducing a version-controlled escalation workflow that minimizes manual follow-up, increases transparency, and improves issue resolution efficiency for Apple product development teams and enterprise users. Current Challenges Manual follow-up through multiple support interactions. Limited visibility into escalation history. Inconsistent handling across regions and support teams. Lack of structured progression tracking for complex technical cases. Difficulty understanding current ownership and next action. Proposed Solution Escalation Versioning Each ticket receives an escalation version number: V1 – Initial Support Review V2 – Technical Specialist Review V3 – Engineering Investigation V4 – Product Team Assessment V5 – Executive Escalation Every escalation creates: Timestamp Escalation reason Assigned owner SLA target Resolution notes Full history remains visible within the portal. 2. Automated Follow-Up Engine The portal automatically performs: Status reminders SLA monitoring Escalation triggers Resolution confirmations Closure validation No manual follow-up emails are required for standard progress updates. 3. Transparent Workflow Dashboard Display: Current escalation version Assigned support team Expected response date Investigation stage Historical escalation path Role-Based Routing Cases are routed according to: Product category Technology domain Severity level Business impact Rather than geographic location. 5. Developer-Centric Features Especially beneficial for: App Store submissions Developer Program support API issues Account management issues Framework and SDK investigations Enterprise deployment support Expected Benefits Faster issue resolution Reduced manual communication Better auditability Improved user confidence Consistent global support experience Enhanced visibility for product development teams Suggested Workflow Ticket Created
↓
Automated Acknowledgement
↓
V1 Support Review
↓
Issue Resolved?
├─ Yes → Closure Validation
└─ No
↓
V2 Specialist Review
↓
Issue Resolved?
├─ Yes → Closure Validation
└─ No
↓
V3 Engineering Investigation
↓
Issue Resolved?
├─ Yes → Closure Validation
└─ No
↓
V4 Product Team Assessment
↓
V5 Executive Escalation (if required)
↓
Final Resolution
↓
Knowledge Base Update
↓
Case Closure Process Flow Visualization Ticket Created │ ▼ Auto Acknowledgement │ ▼ Version 1 (Support) │ ├── Resolved → Close │ ▼ Version 2 (Specialist) │ ├── Resolved → Close │ ▼ Version 3 (Engineering) │ ├── Resolved → Close │ ▼ Version 4 (Product Team) │ ├── Resolved → Close │ ▼ Version 5 (Executive Escalation) │ ▼ Final Resolution │ ▼ Knowledge Base Update │ ▼ Case Closure This concept would be particularly useful for users working with Apple Inc. product development, developer accounts, App Store operations, SDK/framework issues, and enterprise support because it creates a traceable escalation path instead of relying on repeated manual follow-ups.

The option of 'Prefer opening messages in Split View when in Full Screen' doesnt seem to work in Mac OS Golden Gate. When I open Mail in Full Screen mode and then click on new email compose button, a new window emerges from the bottom of the screen, rather that the mail splitting the screen to accommodate the same window on the right side. Please help!

Hello everyone, I am using an iPhone 11 Pro running iOS 27 Beta 1. Since installing the beta, the message "Indexing in Progress" has remained active for approximately 7 days and never completes. I have already tried: Restarting the iPhone multiple times Keeping the device connected to power overnight Keeping Wi-Fi enabled Disabling Low Power Mode Ensuring enough free storage space Despite trying all of these steps, the indexing process is still stuck and does not finish. Is anyone else experiencing the same issue on iOS 27 Beta 1? At this point, I believe this may be a bug affecting Spotlight/Search indexing. Any feedback would be appreciated. Thank you.

Description: When a user's iCloud storage is full, the Notes app continues to save recent edits locally to a pending-sync cache. However, if the user toggles iCloud Notes sync to "Off" in System Settings, macOS executes a total database purge script. The system completely ignores error flags indicating that the local edits never successfully reached the cloud server. This creates a critical edge case resulting in permanent user data loss. Requested Change: Implement an explicit safeguard check prior to executing the local cache purge. If local_edits > cloud_edits, the system must present a warning modal stating: "Your most recent edits have not yet uploaded to iCloud due to full storage. Disabling sync will permanently delete these un-saved notes from this device."

After updating iOS27beta on the mainland Chinese version of iPhone, the airpods option contains real-time translation, but it can't be used after downloading. If there is no appleai, can't it be used at all?

Why should we get apple developer program for appkit and to publish apps?

I received the beta 2 update in Software Update today, downloaded it, and it went through the entire installation process including the reboot. However, once my phone powered back on it did not show the updated version confirmation and is still running iOS 27.0. After troubleshooting, Software Update now shows my software is up to date and beta 2 is no longer available to download. I also attempted to install via iTunes on PC using the Shift + Check for Update method but the IPSW file for my device is not yet available on ipsw.me. Has anyone else experienced this? Any suggestions on how to get beta 2 installed successfully?

This is not a minor visual glitch or a negligible beta bug; this is a catastrophic telecom and safety failure. In iOS 27 Developer Beta, attempting to activate Wi-Fi Calling for US carriers (like RedPocket, Mint, T-Mobile, etc.) that require an E911 address registration completely hard-crashes the Settings app. You cannot activate Wi-Fi Calling, you cannot register your emergency address, and your cellular service is effectively crippled. As an SRE, I pulled the Console logs and traced the crash. It is absolutely unacceptable that Apple is still relying on the ancient, long-deprecated ⁠UIWebBrowserView⁠ inside ⁠TPSCloudCallingWebViewController⁠ for a critical emergency service configuration page. The Settings app is dying from a dual-concurrency crash caused by aggressive iOS 27 refactoring colliding with this legacy web container: The Apple Intelligence / TextInputUI Collision: On page load, the new text prediction engine blindly scans the legacy web input fields and throws a fatal exception: ⁠-[UIThreadSafeNode _smartReplyUpdateInProgress]: unrecognized selector sent to instance⁠. The old web node simply doesn't support the new Smart Reply APIs. The WebKit Thread Violation: This input system failure (⁠RTIInputSystemClient⁠ invalidation) cascades into a complete WebKit thread deadlock. The engine attempts to parse the carrier's CSS and throws a fatal UIKit assertion: ⁠Modifying properties of a view's layer off the main thread is not allowed⁠. The OS instantly sends a ⁠SIGABRT⁠ to ⁠com.apple.Preferences⁠. I have tried every possible workaround: Disabling JavaScript, removing 3rd-party/foreign keyboards, turning off predictive text, and even using MITM proxies to strip the CSS from the carrier's gateway. Nothing works. The crash happens instantly on load because the TextInputUI injection and the background-thread layer mutation are hardcoded into the OS framework. It is utterly absurd that a broken Smart Reply UI prediction path can block a user from registering an emergency 911 address and activating their phone service. Apple, you need to fix this immediately. Either rewrite ⁠TPSCloudCallingWebViewController⁠ to use a modern ⁠WKWebView⁠, or patch ⁠TextInputUI⁠ to gracefully handle legacy ⁠UIThreadSafeNode⁠ instances. Do not ship another beta with a broken carrier service page.

I would like to request a review regarding my account ban in Swords of Glory by Brother Games. The developer stated that the reason for the ban was the use of comments considered inappropriate toward a staff member. I would like to clarify that my intention was not to insult or personally attack anyone, but rather to express my frustration regarding how my issue was handled and request a fair review of my case. My account had significant progress, including Castle Level 31 and around 800 million Power. Despite this, my account was banned without what I believe was a sufficient or fair review process. I kindly request Apple to review this matter and ensure that users’ rights, digital content within the app, and fair and transparent account review procedures are properly considered. I have attached the available evidence, including communications with the developer.

Hello, I would like to seek advice regarding the game Swords of Glory by Jo Wu / Brother Games. My account was banned after I expressed my frustration about how my issue was handled. The developer stated that the reason was using inappropriate words toward a staff member. I would like to clarify that my intention was not to personally insult anyone, but rather to express my dissatisfaction with the way my case was handled and request a fair review. My account had significant progress (Castle Level 31 and around 800 million Power). I was also a supportive player who provided several positive suggestions to improve the game experience, including ideas for map design, character concepts and names, interface icons, text improvements, and player avatar icons. I would like to understand what options are available for users in such situations and whether there is a way to review account bans, especially when the account has significant progress and digital content. Thank you to anyone who can provide advice or guidance.

Once, when I connected to a company's Wi-Fi, I needed to manually set my local IP address to use it. Later, I discovered that my home's auto-configured IP address had reverted to the one I had manually set, which was on a different network segment than my home gateway, causing me to be unable to connect to the internet. I later found that all my auto-configurations had reverted to the IP addresses I had manually set, and even deleting the manually configured SSID didn't change it back. Interesting.

I created my developer account on Wednesday and paid for the subscription straight away, but I’ve been waiting ever since. It says that processing can take up to 48 hours, but I’ve now been waiting for five days and nothing has changed... I’ve contacted customer service but haven’t received a reply. Is this normal?

When I trying to disable sip it just says csrutil: Failed to update security configuration for "Macintosh HD": Manifest verification failed

When transferring photos from my iphone 16 Pro Max running the IOS 27 Developer Beta to a Windows 11 PC via a USB-C cable the photos convert to AAE files, which you can't preview of view.

I was asked to migrate my individual Developer Account to Organization account as a condition to approve one of my apps because of the data the app was collecting. Before I started the migration I was told it will take 3-4 days and a maximum of a week. Its been a month and every time I call they just tell me they will escalate to a supervisor and they cannot also tell how much longer it will take. I provided all my documents on day 1 and I already have a published app. Now I cannot even update my app that is live and neither can I get approval to the app that has been in review. If they had told me they cannot migrate on time, I would have created a business account instead of taking this approach. Apple wouldn't give me even a timeline. This has not been the experience I was hoping for. Has anyone else had similar experience.

I have two lines through Verizon wireless, my main line for the account was acting like a dead eSIM every time it is on it kills my data completely even on the second phone line unable to send a receive phone calls, send a receive text messages, retrieve voicemails, or use data in any capacity from that line. I have completely deleted and reinstalled and reactivated eSIM for that line a handful of times in the last week/week and a half & it is the main account line being rendered completely unusabl.

Summary On an M2 Max (macOS 26.5.1, 25F80), WindowServer intermittently stops checking in with the userspace watchdog ("hung 40/80 seconds since last successful checkin") and the machine resets. The part I'm asking about: since ~2026-06-17 the wedge no longer ends in a normal panic-reboot — it escalates to recoveryOS and forces a full Mac reactivation (local password + iCloud). Four times in 55 hours. The most recent was captured live and fired on a machine that was idle, memory-clean (1.2 GB free, flat swap, no Jetsam), with the underlying IOKit power-assertion count plateaued — so this is not resource exhaustion at the moment of the wedge. It reproduces under a heavy third-party workload (an Electron app's per-session process fan-out, tracked separately by the vendor). I'm not asking Apple to fix that app — I'm asking about the OS behaviors that turn "an app uses a lot over many hours" into "the owner is locked out pending iCloud reactivation." Apple-side vs app-side (so this isn't dismissed as a third-party issue) Apple's — and these should hold regardless of any app, because no userspace workload should be able to cause them: A userspace WindowServer watchdog timeout escalating to a firmware/recoveryOS reset that invalidates the boot policy and demands iCloud reactivation. On disk, the four 06-18→06-20 events have the WindowServer watchdog .spin/.ips but no panic-full and no ResetCounter — they did not take the normal panic-reboot path. The watchdog resetting the whole machine instead of restarting the wedged compositor ("WindowServer has not exited since first loaded"). WindowServer/SkyLight degrading cumulatively under sustained use so the wedge fires even when the machine is currently idle and memory-clean (below). IOKit never reclaiming RootDomainUserClient (IOPMrootDomain) registrations — they accumulate unbounded and clear only on reboot, and the dominant holders are Apple's own daemons (apsd, WebThumbnailExtension), not the app. App-side (separate tracker): unbounded per-session MCP process fan-out + an Electron footprint + a held NoIdleSleep assertion forcing sustained display-on operation. That controls how fast you reach the degraded state; the OS controls whether reaching it is a graceful degrade or an owner-lockout. Event 4 shows the OS failure with no resource exhaustion present at all. System MacBook Pro 14" (Mac14,5), M2 Max (T6020), 38-core GPU, 32 GB — a high-end, fully capable machine I had essentially never needed to reboot before this; it now forces a reactivation roughly once per day of use. macOS 26.5.1 (25F80), kernel xnu-12377.121.6~2 (Darwin 25.5.0). FileVault on, no third-party kexts, 161 GB free disk. Same kernel build as 25F71 — the update didn't change it. Signature userspace watchdog timeout: no successful checkins from WindowServer (0 induced crashes) in 120 seconds WindowServer has not exited since first loaded service: logd / opendirectoryd / configd — last checkin: 0 seconds ago service: WindowServer — last checkin: 120 seconds ago Panicked task ... watchdogd; KEXT backtrace: AppleARMWatchdogTimer -> AppleARMPlatform Compressor Info: NN% (OK) ... 0 swapfiles <-- memory-clean Only WindowServer is stuck; logd/opendirectoryd/configd check in normally. Pre-reset spindumps show ws_main_thread off-CPU ~59 s, wedged in SkyLight → QuartzCore CA::Transaction::commit / CALayer render-commit. Two spindumps per event (the 40 s/80 s checkpoints before the 120 s reset). Timeline & the escalation point (verifiable on disk by panic-full/ResetCounter presence) Normal panic-reboots (panic-full + ResetCounter written): 06-15 22:24 (~6.2 h uptime), 06-16 11:39 (~13.2 h), plus 06-14 / 06-15 16:07 / 06-16 20:08. Latest panic-full on disk = 06-16 20:08. Escalated to recoveryOS reactivation (NO panic-full, NO ResetCounter): # When WindowServer uptime at wedge state R1 06-18 01:23 ~27.6 h (99,278 s) R2 06-18 19:53 ~18.4 h (66,201 s) + Jetsam pressure R3 06-19 15:30 ~19.2 h (68,991 s) R4 06-20 08:19 ~16.7 h (60,180 s) idle, 1.2 GB free, leak plateaued 583 Uptime = WindowServer-process uptime from the .ips "M checkins since K seconds ago" field (the coarse uptime JSON field — 99000/66000/69000/60000 — corroborates). Time-to-wedge is not a fixed interval — it ranges ~6–28 h and scales inversely with GPU/compositor load; the invariant is sustained use, not a clock value. After 06-16 there are zero panic-full and zero ResetCounter on disk — the fingerprint of the recoveryOS escalation. Decisive evidence — R4, captured live A monitor sampling every 2.5 min when WindowServer wedged (08:19, 16.7 h): 08:14 iopm=581 free=1833MB swap=3732MB load=2.88 08:19 iopm=583 free=1192MB swap=3724MB load=3.03 <-- watchdog spindump written Idle (load ~3), 1.2 GB free, flat swap, no Jetsam, the IOKit power-assertion count plateaued at 583. Nothing to exhaust — it still wedged and escalated to reactivation. The trigger is cumulative WindowServer/SkyLight state, not the resource level. The leak (an aggravator) RootDomainUserClient/IOPMrootDomain clients climb without bound (baseline ~120 → 583–923 here). Dominant holders are Apple daemons (live ioreg walk 2 min pre-panic: apsd 228/596, then Safari/WindowServer/powerd/loginwindow). Killing the top creating process does not reclaim them (ioclasscount 526→526) — kernel-orphaned, reboot-only. Per R4 the leak is an aggravator, not the threshold (583 wedged; 923 had not earlier). Ruled out Hardware (survived 25F71→25F80, same kernel; peripheral + driver removal); memory exhaustion (R4 and others memory-clean); a fixed clock (load-dependent, 6–28 h); an iopm threshold (R4 plateaued at 583). Questions for Apple engineering Why does a userspace WindowServer watchdog timeout escalate to recoveryOS + forced reactivation (boot-policy re-verification) instead of a normal panic-reboot? What invalidates LocalPolicy / triggers Activation-Lock re-verification on this path? What in WindowServer/SkyLight degrades cumulatively over sustained use so a render-commit can't complete within the watchdog window even on an idle, memory-clean machine? Can the watchdog restart the wedged WindowServer ("has not exited since first loaded") instead of resetting the whole machine into a reactivation lockout? Can IOKit lifecycle-bound RootDomainUserClient (IOPMrootDomain) registrations so they don't accumulate unreclaimable? Dominant creators are Apple daemons (apsd, WebThumbnailExtension). Apple Feedback FB22947849 has the per-event spindumps, .ips, the live monitor log, and a sysdiagnose. I'd most appreciate a pointer on #1 — the reactivation escalation is what turns a recoverable crash into a repeated owner-lockout.