Bluetooth does not show device options, whereas wifi shows the wifi options in control center.

When I tried to use Xcode to compile an app for my iPhone, it also compiled a macOS version, but they don't work. I tried to delete them from the Applications folder, but they're not there. According to the Xcode logs, I found that they're located in /private/var/folders/ and there are some deprecated projects. How should I delete them?

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

A brand-new MacBook Pro (M5 Pro, 24GB RAM) is experiencing frequent, severe kernel panics. The system freezes completely for a few seconds before executing an automatic reboot or shutdown. This behavior occurs roughly 10+ times per day, significantly disrupting production work. The issue initially triggered immediately after migrating data from a base M4 MacBook Pro via Migration Assistant. Steps Taken & Troubleshooting Hardware Diagnostics: Ran Apple Diagnostics locally; all hardware checks passed with no errors detected. OS Updates: Installed the minor macOS patch intended to resolve M5 automatic reboot bugs. The issue persisted. System Erase: Performed a complete factory reset ("Erase All Content and Settings") and a clean OS reinstallation as advised by Apple Support. Beta Testing: Upgraded to the macOS Tahoe Beta following guidance from a DST Engineer who indicated the issue was addressed in this build. The frequent crashes continue to occur on the beta track. Case / Feedback Reference Feedback ID: FB23273513 (Captured after the system format)

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?

Hello everyone, I recently enrolled in the Apple Developer Program as an Individual developer, and my enrollment is still being processed. My enrollment was submitted on June 17, 2026, and I currently have an open support case (102921992970) with Apple Developer Support. Unlike some payment-related issues discussed here, I have not been charged yet, and no payment has been processed from my card. My enrollment simply remains in a pending/processing state. At the moment, I have not received any requests for additional information or documentation. My support case remains open, but I have not yet received an update regarding the status of the review. I wanted to ask if anyone else has experienced a similar delay recently. How long did your enrollment take to be approved? Were you contacted for additional verification? Is it normal for enrollment review to take more than a few business days before payment is processed? Any insights or experiences would be greatly appreciated. Thank you. Kind regards, Famous Macaulay

How control camera Zoom in and Zoom out from external remote by sending HID

Hi all, Hoping someone has hit and resolved this exact pattern, or can point me to the right escalation path. I'm trying to enrol in the Apple Developer Program as an Individual (Bengaluru, India). The Apple Developer iOS app shows "ID Verification Rejected" under the Apple Developer Program status — but with no specific reason and no retry button. The app does not surface what was actually wrong with the verification. What I have already done: Confirmed my Apple Account name ("Adarsh P S") exactly matches my Passport and PAN card (no extra spaces, correct initials). Opened Developer Support case #102900128848 — the agent replied once on 2026-05-28 asking for a screenshot, which I provided the same day. No follow-up in 3+ business days. Filed a parallel case #102905434551 on 2026-06-02 explicitly referencing the first as escalation, not a duplicate. Apple ID has 2FA enabled, trusted device active, billing address on file. Questions for anyone who has gotten past this: Did the verification reset come from support, or did re-attempting from the app after some delay work on its own? For Indian developers — which ID type was finally accepted (Passport vs PAN)? I understand Aadhaar is not accepted per UIDAI restriction. Is there a specific support topic / contact path that routes to the identity-verification team faster than "Membership and Account → Program Enrolment → Email"? Any pointers appreciated — my iOS 26 / SwiftUI app is built, tested, CI-green, and waiting only on enrolment. Thanks, Adarsh P S

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

Hello Developers, I'm wondering if anyone of you knows if swift student challenge apps are evaluated on real device or on a simulator ? Actually, I'm working on an app which requires iPad Taptic Engine, and I don't wanna restart it from scratch a week before submissions cause I'll learn the evaluations are on a simulator. So, if anyone can explain me how apps are evaluated, that would be great. Thank you!!

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.