I would love to partake in beta testing and reporting issues and bugs! Let me know what you got

My device with Device ID (00008130-001E35840483401C) is stuck in Processing state and cannot be activated. Please refresh or delete it.

腾龙镜头注册流程--薇---1847933278--旨在确保用户能够享受到官方提供的保修、客户支持和专属优惠。以下是注册腾龙镜头的一般步骤，具体流程可能因地区而异。 注册准备 购买渠道： 确保从授权经销商处购买镜头。 所需信息： 准备好镜头的序列号、购买日期和购买凭证（如发票或收据）。 注册步骤 访问官方网站： 前往腾龙官方网站，通常有专门的镜头注册页面。根据您所在的地区选择相应的网站（例如，腾龙美国、腾龙欧洲等）。 创建账户 / 登录： 如果是首次注册，您可能需要创建一个用户账户。如果已有账户，直接登录即可。 填写注册信息： 在注册页面上，填写镜头的所有必要信息，包括序列号、购买日期、购买地点等。 上传购买凭证： 按照网站指示上传购买凭证的扫描件或照片。 提交注册： 仔细检查填写的信息，确认无误后提交注册。 等待审核： 提交后，您可能会收到一封确认邮件。腾龙可能会审核您的注册信息，并在几个工作日内通知您注册结果。 注册完成后的权益 延长保修期： 在某些地区，注册后可以享受额外的延长保修服务。 参与活动： 获得参与腾龙举办的促销活动、研讨会和新品发布会的资格。 接收资讯： 订阅腾龙的电子新闻，获取最新的产品信息和优惠。

果敢腾 龙企业有限公司，薇---184-7933-278成立于2006年8月12日，下面给大家介绍一下公司主要位置和主要经营那些行业，腾龙公司位置靠于云南省临沧市边联的一个小城市，名称果敢老街，实时位置果敢城市中心双峰塔附近，公司主要是经营，旅游业，酒店服务行业，建筑业，科技游戏，餐饮，等等，这个有名的小城市虽然不是很大，但有着纸醉金迷小澳门的名誉之称呼，今天给大家介绍的就这些，如果你有想旅游的心，也欢迎来这个小城市旅游，来感受一下这里的民族风情。

In the official explanation, "deployment targets" refers to "the OS range supported by this version of Xcode for uploading apps to App Store Connect." On the Xcode Support page (https://developer.apple.com/support/xcode/), I can find the deployment targets supported by each Xcode version. My question is: can I use a newer version of Xcode to build an IPA with an older deployment target that isn’t listed? For example, can I use Xcode 26 to build an iOS 12 IPA (just build, not debug)? In my opinion, since the new SDKs still contain many old macros restricted to earlier iOS versions, it should be possible, but I’m not sure if that’s correct. Thanks.

Opened a FB already (FB20928652) but wanted to check here if anybody has seen similar or has better workarounds. xcresulttool merge appears to crash immediately after launch in Xcode 26.1 (and in 26.2b1). It does so regardless of any inputs passed in; the crash appears to be during argument parsing before any other logic is run, so it's not contingent on inputs. Working example from 26.0.1 (passing in arbitrary strings for a minimum-reproducible-case, so we expect to see an error message) : % /Applications/Xcode-26.0.1.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c Error: File or directory doesn't exist at path: b. Usage: xcresulttool <subcommand> See 'xcresulttool --help' for more information. The same example crashes in 26.1: /Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge --output-path a b c zsh: trace trap /Applications/Xcode-26.1.0.app/Contents/Developer/usr/bin/xcresulttool merge Again, this does crash in real use cases as well, the arbitrary strings are just for quick reproduction. The stack trace appears to be during argument parsing (which from a quick look, did indeed change between 26.0.1 and 26.1). On 26.1+, garbage data seemingly gets passed to AbsolutePath.init. * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 * frame #0: 0x00000001002c6748 xcresulttool-26.1`normalize(absolute:) frame #1: 0x00000001002c6438 xcresulttool-26.1`AbsolutePath.init(_:) + 28 frame #2: 0x000000010005a2c0 xcresulttool-26.1`Merge.run() + 372 frame #3: 0x000000010005b180 xcresulttool-26.1`protocol witness for ParsableCommand.run() in conformance Merge + 12 frame #4: 0x000000010011d3e4 xcresulttool-26.1`dispatch thunk of ReadableStream.close() + 16 frame #5: 0x000000010000148c xcresulttool-26.1`main + 156 frame #6: 0x00000001804d5d54 dyld`start + 7184 The only workaround we've found is to keep using 26.0.1's copy of xcresulttool, though that's obviously not ideal.

Body: I am writing to report an ongoing issue with the Apple Developer Program enrollment process specifically affecting developers in India, along with significant concerns about Apple's support responsiveness in this region. Issue Summary: I have been attempting to enroll in the paid Apple Developer Program ($99/year) using the Apple Developer app on my iPhone for the past 4 days. Every enrollment attempt results in the following errors: "Unknown Error - Please try again" "Invalid Request - Service mapping to the requested URL is not available" My Setup (All Verified Correct): Apple ID Region: India Trusted Phone Number: +91 (India country code, matching my Apple ID region) Two-Factor Authentication: Enabled (genuine 2FA, not two-step verification) 2FA Devices: iPhone, MacBook Pro devices, and trusted phone number all verified Account Information: Legal name, address, date of birth, and email all updated and verified on account.apple.com Device: iPhone 17 Pro running latest iOS Troubleshooting Attempted: I have completed every troubleshooting step suggested by the community and by Apple Support myself: ✅ Verified genuine Two-Factor Authentication is enabled ✅ Confirmed Apple ID region matches trusted phone number region (+91) ✅ Updated all personal information (legal name, address, email) on account.apple.com ✅ Force restarted iPhone multiple times ✅ Uninstalled and reinstalled Apple Developer app ✅ Signed out and signed back in with correct Apple ID ✅ Tested on both WiFi and cellular data ✅ Waited 48+ hours between attempts None of these steps resolved the issue. Support Response Issues: This is where my frustration peaks. I have attempted to contact Apple Support multiple ways: Phone Support: Shows "Phone support is currently unavailable" (though it was available last week) Email Support: Submitted via developer.apple.com/support → No response for 4 days Previous Contact: Had contacted support last week, but the troubleshooting steps provided did not resolve the issue Current Status: No follow-up communication or resolution path from Apple Known Issue in India - Why This Matters: I have researched this extensively and found multiple threads in this forum (dating back months) with developers in India reporting identical errors during enrollment. To date, I have not found a single resolved thread with a working solution. This indicates: This is a documented, recurring issue affecting Indian developers specifically Apple appears to have backend infrastructure issues specific to India Support has not provided a resolution path despite multiple reports The Real Problem: Apple's Developer Program enrollment system appears to have specific bugs or limitations that prevent developers in India from successfully enrolling, yet: Support responsiveness is severely lacking There is no documented workaround or known resolution The support team seems unaware of or unprepared to handle this region-specific issue My Request: Acknowledgement from Apple that this is a known issue affecting India-based developers A concrete resolution path (whether manual backend enablement, account review, or system fix) Expected timeline for resolution: Improved support responsiveness - Developers deserve answers, not silence Additional Context: I am ready to provide screen recordings of the exact error I have all the necessary documentation (identity verification, address proof, etc.) I am willing to complete any additional verification steps I simply need clear communication and a path forward I have been developing for iOS and want to contribute to the Apple ecosystem. However, this enrollment barrier is preventing me from doing so. Apple's support infrastructure for India needs improvement, and this issue needs attention. If any Apple team member is monitoring this forum, please escalate this issue. Indian developers deserve better support and communication.

The application crashes immediately when the system attempts to display the automatic password input view controller (_SFAutomaticPasswordInputViewController). This occurs during the login or password-filling process. OS Version: iOS 26.2 Beta 1 Build Number: (23C5027f) Fatal Exception: NSInvalidArgumentException *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil

When I try to get a developer account, I keep getting the error "Payment approval failed". Can someone please help?

Hello On Nov 11, 2025 I upgraded Xcode to 17B100 I found instructions to install it on an external drive because the old way of doing it (install to /Applications and move it to the desired location) didn't work. I downloaded the dmg, moved it to the external drive and the install worked I now have a usable Xcode sitting on my external drive The problem is, there are no simulators and the normal method of downloading them does not work. How do I install simulators (preferably on my external drive) for use by my externally installed Xcode (same drive)?

Why can’t sandboxed mac app store apps have full disk access available in the system settings for full disk access? I discovered mac app store apps in release mode cannot access the ai auggie command line program and other command line programs like opengrep on your system. Debug builds fine. I came up with a workaround: Since I have an ssh client built in for connecting to remote servers, why not connect to ssh on the same local machine… Ask the user for their username and password in a popup. To do this, you have to enable remote login on your mac in system settings -> sharing. In addition you must grant full disk access to cli ssh in system settings: add /usr/libexec/sshd-keygen-wrapper It all works, but I don’t see the cli program in mac settings. To remove the cli program you must run a command line program to remove all full disk access support from all apps. No way to just undo ssh. So my question is, even though I got CodeFrog all working for a mac app store release, should I not do it because it’s insecure or too complicated with the system settings? Should I instead sell the app off the store like Panic Nova? Need some advice. I have not implemented in app purchases yet. Should I just have a reality check and sell the app off the store, or try for app store approval? Bummer… Maybe I’m ahead of my time, but perhaps Apple could review the source code for apps requesting full disk access and make sure there’s nothing fraudulent in them. Then, developer tools app store apps could be in the store with the user’s assurance that nothing is happening behind the scenes that is scary. From: https://blog.greenrobot.com/2025/11/10/i-have-a-decision-to-make/ Related post: https://developer.apple.com/forums/thread/806187 I submitted a code level tech support question for this. They directed me here.

Hello - I’m the Account Holder for an individual Apple Developer Program account. I’m working with freelance junior developers who are building my app in React Native mainly in TypeScript (.tsx) with some JavaScript, with code in GitHub. The app currently runs in Expo Go now. I’ve been directed to this forum for step-by-step guidance. Specifically I need clear, sequential instructions I can give my developers (and what I personally must do on my Mac) so they can produce a properly signed iOS build for TestFlight (internal testing), and Upload that build to App Store Connect and then submit the release to the App Store. Context: This is an individual developer account (not an organization). I am the only person with a Mac. I added them as developers but was told I need to be the one to upload the final build (is this true, and if so, what do they send me to do that, and when they send it to me, can you please tell me exactly what I need to do from there?) I was told about Swift Playground, possible SwiftUI conversion if needed, APK file, and using my Xcode for final submission, but not sure what to make of this that will get it on TestFlight from the current React Native. What I would like to ask for help with is a concise, step-by-step checklist (including exact menu names / commands or tools like EAS Submit, Transporter, or Xcode) of the developers' steps and my admin/account holder steps, so I can hand it to the developers and make sure nothing is missed to get on TestFlight. I’m on a tight timeline, so any clear, detailed guidance would be extremely appreciated. Thank you so much. I have looked everywhere and cannot find a step-by-step!

I wanted to rollback a commit. So I shifted to the commit before it. Then I added new commits on the one I switched to, not realising this is not happening on the main branch. Now what do I do? Neerav

Simply opening Simulator app (26.0) causes high CPU usage on macOS Tahoe (26.1). ReportCrash process usage is very high throughout and causes the system to heat up pretty soon. Looking into Console app for the logs found MercuryPosterExtension process is keep on crashing. (Check under Crash Reports) simctl Diagnose https://download.developer.apple.com/OS_X/OS_X_Logs/simctl_Diagnose_Logging_Instructions.pdf Share the Simulator Diagnose report while reporting, Thanks. I have raised a ticket/feedback with Apple. I request all of you to raise one too so this gets fixed soon. Apple Feedback Assistant - FB20985249

Hi there, We’re encountering this error in all of our builds when using the latest Xcode and macOS: The Metal Toolchain was not installed and could not compile the Metal source files. Download the Metal Toolchain from Xcode > Settings > Components and try again. In short, all builds are failing. I’ve tried fixing this by installing Metal and applying other solutions, but none of them worked reliably. Is there a way to ensure that the Metal Toolchain is installed on the CI machine?

In the Swift UI tutorial on the official website of apple developers, https://developer.apple.com/tutorials/swiftui/creating-and-combining-views, Step 2 in Section 2, through Command-Control-click, the full menu in Figure 1 cannot appear, but the style of Figure 2 appears, and the "Show SwiftUI Inspector" option is missing, see Figure 2. Similarly, in Step 6 of Section 2, "Control-clicking on the Text declaration in the code editor", the options in the red box in Figure 3 cannot appear, and It is the style of Figure 4, and all the options in the red box of Figure 3 are missing. There is no one in Show Coding Tooks. I am using Macbook air 2020 M1, macOS is the latest Tahoe 26.1, and the xcode version is 26.1. The project files used in the learning tutorial are downloaded directly from the above link. Thank you very much for your help to a beginner, which is very urgent for me. I look forward to your reply and sincerely thank you again.

I just updated to Xcode 26 and some of my Swift Packages have been getting strange build errors that I have not been able to resolve. When I try to build my Swift Package in Xcode I get the following error Module dependency cycle: 'UIKit.swiftmodule -> .swiftmodule -> SafariServices.swiftmodule -> UIKit.swiftmodule' It seems like it is related to the change in Xcode 26 that states "Swift explicit modules will be the default mode for building all Swift targets". I see that you can disable this with the build setting SWIFT_ENABLE_EXPLICIT_MODULES=NO, but I don't see a way to do this in Package.swift, as you can't include value assignments like this .define("SWIFT_ENABLE_EXPLICIT_MODULES=NO"). Our private SPM repos use CI/CD and so we need to be able to build them independently of any use in a project. I would appreciate any help on fixing our Swift Package builds in Xcode 26, thanks!

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?

Description: I’m noticing that the code coverage metrics in Xcode 26 are not accurate compared to earlier versions. In Xcode 15, the same set of unit tests shows around 38% coverage, but in Xcode 26, even though all the tests are running successfully (for example, the SegmentedUI test cases), the code coverage is displayed as 0%. Has anyone else observed this behavior in Xcode 26? Is there any known issue, workaround, or configuration change required to get the correct coverage report? Environment: Xcode 26 iOS 18 SDK Unit tests running under XCTest Any insights or suggestions would be appreciated.

Hello everyone, We are currently facing an issue when testing our hybrid mobile application (built with Ionic and Angular) on the iOS Simulator. The app works perfectly on physical iOS devices — all HTTP requests complete successfully. However, when running the same build on the iOS Simulator, every HTTP request fails with the following error: { "headers": { "normalizedNames": {}, "lazyUpdate": null, "headers": {} }, "status": 0, "statusText": "Unknown Error", "url": "https://api.bizify.com.br/demo/api/ping", "ok": false, "name": "HttpErrorResponse", "message": "Http failure response for https://api.bizify.com.br/demo/api/ping: 0 Unknown Error", "error": { "isTrusted": true } } We have confirmed that the API endpoint https://api.bizify.com.br/demo/api/ping is reachable and secured with a valid SSL certificate. This issue occurs only in the iOS Simulator — not on Android devices or physical iOS devices. Has anyone encountered this issue before? Any insights on why the iOS Simulator might be blocking or failing these HTTPS requests — and how we could resolve it — would be greatly appreciated.