before this post I posted this question in Apple Support Community. I do not know this is about some part of beta. but I need to know have some way to change them in beta. My Macbook internal keyboard is ANSI Layout but in Keyboard setting input sources with beta is show the ISO layout. so I need to type `(backtick) but it show "§" instead. how to change keyboard type ISO to ANSI ?

I just downloaded ios 26 atm i was upgrading my phone battery was 50% and charging , now when i fully installated ios 26 it shows battery 1% and even i try to charge it still stays at 1% any idea how to fix it

Hi everyone, Since updating my iPhone 13 Pro to iOS 26, the device stopped charging and is not recognized by my Mac when connected via USB-C to Lightning cable. I’ve run extensive diagnostics: • Tried multiple USB-C cables and ports on the Mac — all work with other iPhones and devices. • The iPhone charges fine using a wall charger. • It also works perfectly with USB-A to Lightning cables — charges and appears in Finder. • I performed a full DFU restore and downgrade to iOS 18, without restoring from backup — the issue persists. • Interestingly, the iPhone is detected by the Mac in DFU mode via USB-C, which suggests the USB-C port is physically fine. This leads me to believe the issue is with the USB-C stack in normal iOS runtime, possibly triggered or corrupted by the iOS 26 update. It’s not hardware-related, as data and power lines work in DFU, and USB-A connections work normally. Has anyone else experienced this? Is there any way to fully reset or reflash the USB-C firmware at a lower level than DFU? Or does this require AST2-level diagnostics from Apple? Thanks in advance!

I’m running macOS 26 Beta 1 (build 25A5279m) on a 2019 Mac Pro (MacPro7,1) with a single 4K display connected via HDMI. Whenever I attempt to launch Finder, WindowServer immediately aborts and the machine reboots. Crash details: Process: WindowServer (PID 1441) Exception: EXC_CRASH (SIGABRT) triggered in thread 0 (ws_main_thread) Termination Reason: Abort trap: 6 Backtrace highlights: CA::OGL::MetalContext::draw(MTLPrimitiveType, …) hits an internal __assert_rtn in libsystem_c.dylib Subsequent calls all stem from QuartzCore’s OpenGL/Metal bridge (CA::OGL::render_layers, LayerNode::apply, etc.) Related threads: Thread 2 (com.apple.coreanimation.render-server) idle in mach_msg_overwrite Thread 1 shows AmbientDisplay and ColorSync callbacks running Hardware/Software: MacPro7,1 (2019) macOS 26.0 Beta 1 (25A5279m) 4K monitor via HDMI System Integrity Protection enabled What I’ve tried so far: Safe-boot (crash still occurs) Switching display profiles in System Settings → Displays → Color (no effect) Happy to provide any additional logs or verbose console output. Let me know if there’s any other data that would help diagnose the Metal/OpenGL integration issue in this beta.

Anyone have a code for testflight? Pls i would really like to use this app, some developer?

Unable to select the desired build in App Store Connect; clicking on the build has no effect. Steps to reproduce: 1.I select my app 2.I choose which build to add 3.I try to select the build Expected result: I should be able to select the build Actual result: Nothing happens Browsers Tested: Google Chrome (both PC and mobile), safari mobile Supporting Video: https://www.loom.com/share/cd9c831920fb43518ef461c9a697f09f?sid=9ce60f81-0a7c-44f4-b88a-74dcc9820e14, https://drive.google.com/file/d/1PJEixy8IpFTEEDLjBMQjV-b9U8zUM2S0/view?usp=sharing Screenshots: https://gyazo.com/e390a5ddaa142ac9e5cbb2a6757abee8, https://gyazo.com/08ac242fbfd61d375766da04f7eb209c

Is it normal to wait a month and a half with no resolution to an account issue? I paid for a membership years ago and never used it. Recently, I've wanted to get a developer account again but there is a problem when I try to Enroll. It tells me "You cannot enroll at this time". I created a support ticket and have been checking in every couple weeks. They just keep saying they haven't heard anything. The lack of support is dissappointing.

Hi everyone, I updated my iPhone 16 Pro to iOS 26 beta and my Apple Watch to watchOS 26 beta because I wanted to test out the new features. After a few days of testing, I found the iOS 26 beta too unstable and laggy for daily use, so I downgraded my iPhone back to iOS 18.5 stable. Now my Apple Watch is still running watchOS 26 beta. I tried resetting it to factory settings, hoping that would help, but now I can’t pair it back to my iPhone because it requires iOS 26 again — which I don’t want to reinstall and don't want to use it till it's stable. Is there any way to downgrade my Apple Watch back to a stable version or somehow pair it again with my iPhone running iOS 18.5? Thanks in advance for any help!

I use other computer ssh to the mac, but return connection reset. I can't solve this problem.

Running Mac0S 26 beta 2 and now 3 on a M3 MBP and Apple mail will not connect ti IMAP. SMTP is connected. Error in Connection Details: READ Jul 07 17:33:36.456 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:p71-imap.mail.me.com -- port:993 -- socket:0x9b9e586c0 -- thread:0x9ba6b27c0 4.18 NO [AUTHENTICATIONFAILED] Authentication Failed Google Mail connects with no issues. Mail is enabled in System Settings>iCloue>Internet Accounts

Hello, The icloud main account with our app was closed for some reason we don't know why. We are unable to take action because we cannot accept current apple policies. We are unable to change the app's main account, and we have not been able to find out how to do this from Apple Turkey Support. How can we solve this problem?

I am using Angular version 14

My airpods seem to disconnect during phone calls but work fine when i hang up. Ive tried restarting them and disconnecting and reconnecting them. I’ve disconnected all other bluetooth options. Any help would be appreciate.

Hello all, We are in the process of deploying EAP-TLS Wi-Fi authentication across our corporate environment for both Windows and macOS devices. All endpoints are managed via Workspace ONE. As part of our macOS configuration, we are pushing device certificates to the login keychain of managed MacBooks. For testing purposes, we have explicitly set the Access Control List (ACL) of the associated private key to allow all applications access. This includes: eapolclient, which handles the EAP-TLS handshake for Wi-Fi panGPS, which is responsible for establishing the GlobalProtect VPN connection (we are using certificate-based authentication with pre-logon enabled) Additionally, we have configured and deployed a Wi-Fi profile via Workspace ONE to prevent users from having to manually select their device certificate - basically the identity preference card in Keychain Access. Despite these settings, we are still encountering Keychain Access prompts when eapolclient attempts to access the private key. This happens even though the key is configured to allow all applications access. This behavior is unexpected, and we’re trying to understand why these prompts persist. Has anyone encountered similar behavior on macOS, or is there something we're missing in terms of permissions or keychain configuration that could be causing this? We would greatly appreciate any insight or guidance. Thank you, Kyo

Hey, I cant can update or downgrade to a newer Version like IOS18.5 Can someone help me? And will Apple fix that?

Dear Apple: After upgrading to version 26 of the iPhone, when broadcasting using the local name, the iPhone 15 Pro Max was truncated to iPhone 15 Pro Ma with a type of 08 (shortened), but the overall length of the broadcast did not exceed 31 bytes

In my setup, the largest external display is Primary, and that's where I do most of my work. The other two external monitors are smaller, and far enough away that I can't use them for viewing text. However, when I open a new Finder window (e.g. cmd-N), it often opens on one of the non-Primary displays, which means I need to drag it to the Primary. What is the algorithm used by the Finder to decide where new windows are placed? I would like to specify that all new Finder windows should open on the Primary display.

Hey there, Just writing here to say how I do enjoy the latest update, but I can’t seem to run it on my iPhone 14 Pro well because it tends to overheat. i can deal with the stuttering issues and app crashes, that’s understandable, but for some reason the hardware seem to really heat up after normal use (scrolling on social media platforms). oh also, I do think rolling back your phone‘s software should be a simpler process as well. It’s not impossible, but the demand of a computer in reinstating a previous backup when iCloud backups your device through WiFi seems like a missed opportunity. Okay. Thank you for reading.

In e-sim after before some time not richeble the internet it was the big issue for me

There seems to be a broken USB sync and Finder recognition issue. Is there a fix to this?