My face id didnt work anymore after new version. After the installation Face id works, but few hours later stopped.

Hey, I'm pre-launch, and can't find any sample financial reports. Really need to see exactly what apple sends out to finish my backend. Anyone have a sample report, or willing to share one of their reports privately. (Promise to keep it private and destroy after use). I'm interested in exact format, not your sales. Particularly interested in reports from people using in app sales and discount offer codes. But that's a bonus. Thank you.

I have a FORD F250 2021. I returned for a deployment, and CarPlay does not work in my vehicle. I have tried all the YouTube, TikTok, Facebook, and Instagram videos I could find. They all actually started to repeat, so I decided to come here. My wife has an iPhone 16 Pro Max, and it connects to CarPlay without any issues. Other than all the social media suggestions, do you have any other suggestions? No, I am not ready to purchase a new device.

Installation has completed login is successful but after 30 secs it returns to login screen safe mode does the same. tried recovery mode and reinstalled. Still in the login loop. what are my choices now?

Over the past few months, I’ve been experiencing persistent, abnormal behavior on my iPhone. Here's a short timeline: March 2025: Most apps log me out every time I close them. April 2025: Stored passwords suddenly begin failing across apps and websites. May–June 2025: Password recovery emails from Gmail accounts no longer arrive — suggesting that Gmail itself may be compromised or blocked/intercepted. Given the escalation, I ran several diagnostics and extracted system-level logs. Below is a structured summary of findings that point toward potential remote access, network traffic rerouting, and possibly hidden use of Bluetooth or debugging interfaces. Device Information Model: iPhone17,1 (A17 chip) iOS Version: 18.5 (Build 22F76) Status: Stock, not jailbroken or running a developer build Region: Netherlands Carrier: KPN NL Language/Locale: Dutch (nl-NL) 1. Evidence of Remote Services and XPC Connectivity Source: remotectl_dumpstate.txt More than 50 remote lockdown and diagnostic services are listed as active. Notable entries: com.apple.mobile.lockdown.remote.trusted and .untrusted com.apple.mobile.file_relay.shim.remote com.apple.webinspector.shim.remote com.apple.pcapd.shim.remote com.apple.bluetooth.BTPacketLogger.shim.remote com.apple.mobile.insecure_notification_proxy.remote This volume of .shim.remote and diagnostic services appears highly irregular for a non-debug, non-jailbroken device. 2. Skywalk Network Flows and Unusual Routing Source: skywalk.txt Dozens of flowswitch entries across interfaces like: ipsec0-7, pdp_ip0-2, en0-2, awdl0 Apps such as Gmail, ChatGPT, Preferences, and com.apple.WebKit are marked as defunct, yet persist in flow tables. Two specific daemons — replicatord and siriactionsd — appear on nearly every interface, in both QUIC and TCP6 traffic. skywalkctl flow-route shows multiple external IP paths, with flows routed through ipsec7, owned by kernel_task.0 — indicate tunnelling? 3. System Anomalies and Resource Behavior Inaccessible System Network Tools Source: get-network-info.txt All scutil calls fail (/usr/sbin/scutil does not exist). This blocks access to: DNS configuration (scutil --dns) Proxy and VPN status (scutil --proxy, --nc list) Reachability checks (scutil -r www.apple.com) The absence of scutil is not expected right? Unusual Resource Usage Source: assetsd.diskwrites_resource-2025-06-25.json assetsd, working on behalf of cloudphotod, wrote over 1 GB of memory-backed files in under 1.5 hours. 4. Metadata Confirmation Source: Analytics-2025-06-27-020008.json Confirms: iPhone capacity: 256 GB DRAM: 7.5 GB Carrier: KPN NL Apps marked as highly active ("Games", "Creativity") in analytics also appear as defunct in skywalk, suggesting ghost background processes. Key Questions for the Developer Community Are >50 remote .shim.remote services typical on iOS 18.5 (release build)? Or does this suggest tampering, an MDM configuration, or debug provisioning? Could a misconfigured VPN or MDM profile enable persistent flow-switching across multiple interfaces (e.g., ipsec, pdp, awdl) and reroute app traffic such as Gmail? Is it possible for a test or developer certificate to silently side-load a background daemon, or trigger services like pcapd or file_relay, without showing in Profiles or Settings? Has anyone else seen the scutil binary missing or inaccessible on a stock iPhone? Could this be a sign of intentional lockdown or system modification? If anyone on iOS 18.5 / iPhone17,1 can share their remotectl_dumpstate output, I'd like to compare the service count and see if this behavior is reproducible. I’d appreciate any insight from those familiar with Apple’s system daemons, skywalk internals, or network service behavior. Happy to share sanitized logs or run additional diagnostics if needed. Thanks in advance. get-network-info.txt route-info.txt remotectl_dumpstate.txt [ assetsd.diskwrites_resource-2025-06-25-221428.json

I've got the initial WWDC beta of macOS 26 (25A5279m) installed inside a virtual machine (UTM), but can't seem to update to the second beta. Nothing is showing up within Software Update. Is this because it's within a VM, or am I doing something wrong? It'd be a real pain to have to install a new VM afresh with the RestoreImage for every update.

I’ve encountered a critical issue in macOS Tahoe (Beta) that affects the Photos app or any app that leverages Apple’s editing frameworks. After editing certain photos—whether applying filters, cropping, or making basic adjustments—the image suddenly turns completely black upon saving or exiting the edit mode. Details: macOS Version: macOS Tahoe (latest beta) Affected App(s): Photos, Preview, and some third-party editing apps Steps to Reproduce: Open a photo in the Photos app Make any basic edit (e.g., crop, adjust brightness) Click “Done” The edited photo appears entirely black Notes: Happens with both JPEG and HEIC formats Original photo appears fine before editing Exporting the photo also results in a black image Restarting the app/system does not resolve the issue iCloud Photos is enabled This issue seems related to the image rendering pipeline post-editing, possibly tied to Core Image or GPU rendering frameworks. It severely affects photo usability and could result in permanent data loss if backups are not maintained. Please advise if a workaround exists or if this bug has been logged already. Happy to provide system logs or sample images if needed.

Every broke I either open mail or the safari application they crash and eveytime I hit reopen and they crash again macOS 26 developer beta 2

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

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

For the last two weeks Time Machine has been unable to complete back up. It's throwing up the following: The error detail shows : The file does not exist in finder and have tried logging Mac out of iCloud and back in again but error remains. Any thoughts much appreciated.

My app has a menu called "Document". On Tahoe, this appears as a lightbulb icon. Is this deliberate? Is it possible to stop this? Or do I just have to use a different name if I want people to read words?

Hi, I am planning to apply for the Apple Swift Student Challenge. Is it acceptable to use Vietnamese names (proper nouns) within the app, provided all other text, code, and UI elements are in English? Will this still be considered valid?

Hi all, I just submitted my application to join the Developer Program. I went through the form, and got to the payment screen and filled out. I submitted and have received an "order acknowledgement" email, but I note that payment hasn't been taken, nor do I have any other emails regarding it. I understand my application can take a while to progress and it's still early days, but I'm concerned that it's stuck in limbo as payment hasn't been taken. With that and the notice on my account page that still reads: "Purchase your membership. To continue your enrollment, complete your purchase now Your purchase may take up to 48 hours to process." When I navigate to the payment screen again, I can see that there is no CVV field which my bank requires to accept payments. I'm wondering if anyone has had a similar issue and how they resolved or, even, if I have done something wrong during the application phase. 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 & 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.

I am trying to create a new app using IOS-26.1, macOS Tahoe 26.1 and Xcode 26.1 with Swift6. Is this a bug that is going to be addressed. This is in the Debug Console...Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x10bb18870 h=--& v=--& _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.width == 0 (active)>", "<NSLayoutConstraint:0x115ac2ee0 _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.leading == _UIButtonBarButton:0x115d40c80.leading (active)>", "<NSLayoutConstraint:0x115ac30c0 H:[_UIButtonBarButton:0x115d40c80]-(0)-| (active, names: '|':_TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0 )>", "<NSLayoutConstraint:0x115ac2df0 'TB_Leading_Leading' H:|-(12)-[_UIModernBarButton:0x115d20a80] (active, names: '|':_UIButtonBarButton:0x115d40c80 )>", "<NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.

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!

As of today we seem to continuously get back 21 of the product IDs we have defined when the shop initializes. This is causing what looks like intermittent bug behavior in our shop. The IDs sent each time are random (not always the same 21). So sometimes they match shop offers and the packs look right and can be bought and sometimes the ones our current shop offers need are not sent and so the offers in game look wrong and error when you try to buy. Is anyone else seeing this new behavior of not getting down all their product IDs successfully?

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

SiriSearchFeedback crashing 30 times per day for over a year, Siri completely broken - tried everything Hi, I have been dealing with a persistent Siri bug for over a year across two different iPhones (15 Pro then 16 Pro) and I cannot find a fix anywhere. The symptom is simple : Siri does not work at all. When I check Settings > Privacy > Analytics > Analytics Data, I see around 30 SiriSearchFeedback .ips crash files generated every single day. The bug_type is 313, which points to the parsecd daemon crashing in a loop, preventing Spotlight indexing and Siri from functioning. What I have already tried, all without success : Full restart Toggling Siri and Search settings for every app Disabling and re-enabling Suggest Apps Before Searching Temporary language switch (French to English and back) Deleting Siri and Dictation history from Apple servers Signing out of iCloud and back in Full factory reset, set up as new iPhone with no backup restored Switching to a new device (15 Pro to 16 Pro) The key point : the bug always comes back the moment I sign back into my Apple ID. This makes me think the corruption is stored server-side and synced back automatically with every login. Has anyone solved this permanently ? Is there any way to fully wipe Siri or Spotlight data on Apple's servers beyond the standard Dictation history deletion ? Any help appreciated.