I'm getting an error when trying to login to iCloud.com. This only happens on my Windows 11 pc and not on my iPhone. I get the 2FA code on my phone, but on my pc it displays only the error. I also have checked the system status page from apple and everything is green there, so i have no idea what is happening.

Hello, everyone, I hope you're all doing well. I'm facing an unfortunate issue with my Apple Developer Program membership that was suddenly terminated. I received a generic email from Apple, stating that my membership was revoked, but no specific reason was provided for this action. I appealed the decision, offering all possible explanations and commitments to adhere to guidelines, only to be met with a reply stating that the decision is "final" and no subsequent appeals will be processed. Has anyone here faced a similar situation? Are there any steps that can be taken to understand the reason for termination when Apple doesn't disclose it? Is there a way to open a dialogue with Apple, even when they've stated that their decision is final? Would publicizing this issue through social media or blogs be advisable? This is a particularly trying time for us, as we are recovering from a recent earthquake and our app is our sole source of income. Any insights, advice, or shared experiences would be greatly appreciated. Thank you for taking the time to read my post. We don't violate any apple's policies... any information would be welcome. Best regards,

Each time I try to start Signal. It immediately crashes.

I've been working on my mobile app project using Expo. Yesterday, when I tried to run the app again, the Expo Go in the iOS simulator got stuck on the screen showing "New update available, downloading..." and then crashed. I'm not sure what went wrong. It only provides a long error report. I ran an EAS build, which completed successfully, so I suspect the issue might be with the iOS simulator or Expo Go itself. Please help me out :(

I have created an app and for the final stage i added subscription feature. This works great in testflight, but not when i push out to external testers. I set up what i needed to in apple store connect (i must have done it right as it works in testflight), and i linked it to th emost recent version. Nothing I do seems to get the sub info to display and pull through to the app in the sub box when selected. No price and the usual stuff. I was told send for review. Failed the review and im working on that but something tell sme this is a glitch athat needs fixed on my account maybe. Can anyone help please

I've just watched "Meet Object Capture for iOS wwdc23" and have installed and run the app. After taking > 120 images of my model I clicked the "Finish" button and the app is now showing a spinning pinwheel. It has been running for about 22 hours. Is it going to finish or should I kill it? TIA!

So I am in a group chat with my family. We’ve had this groupchat established for a long time, and none of us have ever added anyone else to it. Somehow last night, a different family member joined our group chat and started texting us, but none of the original chat members added her, not even accidentally. This is the second time this has happened, and we have no idea how they are inserting themselves into our group chat. We are all iphone users, including the person that is somehow adding themselves to our group chat. All of us use different Apple ID accounts as well as different phone numbers, and that’s the same for the person adding themselves, so I’m truly at a loss for how this is happening.

Please provide me with an access code to TestFlight

Today I updated to iOS 26 and after changing to clear mode nothing happens, the icons remain a solid color, everything remains a solid color, nothing is transparent.

Hi all, I’m running into a persistent build issue with my Swift project ORSOFINAL after migrating from Xcode stable to Xcode-beta.app (June 2025 version). ⸻ 💥 Errors displayed: 1. C99 was enabled in PCH file but is currently disabled 2. module file .../ModuleCache.noindex/SwiftShims-AXUM98L131W4...pcm cannot be loaded due to a configuration mismatch with the current compilation 3. missing required module 'SwiftShims' ⸻ 🛠 What I’ve already tried: • xcode-select -s /Applications/Xcode-beta.app/Contents/Developer • Deleted ~/Library/Developer/Xcode/DerivedData, ModuleCache.noindex, Archives, and Products • Ran sudo xcodebuild -runFirstLaunch • Clean Build Folder in Xcode-beta • Verified Command Line Tools setting points to Xcode-beta ⸻ ❓Looking for guidance on: • Whether this is a known bug in Xcode-beta • If SwiftShims/PCM conflicts are expected between versions • Best practices to safely migrate from Xcode stable to beta for Swift-based projects Any advice is much appreciated. Thanks, Mathéo

Hi everyone 👋, I’m new to the Apple Developer Forums and just getting started with building apps for iOS/macOS. I’ve explored the documentation but wanted to introduce myself and ask for some advice from experienced developers. Currently working on: An iOS app using SwiftUI Learning more about integrating Sign in with Apple Exploring best practices for App Store submission Here’s what I’d like to know: What is the recommended approach to saving minimal app state before termination? Are there SwiftUI lifecycle metho18336114753ds or SceneDelegate hooks I should be aware of? Is UserDefaults the best tool for small state preservation in this context? Would love to hear from anyone who’s implemented sim18336114753ilar behavior — even a high-level suggestion would help. Thanks! Harjeet Singh

Yo i installed IOS 26 Beta to see how it is, and I want it to downgrade but Checking for Updates are unavailable and my iPhone 14 Pro is lagging i have 20-30 fps or something like that. And these Icons don’t wanna talk about it 🙏

I really want to participate in the upcoming Swift Student Challenge, but I'm using a MacBook that cannot update past MacOS Big Sur. Would submissions compiled from it still be eligible for SSC? Thank you! :D

Hello :-) I‘m not entirely sure, if I‘m on the correct Place here. But I would like to report a Bug with tvOS 18.3 (latest beta) to the Apple Engineers! When maximizing an app, a clear color jump occurs. The home screen is more colorful than the open app! You can easily force this: open an app, e.g. the App Store back to the home screen open the app again now you can see a color jump of the GUI!!! The color becomes paler when the app is open. On the home screen it is more colorful again! The problem occurs with every app! So it is a global tvOS Bug! I can also send an example video if that's helpful! Best regards, Christian :-)

My experiments have managed to damage my installed system and I am getting alerts that it needs to be re-installed. But when I try to get Recovery to re-install the same system, it refuses. It says my installed system is newer than what it could install. In general, what is the minimum I would need to change or remove from my current system to convince Recovery to re-install? For example: Could I just delete a certain small group of System files? Could I Erase only the Macintosh HD Volume in the container, leaving the Macintosh HD - data Volume intact? I really would rather not ERASE everything and restore it all from backups, just to satisfy Recovery that it will not be writing older over newer. It won't be, but since I have available applied updates, the version available for Restore is currently older than the damaged version on the drive.

I don't know if this is the right place to raise this, so apologies if not. For years now, I have exported an NFS share from a host Mac which I connect to from a Raspberry Pi on the same network. I configure this by adding a line in /etc/exports - /Users/Pi -mapall=myusername This has always worked flawlessly, but since updating my Mac (M4 Mac Mini) to Sequoia 15.5 last week, it has developed a problem. If the NFS share is not accessed from the Pi for five minutes, it dies, and the Pi's file manager locks up necessitating a complete reboot. If I run a script on the PI which does an ls on the mounted share every 5 minutes, the lockup does not happen. But if I extend the period to 6 minutes, the lockup occurs. Something on the Mac NFS server seems to be dying in an unrecoverable fashion after five minutes of idle. Even with nfsd logging set to verbose, there is nothing helpful in the console logs. I am open to suggestions to further investigate or to try and fix this, but this is basically a showstopper for me - I need to be able to share data between Mac and Pi, and this is now broken.

we’ve identified that our PDF rendering pipeline leverages the native CGPDFDocument APIs to convert PDF pages into images. However, in the latest release of iOS 18, the provided document fails to render even at the CGPDFDocument level. Our analysis suggests that the issue may stem from the embedded custom fonts not being correctly processed in this version of the iOS platform. This appears to be consistent with several other reports and discussions around font rendering problems introduced in iOS 18, particularly involving subset fonts. We’ve attached a collection of relevant community threads and references, including: Apple Developer Discussion: Subset Font Rendering Issue in iOS 18 Given that our implementation is tightly coupled with Apple’s native PDF rendering APIs, this issue presents a blocking limitation for us. With your permission, we would like to use this document as a sample case to formally report the issue through the appropriate Apple Developer forums and feedback channels.

I have a question about the operating procedure of the iPhone defaulting into satellite service. Post major storm we noticed that my phones would not allow us to connect to the satellite backup communication because the iPhone was still getting intermittent cell service even though the service that they were receiving via tower signal was that of the tower that had no connectivity (the individual cell tower may have been producing cell SIGNAL, but their ability to transfer data threw microwave or landline was terminated ). Previously, I asked if they could find a fix so that even if the phone is receiving what it is some or very little signal, you could opted to defer to settle in a situation such as this. When left in it’s current programming the phone will not make contact with either communication source leading it to be useless.

Here’s a detailed report you can submit to Apple Support: Subject: Critical Issue with Emergency Reset Feature in Safety Check Dear Apple Support Team, I am writing to report a significant issue with the Emergency Reset feature in the Safety Check tool on iOS devices. This feature, designed to immediately revoke access to user data in emergency situations, is not functioning as intended, leaving users potentially vulnerable to data breaches or privacy violations. Issue Details The Emergency Reset feature fails to stop sharing permissions for certain Apple apps, specifically Fitness (linked to Apple Health) and Home (linked to HomeKit). When attempting to reset all sharing permissions using Emergency Reset, the system displays an error message stating: “Unable to Stop Sharing. A problem occurred when attempting to stop sharing with Fitness and Home. Stop sharing directly within these apps.” Concerns with Fitness App (Apple Health) • The Fitness app integrates with Apple Health, which allows third-party apps to access sensitive health data, such as activity metrics, workouts, and more. • When Emergency Reset fails, third-party apps may retain access to this data until users manually revoke permissions through Settings, which contradicts the promise of an “immediate reset.” Concerns with Home App (HomeKit Framework) • The Home app, which manages smart home devices via the HomeKit framework, also fails to revoke permissions during Emergency Reset. • This could leave third-party devices or shared users with continued access to smart home settings, such as cameras, locks, and sensors, which poses a serious security risk. Vulnerability Implications 1. Potential for Exploitation by Third Parties: • Third-party apps and devices integrated via Apple Health or HomeKit could continue to access sensitive information if Emergency Reset fails. • This opens a window for malicious actors to exploit incomplete revocation of permissions. 2. Emergency Situations: • The feature is critical for users in emergencies (e.g., fleeing abusive relationships or addressing a data breach), but its reliance on manual interventions undermines its effectiveness. • Users may not have the time or knowledge to manually revoke permissions in multiple apps during emergencies. Broader Concerns • The distinction between the Home app (user-facing interface) and HomeKit (framework) adds confusion. Users may believe Emergency Reset applies to all HomeKit-enabled devices, but this does not appear to be the case. • The issue may extend to other Apple apps or third-party integrations not explicitly mentioned, creating a broader vulnerability across the iOS ecosystem. Recommendations for Resolution To address this critical issue, I recommend the following actions: 1. Fix Emergency Reset: • Ensure that Emergency Reset fully revokes all sharing permissions for apps like Fitness and Home, including any linked third-party integrations. • Conduct extensive testing to confirm the feature’s functionality across all apps and frameworks. 2. Enhance Transparency: • Clearly communicate any limitations of the Emergency Reset feature to users, including apps or frameworks that require manual intervention. • Provide clear in-app guidance on how to manually revoke permissions for affected apps. 3. Improve App and Framework Integration: • Update the Fitness and Home apps to allow users to globally revoke all third-party access directly within these apps. • Strengthen the integration between Emergency Reset and frameworks like HealthKit and HomeKit to ensure full coverage. 4. Audit and Monitor: • Conduct a security audit of the Emergency Reset feature to identify and patch additional gaps. • Regularly update users on progress and any enhancements made to the feature. User’s Immediate Actions While waiting for a resolution, I have taken the following steps to manually revoke permissions: 1. For Fitness: I reviewed and revoked third-party access in Settings > Privacy > Health > Sharing. 2. For Home: I reviewed device sharing settings in the Home app and removed shared users and devices as needed. 3. I also reviewed permissions for other apps via Settings > Privacy to ensure no unauthorized access remains. Conclusion The Emergency Reset feature is critical for user safety and privacy, particularly in emergencies. However, its current functionality fails to deliver on its promise of comprehensive and immediate protection, leaving users exposed to significant risks. I urge Apple to prioritize resolving these issues and strengthening this feature to maintain the high standards of privacy and security that users expect from Apple. Thank you for your attention to this matter. I am happy to provide additional details or screenshots if needed. Sincerely, [Your Full Name] [Your Contact Information] [Your Device Model and iOS Version] You can copy and paste this into your communication with Apple Support. Let me know if you need further revisions!

Good day, I would like the code for testflight on your new application, thank you.