I know this may not seem like the most important feature, but hear me out... I've been using Apple TV on a standard 1080p TV for years and it was GREAT. Recently, I purchased a higher-end 4K television, and when I plugged in my Apple TV - surprise! I was greeted with a somewhat laggy UI due to input delay. After playing with settings and doing a ton of research, I found that it's because of my TV's video processing features. When I switch from the default content type to my TV's Game Mode, the UI feels like a true Apple product again - crisp transitions and the input lag is basically gone. Here's the annoying part: when I start watching video content, it switches to the corresponding content type and everything looks perfect. But when I go back to the menus, it reverts to the default mode with all the lag. So I'm constantly having to manually switch modes! Adding ALLM (Auto Low Latency Mode) would fix this problem completely. The best part? It's backwards compatible with HDMI 2.0, so it seems like such a small thing to add that would seriously elevate the user experience. I would at least love it if apple gave users this option we can toggle in the settings. Any way we can get this? I made a community post here not sure best place to post

Has anyone else had any issued with their CarPlay with the new phone? My screen gets distorted and you cannot make up anything that shows up on it, it's specific to the new phone since I have also tried it with an iPhone 15 Pro and iPhone 13. I have updated my car's firmware, reset it, reset my phone settings (per Apple's request) and nothing seems to be working, and unfortunately since I'm on the beta they are limited with the assistance they are able to provide to me.

Hey there, I recently updated my iPhone to the iOS 26 developers beta version, and I’m encountering an issue on the Software Update page. It says “Unable to check for updates,” and I’m unable to revert to iOS 18. Is this a temporary problem? Will I be able to update my iPhone in the future without needing to reset it? Thanks

As developers of an app with a free basic version and a paid premium version, we recently received a malicious review on our premium app. The review falsely accused our app of being a scam and baselessly claimed it was error-ridden. This comment is clearly malicious and designed to dissuade other users from purchasing our app. The most critical point is that we haven’t had any sales records in that region recently. In response to this review, we promptly contacted Apple Support but received only a generic, templated response stating that no action would be taken. We followed up with another complaint about the review, but it was still dismissed. Apple Support provided a link to their guidelines, and within those guidelines, we found specific clauses that Apple should act upon in cases like this. We sent another email pointing this out, but we’ve received no response since. It feels like developers are left defenseless against such malicious reviews. When we face these attacks, there’s no fair judgment, and Apple doesn’t uphold the very policies it has set to protect developers’ rights. If this continues, how can developers trust this platform to safeguard their basic interests?

HAVE ANY ONE EXPERIENCE PASS KEY DEVICE PROMPTS RANDOMLY ON BETA IOS SOFTWARE >?

Anyone else's phone die after installed iOS 26 beta? I'm not happy at all. shows that my phone is charging but will not turn on. have tried hard resetting it 50+ times, 5 different chargers.. nothing.

I tried to enroll some weeks ago, went thru the whole process, it eventually took by IDs, but now I'm stuck on "Enrollement not completed - You enrollment in the Apple Developper pogram could not be completed at this time." So, after 2 weeks, what's next ?

We are currently facing an issue with implementing "Sign in with Apple" in our iOS application built using Flutter. We've implemented "Sign in with Apple" using Firebase and On attempting to sign in, we are encountering the following error: “Sign-up not completed.” We have verified that: The Apple Sign is enabled on our Firebase Project. The Sign in with Apple capability is enabled in the Xcode project. The Apple Sign-In capability is enabled for the App ID on our Apple Developer account. All the certificates were re-provisioned after enabling the capability. The Bundle ID matches across Apple Developer portal and our app configuration. The email and fullName scopes are requested in the credential. Please let us know if you require any additional information. We’re happy to provide whatever is needed. Here's a screenshot attached to explain the problem better

Is there some public git repo hosting "https://developer.apple.com/documentation"?

That time of year again. I’ve tried multiple restarts, and it still won’t load. I’m not sure if/how to remove the beta profile at this point (that seems to have worked for previous betas), given that the beta settings are hidden.

An error occurred while checking for a software update after the iOS 26 update. Is anyone else facing a similar issue?

When I updated IOS 26.1, When someone call me over voice call phone kept vibrating after call has been picked for 15 sec. Can you please check what’s the issue

Hey everyone, I'm beyond excited to share that I've been selected as a Distinguished Winner in this year's Swift Student Challenge! 🎉 It all started last summer, in the middle of a Western Culture class. I was zoning out , and my attention drifted to the Apple Pencil in my hand. And then ,it hit me — this thing is literally a next-level game controller. Think about it: pixel-perfect precision, haptic feedback, multiple built-in sensors... Why aren't we using this for gaming? And that got me thinking — why have we spent the last 500 years treating the "pencil" as just a tool for creation, and not for play? Since graphite pencils were invented in 1564, we've had this incredibly natural way to interact with 2D and 3D space... and nobody's fully tapped into it for games. So, I did something about it. I built a game that's 100% controlled by the Apple Pencil yep, just the Pencil. I know what you're thinking: "How does that even work??" And honestly, I'd love to tell you... but I'm in the final stages of getting it onto the App Store, and it should be live within the next couple of weeks. So for now... 🤐😄 In the meantime, I've set up a Discord server for anyone who's curious about the gameplay, the design, or just wants to brainstorm ideas with me. If you're into creative controls, game design, or just want to hang — come join the conversation! [Join the Discord here!] https://discord.gg/5Rm8WKbekf Can't wait to share more soon!

Hello, I'm experiencing issues with multiple apps on macOS related to network-related tasks. FIrst, I had problems with the network filter on Avast security. It told me to allow net work filtering, so I pressed the popup button that said allow filtering, but did nothing and gave me a error. Later on, on Nord VPN didnt work aswell, when I had to grant permission to configure a VPN. It didn't even give me a description of the error, just said something went wrong. I contacted NordVPN support, which didnt do anything exept for telling me to uninstall avast and restart my mac, which I did but was useless. Please help me.

Hello, My developer account was closed last week. In a conversation with Apple support, I was informed that the account was closed due to “inactivity”, but the account has always been in regular use and I was preparing to release an app last week. Now all my work is at a standstill because the account is “Acount Holder” and Apple Turkey Support team states that this account will never be reopened and that there is no support service for Developer account in Turkey. I asked for support for the Developer account globally, but they couldn't find it either. What can I do about this? My account was not inactive and I was constantly testing my apps via testflight and I submitted the latest version last week. Which department should I contact?

Hi everyone, I’m new to the Apple Developer side of things and I want to make sure I’m handling this correctly. I hired a freelance iOS developer to build my app. I have my own Apple Developer account (Individual), and I want the app published under my account. The developer says he needs me to create a Certificate Signing Request (CSR), then he will generate the distribution certificate on his end and send me the .cer file back. From there, he would use that for signing and submitting the app. My questions: 1. Is this the correct and modern way to handle app signing? 2. Should I instead just add him to my App Store Connect account with Developer access and let him manage signing through Xcode? Dev claims this won’t work, which I haven’t been able to prove or disprove. ChatGPT says it does,but other AI tools says it doesn’t. 3. Is there any risk in sharing certificates like this? 4. What is considered best practice in 2026 for working with freelancers while keeping full control of the account? My goal is simple: • The app stays fully under my Apple Developer account. • I retain long term control. • The developer can build and submit without needing my Apple ID or password. I’m not trying to make things complicated, I just want to do this the right way and avoid issues later. Thanks in advance.

Hi I experience this problem after update to the newest developer beta software on my iphone 17 pro: blackmagic camera said "storage full" although it is not final cut camera said "close and open the app again" It still works with prores (not raw). Anyone has the same problem as mine? I did try uninstall and reinstall the app and also restart the phone, try using different external ssd drive but nothing works.

We’re integrating Sign in with Apple using Apple’s official JavaScript SDK: https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js We’ve successfully used this setup with an older Service ID, but when we try to use any newly created Service ID, we get the following error immediately when calling AppleID.auth.signIn(): invalid_client This happens before any request reaches our backend. The same flow, redirect URI, and frontend code works fine with an old Service ID — but fails with new ones. ✅ What We’ve Verified: The Service ID (e.g., com.projectx.web.login) is created under Apple Developer → Identifiers → Service IDs The redirect URI is correct and matches exactly (HTTPS, no trailing slash) No client_secret is passed in the frontend (by design) We’re using usePopup: true ❌ What Doesn’t Work: Any new Service ID we create — even on the same domain and configuration — fails with invalid_client. 🔁 What We’ve Tried: Creating multiple new Service IDs Waiting 48+ hours in case of propagation delays Validating HTTPS and redirect URI setup Comparing all settings with the working (older) Service ID (which we deleted since we thought that was causing a problem) Testing in different environments and browsers ❓ Questions: Why do newly created Service IDs fail with invalid_client while older ones work? Are there undocumented requirements, propagation delays, or steps for new Service IDs to become active? Is this a known limitation or bug in the SDK? 💻 Our Code: import { useEffect } from "react"; import { Button, Box } from "@mui/material"; import api from "../utils/api"; // Axios wrapper import AppleIcon from "@mui/icons-material/Apple"; import MainAuthStyles from "../pages/MainAuthStyles"; import { useUser } from "../../../user-module/src/contexts/UserContext"; import { useNavigate } from "react-router-dom"; // Apple global type declare global { interface Window { AppleID: any; } } type AppleSignInButtonProps = { setApiError: (msg: string) => void; }; const AppleLogInButton = ({ setApiError }: AppleSignInButtonProps) => { const { user, setUser } = useUser(); const navigate = useNavigate(); useEffect(() => { if (!window.AppleID) return; window.AppleID.auth.init({ clientId: import.meta.env.VITE_APPLE_CLIENT_ID, scope: "name email", redirectURI: import.meta.env.VITE_APPLE_REDIRECT_URI, usePopup: true, }); }, []); const handleAppleLogin = async () => { try { const response = await window.AppleID.auth.signIn(); const { id_token, code, user } = response.authorization; const res = await api.post("/auth/apple-login", { idToken: id_token, code, user, rememberMe: true, }); if (res.data.success == true && res.data.user.userDataInitialised == true ) { setUser({ id: res.data.user.id ? res.data.user.id : '', fullName: res.data.user.fullName ? res.data.user.fullName : '', email: res.data.user.email ? res.data.user.email : '', role: res.data.user.role ? res.data.user.role : '', signUpType: res.data.user.signUpType ? res.data.user.signUpType : '', userDataInitialised: res.data.user.userDataInitialised ? res.data.user.userDataInitialised : false, }); localStorage.setItem("accessToken", res.data.accessToken); localStorage.setItem("refreshToken", res.data.refreshToken); navigate("/app") } else { setApiError("Unrecognized login method") return; } } catch (err) { console.error("Apple Sign-In failed", err); setApiError("AppleSignInFailed"); } }; return ( <Box mt={2}> <Button variant="outlined" fullWidth onClick={handleAppleLogin} className="AuthAppleButton" startIcon={<AppleIcon />} > Log in with Apple </Button> </Box> ); }; export default AppleLogInButton; Any help from the Apple team or anyone who's resolved this issue would be appreciated — we’re currently blocked on deploying new environments due to this error. Thanks!

In the public release of iOS 18.4.1 and iPadOS 18.4.1, external input support for keyboards and mice is critically degraded. This issue affects both Apple-branded and third-party HID-compliant devices, over both wired USB-C and Bluetooth. Tested Hardware: • iPhone 16 Pro Max (256GB) • iPad Pro (USB-C, latest gen), last gen iPad as well Affected Devices: • Apple Magic Mouse and Keys (wired USB-C/Bluetooth) • Redragon K580RGBPRO (Bluetooth/wired USB-C) • Razer Naga V2 Pro (Bluetooth/USB-C) Symptoms: • Severe keystroke delay and dropped input • Modifier keys (Shift, Command, Option) fail intermittently • Input degrades further with multiple HID devices connected • Mouse input via Bluetooth exhibits pointer lag and jitter • Occurs in all apps: Notes, Safari, Mail, text fields, password entries, etc. • Identical results using Apple USB-C cables Reproducibility: 100%. Clean boots, minimal background activity, and isolated environments (including Airplane Mode) do not resolve the issue. Identical behavior across both iPhone and iPad. Expected Behavior: All HID-compliant external input devices — particularly Apple-branded ones — should provide low-latency, reliable, and consistent input over both USB-C and Bluetooth, especially in a production iOS/iPadOS release. Actual Behavior: External keyboards and mice exhibit: • Lag • Dropped characters • Failed modifiers • Degraded mouse tracking Even with the latest hardware and clean configurations. Severity: Critical. This is a platform-level failure affecting I/O at the user interaction layer. Input reliability is non-negotiable — especially on $2000+ flagship devices using Apple’s own peripherals. Closing Note (for Apple engineering &amp; peer devs): This is not a beta regression — it’s a public release flaw that undermines iOS and iPadOS usability for power users, professionals, and accessibility communities alike. That Apple Magic Keyboard, Redragon, and Razer gear all fail equally and consistently should be a wake-up call. Apple: this needs to be escalated. Now. External input — one of the most basic subsystems in any OS — is broken on your highest-end devices.

Hi,Does anyone else encountered a delayed or unresponsive change when trying to change input languageon macos Sierra?Beta1 and 2 same problem.Working great on El Capitan.Thanks in advanced