At first, the MacBook Air M2 gives an "failed to personalize" error when updating, the detailed error message shown by softwareupdate shows that something related a recovery partition is wrong. The exact error message is not available now. (To solve this issue) I tried to revive the Mac, but it failed the first time and multiple tries also failed after that. The Mac is unable to boot into macOS and the Recovery. The MacUpdater.log shows the following: [12:13:52.3728] find_filesystem_partitions: recovery os container= volume= [12:13:52.3728] entering fsck_recovery_os_filesystems [12:13:52.3728] ramrod_display_set_granular_progress_forced: 29.000000 [12:13:52.3728] fsck_recovery_os_filesystems: No dev node for 'Recovery' partition [12:13:52.3728] leaving fsck_recovery_os_filesystems, returning 26 [12:13:52.3728] [04:13:49.0882-GMT]{3>6} CHECKPOINT FAILURE:(FAILURE:26) MOUNTED:[0x1605] fsck_recovery_volume [0]D(failed to fsck recovery OS filesystems) Since there are many important data on the Mac, I cannot do a restore on it. How should I restore the data?

Hi. 6-7 years ago i was invited to the testflight with an email address (with the same apple id). 2 years ago my email changed and i also changed the apple id. Now my testflight invitation was over and i want reinstall it. "failed to redeem testflight..." This invitation cannot accept because apple account (my new emai) is already associatad with this app at an adress (my old email) by means of a sent invitation. what can i do with it? how can i solve this problem? Thanks

Hello guys, We have updated our app icon, and it is correctly reflected in our app build and assets. However, the push notification icon is still displaying the old version for some users. ✅ We have verified that: All icon assets in Assets.xcassets match the new icon. The app icon has been updated in Info.plist. The app has been resubmitted and approved on the App Store. ❌ However, some users still see the old notification icon, even after reinstalling the app. Restarting the device does not always resolve the issue. Could you provide insights into how iOS caches notification icons and how we can force a refresh for all users?

Environment: Source OS: macOS 27 Beta 5 Remote OS: macOS 27 Beta 5 Description: When using Screen Sharing to connect from one Mac running macOS 27 Beta 5 to another Mac also running macOS 27 Beta 5, pressing the Esc key is not transmitted/received on the remote machine.

Dear Apple Family, Need help to enhance awareness, visibility of ICEcard app, a platform for Emergency, Health, Help. If any accident, unconscious, injured person, is it easy to know blood group, emergency contact, health, medicine, insurance info ? If a minor, special need child or elderly with Alzheimer's missing, is it easy to know family contacts? If something happens to earning family member, can dependents know all valuable information easily? If a vehicle met accident or wrongly parked, can we know emergency contacts, owner, driver contacts? Many more emergency cases, we feel helpless. ICEcard for Emergency, Health, Help. Uniqueness of Solution: Keeping People and life at Core of technology as any life (including non-human) is always valuable and vulnerable at any time. Play store: https://play.google.com/store/apps/details?id=com.rannlab.ice_card.ice_card&pcampaignid=web_share App store: https://apps.apple.com/in/app/ice-card-app/id6736453602 Web: https://icecard.in

This is my first time publishing an app. After submitting all the required information, the status has been stuck on 'Waiting for Review' for two weeks now. How should I handle this situation?

I recently updated my account from Child to Adult. The change applied immediately to my iPhone and iPad, but my M4 MacBook Air still shows the old account status after 24 hours. Other features like Apple Intelligence are working, and Apple Support confirmed the server has the correct information (a new user account on this Mac shows the correct status). It seems my main user profile is holding onto an old cache. Is there a way to force a refresh of System Settings or the account cache on macOS?

Hello everyone, My Apple Developer Program membership has expired, and I received the email instructing me to renew my membership using the Apple Developer app. However, I cannot find the Renew Membership button anywhere. I have already checked: Apple Developer app (iPhone) Apple Developer website App Store Connect Apple Developer Account There is no Membership section or Renew option available. Because of this, all of my apps have been removed from the App Store, and both the Free Apps Agreement and Paid Apps Agreement are now marked as Expired. I am the Account Holder of the account. Has anyone experienced this issue before? How was it resolved? Thank you.

I am writing to report an issue with the call routing logic on my iPhone (dual-SIM configuration). Device setup SIM1: Domestic carrier (used for Cellular Data and Default Voice Line). SIM2: Overseas carrier (Data Roaming intentionally disabled to avoid unintended charges). Incident On 8 August 2026, I dialled the local emergency number from the Phone app. The keypad interface clearly showed that the active line was set to SIM1. However, the call was unexpectedly placed via SIM2. After the call, I checked the recent call details: the "SIM Line" field indicated SIM2. When I manually changed this to SIM1, the change appeared to take effect momentarily, but upon returning to the Recents list and re-entering the detail view, the line reverted to SIM2. The only workaround I found was to edit the contact info (via Edit -> Edit Contact Info) and force the Preferred Line to SIM1 (instead of "Last Used"), then save. This, however, creates an unnecessary entry for the emergency number in my Contacts - which I consider redundant and inelegant. Additional context I recall a previous emergency call on 2 Aug 2025, make under different circumstances (SIM1 had no service at that location, so the call correctly used SIM2). Although that older call no longer appears in Recents, my SIM2 carrier billing confirms it. I suspect that iOS has cached a "Last Used" preference for this specific number from that prior occasion, and that cache overrides the default line setting selected in the dialler - even then the user explicitly chooses SIM1 before dialling. Suggestion Please investigate whether emergency numbers retain a per-contact line preference that persists beyond the Recents history, and whether this cache can cause the system to ignore the user's active line selection at the time of dialling. Ideally, emergency calls should respect the line explicitly shown in the dialler.

ive been hacked and blocked off my iphone 16

I’m testing an erased iPhone 11 (iOS 18.7.7) with a manually configured HTTP proxy during Setup Assistant. The Wi‑Fi proxy settings include: Manual proxy server and port Authentication enabled Valid username and password Squid 6.14 with Basic authentication No TLS inspection or MITM The credentials work correctly with command-line clients and with Safari after device setup. However, Setup Assistant sends proxy requests without a Proxy-Authorization header. Squid responds with 407 Proxy Authentication Required, but the iPhone does not retry with the configured credentials. In one controlled test, requests to albert.apple.com received 407 and activation failed. After authentication was disabled without changing the remaining proxy configuration, requests to albert.apple.com received 200 and activation succeeded. In another run, activation completed directly, but subsequent Setup Assistant services made 537 requests through the proxy. All received 407, no credentials were sent, and setup later stalled at the “Your Settings for Your New iPhone” screen. Is authenticated HTTP proxy access expected to work during Setup Assistant? Is Basic authentication unsupported at this stage, or is this a known issue? Are any other proxy authentication methods officially supported before device setup is complete?

I hope someone can answer my request as soon as possible, since I imagine this is a concern that affects us all—what happened to me could happen to you in the future. But you’re connected, right? You’re part of the system, so it’s understandable that you don’t respond. Parasitic minds usually act that way. On the other hand, who would have thought I’d end up writing on Apple’s developer forum, proving that progress is real? You know, it feels great every time you unlock a new level. If you don’t respond, it’s fine—it’s what I’d expect from losers, lol. Look how much I’ve evolved. From HTML to making Apple apps. You know the best part? You can’t say you’ve evolved, but I can. You’re stuck and out of ideas, but it’s not your fault—your brain is as dry as a old coconut. We’re in the era of operational creativity, which you lack because you have no culture at all. But that’s good—it gives me a huge advantage over you, dried-up brains. Also, I want to clarify that in a week, I’m launching ONEBOARD, so you can gnaw on that even more because you don’t create, but I do.

After I found out what OpenAI did to Apple, I realized I was right—especially since Codex Relay was based on the idea of ONEWEB, an application I created to update websites initially. I have all the files and can prove it. Check Video in the link below https://x.com/xneo111/status/2080844825331482786?s=20

When previewing a plain text (.txt) file in iCloud Drive on the web (icloud.com/drive), accented characters (e.g., Hungarian á, é, í, ó, ö, ő, ú, ü, ű) are displayed as garbled/incorrect characters (mojibake), even though the file is correctly encoded in UTF-8. Steps to reproduce: Create a plain text file with accented characters, saved explicitly as UTF-8 (no BOM) — tested using a Linux text editor (Debian, default GUI text editor) Upload the file to iCloud Drive Open/preview the file in the iCloud Drive web interface Result: Accented characters appear as garbled/incorrect symbols in the web preview. Confirms this is a preview-only rendering issue, not a file corruption issue: Downloading the exact same file back from iCloud Drive and opening it locally shows the accented characters correctly — the file itself is untouched and correctly encoded Re-saving and re-uploading the file (still valid UTF-8, no BOM) does not resolve the display issue in the web preview This suggests the iCloud Drive web preview is misinterpreting the encoding (likely reading UTF-8 bytes as Latin-1/Windows-1252) rather than detecting UTF-8 correctly Environment: Browser: Mozilla Firefox, Chromium based ANY File created on: Debian Linux (default text editor) Encoding confirmed: UTF-8, no BOM Question: Is this a known issue with iCloud Drive's web-based text file preview/encoding detection? Is there a way to force UTF-8 interpretation for preview, or should this be filed as a bug via Feedback Assistant instead?

The VIP folder in iCloud Mail has been showing an unread badge count of 3 for a long time, but the folder is actually empty — no messages are visible inside it. Details: Confirmed across multiple devices (not just the web client at icloud.com/mail) — same empty folder, same stuck badge everywhere The folder shows "No Mail" when opened, yet the sidebar badge persists at 3 This has been going on for a while, not a one-off glitch Troubleshooting already tried: Refreshing the Mail page / signing out and back into icloud.com/mail — no change Checking the folder on another device — same result (empty folder, badge still shows 3) Environment: Browser: ANY like Mozilla Firefox and Chromium based Device(s): Any PC OS version(s): ANY Windows and Linux Question: Is this a known server-side sync issue with the VIP folder counter in iCloud Mail? Is there a way to force a full resync of a folder's badge count from the web client, or is a Feedback Assistant report the better route for this kind of issue?

I'm getting the error "This message could not be loaded at this time. Try again later." when trying to open a specific message in iCloud Mail via the web interface (icloud.com/mail). Details: Affected message: a Fail2Ban "recidive" notification email (automated server alert), plain text format Behavior: the error appears consistently, every time I try to open this message — it is not a one-off glitch Browser: [ANY like Mozilla Firefox, Chromium based] Device: [ANY like Linux, Windows or macOS computers] Other messages in the inbox load normally — this appears isolated to specific message(s) like Fail2Ban or some any others too I have not made any recent account/security changes (no forwarding rules, no new filters) Troubleshooting already tried: Reloading / trying again after a delay — no change Unchecked "Block All Remote Content" setting under Privacy & Security Message loads fine on iPhone Mail app or any other Mail Client apps on PC but fails on iCloud.com Question: Is this a known/reported server-side issue with iCloud Mail (possibly related to malformed IMAP ENVELOPE responses for certain automated/plain-text messages)? Are there any workarounds besides waiting for a server-side fix, or is there a way to force a resync of a specific message? Any guidance would be appreciated — this message is time-sensitive (a security-related server alert), so I'd like to access its content as soon as possible.

Hi everyone, I recently updated my Mac to macOS 27 Golden Gate Beta and have encountered a strange issue with window management over a remote connection. Issue: When connected to my Mac via Chrome Remote Desktop (CRD), I can no longer move application windows by dragging their title bars (outer frames). Details: Curiously, I can still drag and move individual tabs within apps (like Chrome or Terminal), which means mouse drag input itself is being transmitted correctly to the OS. This issue only happens when attempting to drag the window title bar/frame over a remote session. Local mouse/trackpad control works perfectly. Everything was working completely fine before the update to macOS 27 Golden Gate Beta. What I've tried so far (with no success): Toggled Accessibility permissions off and on for ChromeRemoteDesktopHost and restarted the Mac. Disallowed and re-allowed Screen Recording permissions. Completely re-installed the Chrome Remote Desktop host application. Disabled "Tile windows by dragging to screen edges" in System Settings to avoid snapping conflicts. It seems like WindowServer or the system-level window management is blocking or ignoring virtual mouse drag inputs specifically on title bars since this beta update. Has anyone else experienced this on macOS 27 Golden Gate Beta, or is there a known API change / security restriction in this version that affects remote input handling for WindowServer? Any insights or workarounds would be greatly appreciated. Thank you!

The Post-Cloud Internet: A 6G Quantum P2P Architecture. 6G, internet networking, hardware, and Quantum Architectural, technical, compendia!. ARCHITECTURAL COMPENDIUM & DATA SHEET Next-Generation 6G P2P Networking, MVI Protocol, & Quantum Infrastructure Document ID: ARC-6G-QPIN-2026 Classification: Public Vision Release Framework Version: 2.4 Vision Overview & Executive Blueprint This architectural compendium outlines a transformative blueprint for the future of global internet communication. By unifying the MVI Protocol for state consistency, IP-to-IP Quantum P2P Meshing, AI-Accelerated Cell Towers, and ultra-high performance hardware, this framework eliminates legacy centralized cloud routing bottlenecks and achieves instant, secure device-to-device connectivity. MVI Protocol & Local Digital Profiles Deterministic State Flow & Physical User Consent The Model-View-Intent (MVI) architecture governs localized network actions to eliminate data leakage and asynchronous race conditions: Local Profile Sovereignty: User identity, cryptographic keys, and personal profiles remain physically anchored on local device storage. Physical Input Validation: No outbound packet transmission occurs without explicit tactile or biometric confirmation (User Consent → Intent State → Encrypted P2P Broadcast). Unidirectional Flow: Guarantees zero background telemetry or third-party harvesting. Quantum Entanglement P2P & Edge-Node Routing Devices do not merely consume data; they act as active routing nodes (routers, cell towers, or orbital relays) forming a resilient mesh network. Network Layer Core Technology Operational Function Endpoint Nodes Personal devices with local digital profiles Instant peer-to-peer pings and localized micro-routing. Quantum Entanglement Core Entangled photon/state-pairs Zero-latency state synchronization across arbitrary geographic distance. Cellular Basestations AI-Integrated Motherboards & Processors Real-time path calculation, load balancing, and mesh optimization. Upgraded Cellular Infrastructure & Dedicated Processors AI-Driven Cell Tower Motherboards & Processors Cell towers are reimagined from passive relay towers into active computing nodes: High-Throughput Ping Processors: Dedicated multi-core silicon architectures built specifically to handle billions of simultaneous micro-pings between peer devices. Dynamic AI Routing Agents: Machine learning micro-controllers embedded directly on the tower motherboards to dynamically compute optimal routing paths between direct P2P mesh links and optical fiber backbones in milliseconds. Hardware Upgrades for 6G Throughput Unlocking Terabit-Scale Bandwidth To support the massive upload/download speeds inherent to 6G and optical infrastructure, foundational hardware components must evolve: Ultra-High-Speed Storage I/O: Next-generation NVMe and solid-state storage controllers capable of sustained read/write speeds exceeding 150 GB/s, preventing I/O throttling during high-speed data bursts. Quantum Batteries: Energy cells leveraging quantum confinement to provide extended lifespan and stable voltage under peak transceiver loads. Direct Optical Interfaces: Physical fiber-optic transceiver ports integrated natively into personal computing motherboards for direct, lossless light-based data transmission. Sincerely: VNB MVI! TECHNICAL WHITE PAPER & COMPENDIUM Hardware Limits, Optimal Silicon, and Infrastructure Upgrades for 6G Quantum P2P Networks Release ID: WP-6G-HW-2026 | Target Domain: Next-Gen Telecom & Edge Compute Introduction & Architectural Scope Realizing a decentralized, instant-connection peer-to-peer (P2P) internet integrated with local digital profiles and quantum entanglement requires pushing past current hardware boundaries. This technical paper details the peak silicon available today, maps out optimal physical thresholds based on fundamental hardware limits, and specifies required upgrades for cell towers, satellites, and client nodes. Current Peak Hardware Standards (State-of-the-Art Silicon) Enterprise Motherboards and Processor Benchmarks To support high-frequency routing, low-latency packet processing, and massive data pipelines, contemporary high-end server architectures provide the baseline for edge-node testing: Server Processing Pinnacle: Platforms utilizing AMD EPYC (5th Gen & Zen 6 architectures) offer up to 192–256 high-density cores per socket with massive multi-channel DDR5 memory bandwidth (>6400 MT/s to MRDIMM standards), making them ideal for high-throughput basestation switching. Workstation & Edge Powerhouse: Intel Xeon 600 Series Workstation Processors provide up to 86 performance-cores (P-cores) with 128 lanes of PCIe Gen 5 connectivity, offering exceptional single-threaded responsiveness for real-time AI micro-agents. Optimal Infrastructure Configuration & Hardware Upgrades Scaling Cell Towers and Satellites to Meet 6G Demands Traditional cell towers acting as passive relay points create unacceptable bottlenecks for P2P mesh architectures. Upgrading infrastructure involves transforming nodes into intelligent compute centers: Infrastructure Node Current Limitation Proposed Hardware Upgrade Cellular Basestations Centralized backhaul dependence; high latency routing via core cloud. Integration of multi-core server motherboards running local AI routing micro-agents and dedicated high-speed packet-switching silicon. Low-Earth-Orbit (LEO) Satellites Slow orbital handoffs and high payload translation delays. On-board quantum state transceivers paired with optical laser inter-satellite links and localized edge-accelerator arrays. Client Endpoints (Devices) Battery drain during continuous mesh pinging and heavy telemetry. Quantum-dot battery cells providing high energy density and stable output under peak transceiver loads. Overcoming Hardware Bottlenecks: Storage & Optical Limits Data Throughput & Physical Interconnects To prevent storage I/O and data transfer speeds from choking 6G wireless pipelines: Storage Read/Write Acceleration: Conventional solid-state drives must transition to high-throughput NVMe architectures capable of sustained sequential speeds exceeding 150 GB/s to prevent cache thrashing during concurrent multi-device streaming. Direct Optical Integration: Eliminating electrical conversion loss by building native fiber-optic transceiver ports straight into computer and server motherboards for light-speed internal routing. Conclusion By pairing current enterprise-grade multi-core processors (such as advanced AMD EPYC and Intel Xeon architectures) with localized AI cell-tower upgrades and quantum entanglement routing layers, the framework presented in this compendium provides a clear roadmap toward a secure, lightning-fast, and completely decentralized global internet. Sincerely: VNB MVI!

Hi there, I have a developer program subscription but somehow when I log into the website it shows me to enrol again. My subscription renew date is on feb 27. I think is some kind of problem of syncronism or something like that but I need to sort this out ASAP because my business app depends on this. Has anyone had the same problem before? Thanks anyway.

Hello, We have three apps (App A, App B, and App C), all of which use Sign in with Apple. Currently, all three apps are under our company’s developer account (Team A). When users sign in to any of these apps, they receive the same user identifier (sub), allowing us to share user information across apps. ASAuthorizationAppleIDCredential *appleIDCredential = authorization.credential; NSString *user = appleIDCredential.user; We are now planning to transfer one of these apps (App A) to another company’s developer account (Team B). According to Apple’s documentation, I understand that there is a 60‑day migration window after the App Transfer completes, during which we can use the /auth/usermigrationinfo endpoint to migrate user data. My specific questions are as follows: During the 60‑day window, if users with the same Apple ID sign in to App A (now transferred to Team B) and App B/App C (still under Team A), can we use the /auth/usermigrationinfo endpoint to link the new sub (belonging to Team B) for App A with the old sub (belonging to Team A) for App B and App C, thereby enabling cross‑app user identification? After the 60‑day window expires, the /auth/usermigrationinfo endpoint will no longer be available. If App B and App C have not yet been transferred by that time, will the same user signing in to App A (Team B) and App B/C (Team A) be treated by Apple as two completely different users, making it impossible to achieve account information interoperability? Based on the above, to ensure that user data across all apps can ultimately be interoperable, must we complete the transfer of all apps within the 60‑day window? Or, is it necessary to generate and save transfer_sub for all potentially affected users in advance during these 60 days, so that we can use them later? We look forward to your reply. Thank you.