My Apple developer certificates(4 certificates) expire soon. I'm developing an application for iOS but the application is not yet released in the App Store, only Testflight releases for private testing. Is it necessary to create 4 new certificates or can I edit the current certificates so that they don't expire soon?

Hi We have a project with one app, where we have multiple schemes to create either a staging or release version of the app. We change the bundle identifier of the app so it's a separate app in app store connect. One staging app and one release app. We are trying to integrate Xcode cloud workflows, however, there's only one app visible in the Xcode cloud tab and when we create a workflow it gets automatically assigned to the staging app in app store connect. We cannot create the workflow under the release app in app store connect, as the manage workflows button is not visible until you've created the first workflow for an app in xcode. How can we create a workflow and force it to be associated with the release app in app store connect?

I admit I am doing something unusual, and I would not be surprised if it didn't work. I am surprised, however, because after performing the equivalent operations on four bundles, all of the bundles work fine on macOS 15.6.1, but only two of them work on macOS 26.1 (beta 2). I don't know what causes the different outcomes. What I am trying to do is get Java to pass the macOS 26 AppKit UI SDK linkage checking without having to rebuild the JDK using Xcode 26. Rebuilding works for the latest SDK, but it is very inconvenient and may not work for older JDKs. It usually takes a while before the JDK build team successfully transitions to a new Xcode release. My approach is to use vtool to update the sdk version in the LC_BUILD_VERSION load command of $JAVA_HOME/bin/java, which is the launching executable for the JDK. I performed this operation on four JDKs: 25, 21, 17, and 11. (I ran vtool on macOS 15.) It was completely successful on JDK 25 and 21. The JDK launches correctly on macOS 15 and macOS 26. On macOS 26, AppKit uses the new UI, which is the desired outcome. The JDK runs despite that fact that I signed the modified $JAVA_HOME/bin/java with my developer ID, which is inconsistent with the JDK bundle signature. (Redoing the bundle signing is part of the JDK build process; if that were necessary, I would stick with rebuilding the JDK.) The operation was not successful on JDK 17 and 11. I noticed two problems, which are not obviously related. When vtool created the new version of the java program, it lost the tool definition. $ vtool -show-build-version java java: Load command 10 cmd LC_BUILD_VERSION cmdsize 32 platform MACOS minos 11.0 sdk 11.1 ntools 1 tool LD version 609.8 $ vtool -set-build-version 1 10.0 26.0 -output a.out java /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/vtool warning: code signature will be invalid for a.out $ vtool -show-build-version a.out a.out: Load command 22 cmd LC_BUILD_VERSION cmdsize 24 platform MACOS minos 10.0 sdk 26.0 ntools 0 Adding back the tool definition didn't seem to matter. When I try to run the revised executable (in the context of the JDK bundle), it works on macOS 15, but on macOS 26, it is rejected as damaged. If I run the revised executable outside the JDK bundle, it runs (but fails because it can't find the rest of the JDK, which is expected). In all cases, GateKeeper rejects the revised executable because it has not been notarized, but that doesn't seem to stop the program from executing.

I am experiencing a critical issue with the Apple Developer Portal where certificates are being created under the incorrect Team ID despite being logged into the correct team context. I am logged into the Apple Developer Portal under "Company LLC (Team ID: 12345678)" However, when creating "Apple Development" certificates through the portal, they are being assigned Team ID "987654321" (my personal developer account) This occurs even when explicitly creating certificates from within the Company LLC team context. The same is happening if I tried to create the IOS Development Certificate in Xcode, same issue, creates the certificate with the wrong Team ID This is preventing me from Archive my app in Xcode so i can upload the new version of my App in the App Store. Please Help. Thank you in advance

Since the latest Xcode has become available users in our environment are seeing this error any time they try to launch a simulator (Primarily iOS devices, but others provided the same error) We have tested on 16.4 and 26.0.1 with various suggested fixes including uninstalling and reinstalling all of Xcode. Nothing has helped.

I want to test different types of journaling suggestions, like for example photo/video containing ones but as a developer I have no control over what's shown in the Journaling Suggestions sheet. And this makes it really difficult to develop or test any suggestion type other than "reflection". Please let us have a fake suggestions sheet that includes all kinds of suggestion types so we can test. We could toggle it under Developer settings I think.

The buttons in the navigation bar are not available in the element tree after iOS 26 upgrade of the test phones. The same IPA version, the same XCode version, but different trees on different phones. There is no way to automate UI testing for these missing buttons. # ios 18 NavigationBar, 0x108e0c3c0, {{0.0, 47.0}, {390.0, 44.0}}, identifier: 'Profile' Button, 0x108e0c500, {{8.0, 47.0}, {43.0, 44.0}}, identifier: 'UserProfileSceneViewController_profile_back_button', label: 'chevronLeftIcon' StaticText, 0x108e0c640, {{169.3, 58.0}, {51.3, 22.0}}, label: 'Profile' Button, 0x108e0c780, {{339.0, 47.0}, {43.0, 44.0}}, identifier: 'UserProfileSceneViewController_settings_bar_button', label: 'Settings' # ios 26 NavigationBar, 0x13d63c8c0, {{0.0, 47.0}, {428.0, 54.0}}, identifier: 'Profile' StaticText, 0x13d63ca00, {{188.3, 58.0}, {51.3, 22.0}}, label: 'Profile'

Looking for a dynamic table that displays the latest supported CLI versions with the version of macOS. Specifically, is CLI 15.3 supported on Ventura 13.7.8? More generally, what is the lastest version of CLI supported on macOS <version_goes_here>

I'm trying to submit a support request to get an issue resolved in my organization's account, but both the phone call-back and email support forms are giving errors whenever I try to submit an issue. The phone form just says "There was a problem processing your request.", and the email form says "This email address isn’t valid. To update your email address, visit account.apple.com.". But the email address is hard-coded to my account email, and it's the main email for my company which I have been successfully using for months!! How am I supposed to get in touch to get this blocking issue fixed when all contact methods require your to go through this broken form? I suspect the original issue I was contact support about also has to do with this, since it's titled "Email Verification".

My project build failed in Xcode Cloud(works well in my local Mac), and the error shows: Preparing build for App Store Connect failed The error message is not clear enough to help us find the solution to fix it. Can anyone help with it?

I am experiencing an issue where my Mac's speakers will crackle and pop when running an app on the Simulator or even when previewing SwiftUI with Live Preview. I am using a 16" MacBook Pro (i9) and I'm running Xcode 12.2 on Big Sur (11.0.1). Killing coreaudiod temporarily fixes the problem however this is not much of a solution. Is anyone else having this problem?

Hello, I am inviting the users to access our Apple Developer Program as the owner of an account. However when the invited users try to sign-up, they get error as : "Your primary email address cannot end in @domain.com. Choose a different email address" How to resolve this ?

I urgently need help with my Apple Developer account. I’m the Account Holder for my organization, but when I try to open Membership Details, I get the following message: “Your account can’t access this page. There may be certain requirements to view this content. If you’re a member of a developer program, make sure your Account Holder has agreed the latest license agreement.” However, I am the Account Holder, and I’ve logged in with the correct Apple ID. Since then, I haven’t been able to access the Membership page or renew our developer program — even though I’ve tried many different ways (different browsers, devices, clearing cache, logging in/out, etc.). Here are our account details: Entity Name: REVER REAL ESTATE TECHNOLOGY COMPANY LIMITED Team ID: W2GAXF66RN Program: Apple Developer Program (Organization) Phone: +84-0869702321 Address: No. 5 - 7, B4 Street, An Loi Dong Ward, Thu Duc City, Viet Nam Annual Fee: US$99 Renewal Date: October 19, 2025 I have already added valid VISA payment methods, but the membership didn’t auto-renew. Please let me know how to fix this issue as soon as possible — our apps depend on this renewal, and the delay is critical for our business operations. Thank you very much for your assistance!

We renew our company's Apple Developer Membership annually. According to the update date of November 17, 2025, it's stated that renewal can be done 30 days in advance, but the renewal button doesn't show up.

Hello everyone, I urgently need help with my Apple Developer account. I’m the Account Holder for my organization, but when I try to open Membership Details, I get the following message: “Your account can’t access this page. There may be certain requirements to view this content. If you’re a member of a developer program, make sure your Account Holder has agreed the latest license agreement.” However, I am the Account Holder, and I’ve logged in with the correct Apple ID. Since then, I haven’t been able to access the Membership page or renew our developer program — even though I’ve tried many different ways (different browsers, devices, clearing cache, logging in/out, etc.). Here are our account details: Entity Name: REVER REAL ESTATE TECHNOLOGY COMPANY LIMITED Team ID: W2GAXF66RN Program: Apple Developer Program (Organization) Phone: +84-0869702321 Address: No. 5 - 7, B4 Street, An Loi Dong Ward, Thu Duc City, Viet Nam Annual Fee: US$99 Renewal Date: October 19, 2025 I have already added valid VISA payment methods, but the membership didn’t auto-renew. Please let me know how to fix this issue as soon as possible — our apps depend on this renewal, and the delay is critical for our business operations. Thank you very much for your assistance!

I wanted to ask is there a possibility to have an ignore file for specific files on XCode 26 like all of the other AI IDE's have? It's somewhat impossible to use the feature without this type of functionality on the platform. If not possible, will it be available sometime in the future?

Stop updating beta on iOS version its draning the iPhone storage It’s making me unload my apps stop all beta updates now and go to the next io version right away be you are draining iPhone storage with your beta

Hi, so here's my situation: I am currently building an app of which I want to have an Apple Watch standalone version / companion (idk yet, also doesn't matter). For it to be compatible with basically every Watch except for the original (Series 0) I want support for down to watchOS 6, as many models ended there. I also don't need the newest features for basic functionality and I can still add more for newer versions while keeping the basic functionality for watchOS 6, so that is not a concern, I'd rather have the compatibility. However, watchOS 6 is the last version to require the Storyboard architecture with an app bundle and extension target. I did some research and found out that you can create that and set the development target to 6.0 while also having a SwiftUI target with a development target of 7.0. That would have the benefit of being able to use SwiftUI for modern features to give a nice experience while building a basic but functional version for 6.0 in Storyboard architecture. And it would figure out what to install on its own based on the watchOS version. Now the problem is, in Xcode 26 I can't create a watchOS target with the Storyboard architecture anymore, the option is just not there. So to solve that, I installed Xcode 12 on Big Sur and created one from the template in a new project. That project can be opened and edited with no problems in Xcode 26 as long as it is already configured, you just can't create a watchOS target with that architecture anymore, it has to be there already to work with it. Now I just need to copy the app and extension target with the corresponding files and configuration to my other project, and that is the problem. I can't seem to find proper way to copy that over, and that is where I need your help. Or maybe someone has a way to create that in Xcode 26, but from my understanding the template is gone. Thanks so much in advance

Hello, my name is Kanazawa Kenta, and I am a university student currently conducting research and development using visionOS. In my project, I would like to access the main camera using the Enterprise APIs for visionOS. However, when I try to request permission or view the documentation, I receive the following message: "Your account can’t access this page. There may be certain requirements to view this content. You must be the Account Holder of an Apple Developer Program for Organizations or an Apple Developer Enterprise Program to view this page." I am currently enrolled in the Apple Developer Program as an Individual. My question is: Is it possible to use the Enterprise APIs with an individual developer account? If not, what are the available options for students or researchers who wish to use these APIs for academic purposes? I would greatly appreciate any guidance or suggestions on how I can gain access, or alternative ways to use the main camera for research in visionOS. Thank you for your help. Best regards, Kanazawa Kenta

With the latest (26) version of Apple's developer tools, is there a way to manually attach a debugger (other than lldb) to an iOS app launched with "devicectl device process launch --start-stopped"? In the past, this was possible via the ios-deploy third-party tool (now defunct), which provided a debugserver port. This information is notably missing when using devicectrl – although the process ID of the launch process is provided, and the tool is clearly aimed at letting you launch and attach to processes from the command line. lldb can, of course, attach via its built-in support for this using the device set of commands. But I'm explicitly looking for a way to attach my own debugger via the GDB-compatible debug proxy.