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

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.

If you're on an Intel Mac, here's the reason and the fix. Cost me an evening, and I found nothing online except closed bug reports with the same symptom. The problem: The browser flow works fine. You authorize, the page confirms, Xcode acts like nothing happened, no error anywhere. Xcode only downloads the Apple Silicon (arm64) build of its agent binaries. On Intel they can't run at all. The process meant to receive your login dies instantly with "bad CPU type in executable" and Xcode never surfaces it. Check if this is you: file ~/Library/Developer/Xcode/CodingAssistant/Agents/claude/*/claude If it says arm64 and your Mac is Intel, that's the problem. The fix: Open the Info.plist next to the binary. It has the exact download URL. Download the x64 build of the same version. → Claude: change darwin-arm64 to darwin-x64 in that URL. → Codex: grab codex-x86_64-apple-darwin.tar.gz from the matching rust-v release on GitHub. Replace the binary and make it executable: chmod 755 Update the checksum in Info.plist. It's a plain SHA-512: shasum -a 512 Restart Xcode and sign in again. Bonus (Claude Pro / Max) Run claude setup-token in Terminal, then add the token to: ~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig/settings.json {"env": {"CLAUDE_CODE_OAUTH_TOKEN": "your-token"}} Pick "Authenticate with Configuration File" in the agent menu. Runs on your subscription no API key. Heads up: an Xcode update can re-download the wrong binary, so you may have to repeat this until Apple fixes the architecture detection.

For context, I spent my entire Monday calling apple for 2 hours each time then restarting (I got through around 4 calls before apple phone support stopped) so a total of 8 hours. Today Ive been waiting another 3 hours and still no one has picked up. Ive never had this issue before usually it's a 10-20min wait if not less but this is totally different. A Anyone else facing this issue?

Hey everyone,I’m running into a deeply frustrating structural bug with the redesigned Screen Time menus in the iOS beta, and I wanted to see if anyone else has found a workaround (or is facing the same thing).In previous iOS versions, if a site was blocked by the filter, you could hit "Allow Website," enter your code, and go on with your day. It didn't permanently log itself into your settings.In this beta, the system acts like a strict binary engine. The second you manually approve a site or click "Allow Anyway," that URL is permanently added to a list. There is no swipe-to-delete option anymore. You are completely locked into either choosing "Always Allow" or "Never Allow" for that URL. There is literally no middle ground or way to just remove it from the menu entirely.To make it worse, I have tried literally everything: disabling Screen Time, turning off tracking, and I even went as far as doing a full Reset All Settings. Guess what? The list was still there. It seems to be pulling straight from an iCloud ghost-sync loop that ignores local device overrides.Has anyone successfully forced these URLs to delete, or are we completely at the mercy of Apple patching this database design flaw in a future beta build?

I'm the legal owner of a company that has never had an Apple Developer account. When I went to enroll, I found an account already exists under my company's name. Since Apple allows only one enrollment per legal entity, I'm now blocked from enrolling my own business. I contacted Apple with proof of ownership (company registration documents and ID), and Support gave me a case/support ID. It's been three days with no response. A few details that may be relevant: The email tied to the existing enrollment is not mine. It uses a lookalike domain built from my company name that I've never owned or controlled. I believe the enrollment may be incomplete/unpaid rather than a fully active, paid account. There are no apps published under the account. My questions for anyone who's dealt with this: Is there a faster path to escalate a fraudulent enrollment specifically, versus a general support ticket? Has anyone successfully had a squatted/fraudulent organisation enrollment removed, and roughly how long did it take? Is phone/callback support more effective than email for this, in your experience? Any pointers appreciated. Happy to provide documentation to Apple through the proper channel.

Hi everyone, I’m trying to enroll in the Apple Developer Program using the Apple Developer app on my MacBook. Originally, my enrollment became stuck before the payment step. Apple Developer Support withdrew my previous enrollment and confirmed that I could enroll again through the Developer app. The app now correctly shows “Enroll Now”, but when I click it, it immediately displays: “Unable to Continue. Contact support.” The error appears immediately, and the enrollment flow never starts—I don’t reach the terms, identity verification, or payment screens. I’ve already: Updated to the latest macOS. Installed the latest Apple Developer app. Verified that iCloud is enabled. Confirmed I’m using the same Apple ID everywhere (I only have one Apple ID). Restarted my Mac and signed out/in again. Tried different internet connections. Apple Developer Support has already reset my enrollment once, but the issue still persists. I’ve also replied to my support case with screenshots showing the problem. Has anyone experienced this after an enrollment reset? If so, what resolved it? Any advice would be greatly appreciated. Thank you!

Je recherche un developpeur pour créer une app sur Vision Pro utilisant les fonctionnalités lidar et IMU pour procéder à des relevés de dimensions.

Hi, which devices and operating systems (if any) support the extended messages from USB PD (section 6.5 from the USB PD spec)? I want to read the device SOC using the Battery Status Data Object. This is an optional part of the spec. Do Apple devices support this? Thanks in advance, Antonin Dospiva

That is not exactly a development issue, but more a Mac configuration (which may hide other problems ?). I use a new MacBookAir with MacOS 26. When I Airdrop from another Mac (15.7.8) the MacBookAir does not show any icon but a blank area, whilst other devices show their icons: That seems an old issue with MacBookAir: https://www.reddit.com/r/macbookair/comments/1benu4o/blank_airdrop_icon/ Beside this, Airdrop works OK. Just as if the MacBookAir icon was missing in some system file ? Has anyone a solution ? I filed a bug report FB24034384

Is iOS 27 Public Beta or iOS 27 Developer Beta is good to update to or better still wait for apple normal iOS update to release ????????

Hello, I am experiencing an unexpected reboot on my iPhone while it is idle and locked. Device information Device: iPhone 17 Pro Max Model identifier: iPhone18,2 iOS version: iOS 27 Beta 4 Build: 24A5390f The issue occurred while the phone was locked and not actively being used. The device entered sleep, briefly woke, and then restarted. The panic log confirms that the device was locked at the time of the crash. The main panic string is: GFX crash of unknown type 0x80a Exception class=0x2f (SError interrupt) agx_scheduler(2) The panic initiator is also listed as: panicInitiator: GFX This appears to be related to the GPU or graphics subsystem, possibly during a display sleep/wake or lock-screen transition. I have already tried the following: Disabled Always-On Display Disabled StandBy mode Changed the Lock Screen to a static wallpaper without motion or depth effects Removed Lock Screen widgets Disabled Live Activities Disabled Raise to Wake Disabled Tap to Wake Enabled Reduce Motion Enabled Limit Frame Rate Restarted the device The problem does not appear to be caused by low storage or thermal pressure. The device had sufficient free storage, and the panic report showed no thermal pressure at the time. I also found reports from other users describing the same panic string, particularly: GFX crash of unknown type 0x80a agx_scheduler(2) Some users reported that the issue continued even after restoring the device and setting it up as a new iPhone without restoring a backup. Has anyone else encountered this exact GFX panic on iOS 27 Beta 4? Is this believed to be a software regression in the GPU driver or display sleep/wake handling, or could it indicate a hardware issue? I have submitted the panic log through Feedback Assistant as well. Thank you.

Hello everyone, just wanted to introduce myself. I'm new around here. I actually used to work for Apple back in the day, now getting into Swift Development. Hoping to push out my first app in just a few weeks called "Weather Experience." First iteration is just a basic app but heavily going to be utilizing the features of iOS 27 to deliver a special weather experience in late September.

Hello everyone, I am reaching out to the community because I have been unable to enroll in the Apple Developer Program as an individual and have exhausted the standard support channels. The Situation: When I attempted to enroll, I received an email from Apple Developer Support stating that my enrollment could not be completed for "one or more reasons," and that they are unable to proceed with my registration. The email did not provide any specific explanation for the rejection. My case number is 20000127737965. What I Have Done So Far: I have replied to the support email, expressing my willingness to provide any necessary documentation, including: A photo of my personal ID for identity verification. A Certificate of No Criminal Convictions. A clear explanation of my development purpose (to publish my app, "dumpany," a desktop document-downloading tool). I have asked for the case to be escalated for a manual review. I have confirmed that all my personal information, including my legal name and payment method, matches the details on my Apple ID. My Question to the Community: Has anyone else experienced a similar issue where the enrollment was rejected without a clear explanation? If so, were you able to resolve it, and if yes, how? I am willing to correct whatever the issue is; I just need to understand what it is. Any guidance or insights from those who have navigated this would be greatly appreciated. Thank you for your time.

Device: iPhone 17 iOS Version: Latest public release Steps to Reproduce: Receive an SMS from India Post containing a tracking number (e.g. EU714545174IN). Long-press the tracking number. Select Track Shipment. Expected Result: The shipment should be tracked using India Post or the correct carrier. Actual Result: iOS opens an in-app Safari page for DTDC with an invalid tracking URL. The shipment cannot be tracked because the tracking number belongs to India Post, not DTDC. Additional Information: Tapping the India Post website link in the SMS works correctly. Only the built-in Track Shipment action misidentifies the carrier.

Please help me on this error. i'm not sure that i'm missing.

I’m developing an app (well, Claude Code is doing the Swift work) that has a need to send SMS messages on a regular basis. It’s an app that sends location information to a third party, via SMS, in case the user goes missing. Claude is telling me that the user has to hit send for every message. Claude also says there’s no way for the app to know if a message was successfully sent. It only knows that it was queued in Messenger but not that it was actually successful in sending. In the Android port we don’t have those restriction, apparently. The Android app can send messages without the users involvement (after granting permission ahead of time). The Android app can also query as to whether the send was successful, and optionally retry the send when it wasn’t. The advantage of not having the user needing to hit send ’Send’ and being able to determine if the queued send was successfully sent is an increase in reliable location information being received by the recipient. My questions are whether Claude Code is correct in what iOS allows, and if there’s an alternate approach. I understand the security concern with sending messages the user didn’t explicitly approve for each message but I’m wondering if Apple is considering an implementation mechanism that approaches Android (ie: approve message sending without per-message authorization) and the ability to check if a queued message was successfully sent. Thanks.