what else can you do with it except for getting the alarm run off? and the alarm even gets dismissed when the user presses any buttons on device even volume buttons. I hope it's better by the time when iOS26 is officially released but I can't prepare for the new iOS update with this useless new framework. does anybody know what new features in this framework are coming up?

I found a glitch when you click on Phone and contacts the search bar is gone. You have to from the Home page click on contacts and the search bar is there.

This is my first problem and my first question hopefully somebody can help or give me some suggestions. I was in the developr beta of IOS 26 build(235260n) for a while I haven't updated it since the new beat has came out, beta 3. I have been trying to update requested, after about 20 seconds it goes away but does not start the download the update. The problem also begins to download something into the system beta goes from 22.85 GB to 33.78 GB. It just holds the update but doesn't;t update the phone. I have tried power cycling the device and everytime I do that it just resets the system data and allows up to try the update again. Unsure what to do and don't know if I would need to wait for the public beta for IOS26 to change anything on the device. Please let me know if you guys have any more suggestions what should be the next step. I also was unsure if I should backup the device and reinstall it to make sure that its not something with the conncetion.

Hello, We are developing a social media application that allows users to share and view content in the form of images and videos. The app is built with Angular and Ionic, and we use Capacitor to integrate native functionalities. Currently, we are experiencing an issue with content loading on iOS devices. Specifically, when the iPhone is connected to Wi-Fi, videos load quickly and play smoothly. However, when using mobile data, videos take a long time to load or, in some cases, do not load at all. We are trying to identify the cause of the issue and determine whether it could be related to Xcode configuration or any system restrictions. Some potential reasons we have considered include: iOS Mobile Data Usage Restrictions iOS may limit mobile data usage for large downloads or streaming content if the app does not have the proper permissions. In Settings > Mobile Data, users can restrict data usage for specific apps. App Transport Security (ATS) Configuration Xcode and iOS enforce strict security policies for network connections through App Transport Security (ATS). If the API serving the videos uses HTTP instead of HTTPS or has restrictive headers, this could affect loading over mobile networks. Xcode Network Usage Settings Xcode allows configurations related to network access. There might be a setting limiting access to mobile networks when the device is not on Wi-Fi. Video Quality and Adaptability Differences If videos are not optimized for mobile networks (e.g., high-quality formats without adaptive versions), loading times could be significantly longer. Implementing HLS (HTTP Live Streaming) could improve playback on slower networks. Request Timeout Issues If video loading requests have a short timeout, slower mobile network connections might exceed this limit, causing the request to fail. Compression and Caching It is essential to check if videos are properly compressed and if caching is implemented to improve performance on mobile networks. Given this situation, we would like to know what Xcode settings might be affecting video loading performance on mobile data and how we can adjust them to enhance the user experience.

I'm trying to create an Apple account for my client, and I'm getting this error "We can't create your account at this time." I've tried with two different email addresses and always get the same error. What could it be?

After too many boot loops and inability to boot up at all from system data bloating, I decided to restore the iPhone 16 Pro Max I’m beta testing on back to iOS 18.4 for a third time. Unfortunately, I found the iOS 26 beta 2 had made a iCloud backup last night, replacing my 18.4 backup. Is this something betas are supposed to do? I’ve been beta testing for around a decade now, I’ve never seen a iOS beta make an iCloud backup. Is anyone else noticing excessive system data bloating (70-100 GB or more)? Regardless, I’m in it for the long game now 😂

Hi everyone, After updating to iOS 26 Developer Preview on my iPhone, I’m experiencing a repeated issue with certain third-party apps. ⸻ -Issue details: • The apps open as if freshly installed, showing the onboarding or login screen each time • User session is completely lost (no saved login or data) • Around 10 seconds after launch, the app automatically closes • It disappears from the app switcher (not just backgrounded) • This happens every time, with no crash message or error shown ⸻ -What I’ve tried: • Reinstalled the apps • Restarted the device • Toggled Face ID, Background App Refresh, etc. • Confirmed I’m running the latest iOS 26 Developer Preview build ➡️ Problem still occurs exactly the same way ⸻ -Feedback status: I submitted a report via Feedback Assistant with a screen recording and full reproduction steps. No response yet after several days. ⸻ -Looking for: • Confirmation from others with similar issues • Info on whether this is already being tracked by Apple • Whether it’s worth resubmitting a new Feedback report Thanks for any insight.

When using a VStack containing two TextFields inside a ScrollView on an iPad running iOS 18.0, the FocusState of the topmost TextField does not trigger, while the second TextField's FocusState works correctly. Adding an invisible TextField on top resolves the issue, but it appears to be a bug specifically in iOS 18.0 on iPads. This issue does not occur on iOS versions below or above 18.0 (including iOS 18.1). Code that is not working struct ContentView: View { @State var text: String = "" @FocusState private var focusState: Bool var body: some View { ScrollView(.vertical, content: { VStack(spacing: 0) { TextField(text: $text) { Text("Hello, World!") } .border(focusState ? Color.red : Color.gray) .focused($focusState) .onChange(of: focusState) { oldValue, newValue in print(newValue) } .onChange(of: text) { oldValue, newValue in focusState = true } } }) .padding() } } Code that is working struct ContentView: View { @State var text: String = "" @FocusState private var focusState: Bool var body: some View { ScrollView(.vertical, content: { VStack(spacing: 0) { // Invisible Text Field TextField("", text: .constant("")) .frame(height: 0) TextField(text: $text) { Text("Hello, World!") } .border(focusState ? Color.red : Color.gray) .focused($focusState) .onChange(of: focusState) { oldValue, newValue in print(newValue) } .onChange(of: text) { oldValue, newValue in focusState = true } } }) .padding() } }

Dear team, I am reaching out to inquire about potential daily usage limits for the CoreLocation geocoding services. While I understand that there is a known limit of approximately 50 requests per minute, I have received information suggesting there may also be a daily cap of 25,000 requests. Could you please confirm whether such a daily limit exists? Additionally, I would appreciate any recommendations you might have for increasing the allowable number of daily geocoding requests, if possible. Thank you in advance for your support.

after updating to beta 4 the whole phone is not working anymore nothing is working only making calls and the camera no apps no internet even if it's connected to wifi or 5G ANd to get back to the old version you will lose your backup And now im stuck my data that i can't restore it cuz it have been made on the last IOS beta I don't want to lose my date and i don't know what to do Please help

I am trying to create a phone app that can receive incoming call notifications using CallKit, as described in Apple's CallKit documentation. Added the com.apple.developer.calling-app entitlement in my .entitlements file. Implemented CXProvider and set up the delegate methods (provider:perform: and providerDidReset). Added UIBackgroundModes with voip in Info.plist. Configured CXProviderConfiguration to support phone numbers. I expected to receive incoming call notifications when my app was set as the default calling app. However, I am not receiving any notifications when an incoming call arrives. How can I properly detect and handle incoming calls in my default calling app? Is there any additional configuration required for iOS 18.2+?

Latest ios cannot perform screenshot

From iOS 26Beta1, iOS 26Beta1.1 to iOS 26Beta2. I couldn't log in to the Feedback App for 4 weeks. It kept prompting BUGs and asked me to log in to Feedback. However, the problem was that I couldn't log in to Feedback. So the problem kept repeating. Apple didn't receive any feedback, so Apple thought this was the most successful version in the history of iOS because it didn't receive any feedback.

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

Hello developers, My question isn't directly related to app or software development, but this seems to be the most appropriate channel to possibly find the information I need. Context I work for an automotive company and I'm currently looking for Apple CarPlay certification guidelines. We're in the process of installing a multimedia system in a vehicle. The most viable solution would be to use the multimedia unit and microphone provided by our supplier, but with a custom wiring harness developed by our company to simplify the installation process. The multimedia unit, microphone, and the supplier’s harness are already certified for CarPlay. Question Would using our company’s custom wiring harness affect the existing CarPlay certification of the supplier’s product? Any information, contact, or suggestion on where I could find official guidance on this matter would be greatly appreciated. Thank you in advance!

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!

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design, hoping for the best. Thanks. My FB-FB18327769

Hello Apple Developer Community, I'm encountering a persistent issue while attempting to create a new partition on my Mac, and I'm hoping to get some assistance or insights from anyone who might have faced a similar problem. Issue Description: I'm trying to partition my internal drive. I initially used Disk Utility.app for this purpose. The partitioning process starts, but consistently freezes when it reaches approximately 10-20% completion. I've left it running overnight (for over 9 hours), but there was no progress, and the application remained unresponsive at that percentage. After several attempts with Disk Utility, I decided to try using the diskutil commands in Terminal to see if that would yield a different result. I used commands such as diskutil apfs resizeContainer and diskutil partitionDisk. Unfortunately, these commands also result in the same behavior: the process starts, reports progress up to about 10-20%, and then completely freezes without any further output or completion, requiring me to force-quit Terminal. Mac Model: Apple M4 Pro MacOS Version: Sequoia 15.6

Hi All, I searched for this feedback but didn't see it, so apologies if this has been covered by another thread. Exploring the new camera app, It doesn't seem to recognize that external storage has been connected, so the additional features that allow ProRes high frame rates will throw an error dialog stating that "to use this you need external storage" even when external storage is connected. Using the Files app, the phone recognizes the storage, and this is something I can do with this external storage device on the previous version of IOS. It is clear that this release of the camera has been rewritten significantly since the last version. Is it possible that this is an oversight, a bug, or just functionality that has not been completed? Interested if anybody else is seeing this, or if it is just my setup.

Since macOS 15.4 Beta 2, my App Store has been unable to install or download any new applications; it can only download applications I have previously purchased. It appears as follows: when I click 'Get,' the system spins to load and then returns to the initial state. Upon checking system error reports, it seems there's an issue with AMSUIPaymentViewService_macOS [2113]. This problem persists despite changing credit cards or even removing all credit cards. macOS 15.4 Beta 3 has not fixed this error.