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

iPadOS 26 Dev Beta 1 - need to do a restore via DFU mode. I made sure iPad in normal mode shows up in Finder and I can see device details. When I boot into DFU mode (I have kept the ipad connected to mac), it does not show up in Finder. No matter what combination of plugging/unplugging cables, rebooting, again into DFU mode, it will not show up in Finder. Looking for steps to resolve this, or do I need to wait until beta 2 to resolve this?

Hello everyone, I am looking for advice or help from anyone who has experienced a similar situation. I enrolled in the Apple Developer Program as an organization under the name Mindzone Technologies on Monday, December 15, 2025. Since then, the enrollment status has remained in “processing” with no updates. After waiting several weeks, I contacted Apple Developer Support twice but have not received any response. First email was sent on Monday, January 19, 2026 (GMT+4) Second email was sent on Friday, January 23, 2026 (GMT+4) Category: Membership and Account, Program Enrollment At this point, it has been over 40 days since enrollment and more than 3 business days since the last support contact, despite Apple stating typical response times are much shorter. There has been no request for additional documents, no phone call for identity verification, and no explanation provided. This delay is blocking our ability to publish apps and proceed with business commitments. Has anyone else faced an enrollment delay of this length recently Is there a specific escalation path or action that actually helped resolve this Should I expect a phone verification call or is there something I should proactively request Any guidance from Apple staff or developers who managed to resolve a similar case would be greatly appreciated. Thank you in advance.

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.

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?

XQuartz, used to run X11 apps on the Mac, does not work on Tahoe. Can you do something about this?

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.

As l proceeded through the enrollment/membership. I found the price is fixed for US$99. At the end. What about Renewal. Is there any cost reduction for Apple Developers?

Since iOS 26.1 I'm running into the following iCloud issues. Contacts are not being synced to iOS and iPad OS at all, no matter how I re-enable contact syncing I can't get them to sync. Somehow, my Mac and iPad are able to send out iMessages, but not my iPhone. My iPhone can receive and sync what I've sent using my Mac and iPad Unable to save an airdropped contact

I was wondering wether you have to create your full app as an Xcode app and then translate it into playgrounds? Because some of the submissions I have seen on YouTube are running on Xcode iPad emulators.

Hello Apple Developer community! While reading the SSC Full Terms and Conditions, I noticed that "Your app playground requires sign in" is a term for disqualification. If our app idea requires sign in for personalization and security, can we submit a prototype without the sign in feature and add it later before publishing the app? Or should we steer clear of app ideas that require sign in altogether?

Hello, Can someone let me know why my car play screen keeps changing and how do I stop the change?

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!

My app has three main SwiftData models: Collection, SavedItem, and Extract. A Collection can contain subcollections (folders within folders) and SavedItems (files). Each SavedItem can have child Extracts. I'm preparing for the ability for users to be able to share Collections with each other. Currently, my architecture treats each Collection as the root of its own CloudKit zone (a root parent Collection and all of its items and subcollections live in 1 zone). This makes sharing and isolation straightforward, but it also means that moving a SavedItem or subcollection between Collections involves moving it across zones. I’m trying to figure out the best pattern for handling these cross-zone moves while keeping data integrity, relationships, and sharing intact. My understanding is that in CloudKit, and moving a record from Zone A to Zone B would require deleting it from Zone A and recreating it in Zone B - while somehow maintaining the link back to my local SwiftData store. Has anyone run into this or know how best I should handle it?

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

System: OS: macOS 15.5 CPU: (10) arm64 Apple M1 Pro Memory: 82.02 MB / 16.00 GB Shell: 5.9 - /bin/zsh` IDEs: Xcode: 16.1/16B40 - /usr/bin/xcodebuild Managers: CocoaPods: 1.15.2 - /Users/liuxiwei/.rvm/gems/ruby-3.3.5/bin/pod SDKs: iOS SDK: Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1 Android SDK: Not Found i use react-native to build ios app . when archive than it happens: ld: Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5184.

hi team To continue testing Xcode 26 beta for our POS project's compatibility with the upcoming iOS 26 release in September, we’ve been running trials on various simulators. While the app works fine on iOS 18 simulators (iPad Pro/Air), it fails to launch on iOS 26-based iPad simulators with the following error: "libswiftWebKit.dylib library is not loaded"...... SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib (Detailed logs are shared below.) Is there a known fix for this issue, or is a resolution expected in an upcoming beta release? dyld[34660]: Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such file, not in dyld cache), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswiftWebKit.dylib' (no such file) Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/24F74/com.apple.CoreSimulator.SimRuntime.iOS-26-0.23A5260l/ DYLD_ROOT_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib```

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

Enrolled via website for the apple developer account last Jan. 17 and got the e-invoice last Jan. 19. However, until now I still have not received any confirmation from Apple. I thought it was supposed to be 48hrs max only? Worth noting that I started the process in the developer app but had to withdraw it due to incorrect details but when I tried to enroll again, the button was disabled already so I had to do it via website. I also submitted 2 support tickets, one on Jan. 18 and one today, Jan. 20. Both no reply. Anyone else here had the same problem or knows the solution?