I am Developer of SMCB ANAND Application, my Apple Developer Program membership had been expired in September 2024. I observed that expired in November 2024. Since that time i couldn't able to renew Apple Developer Program membership. I went through Apple Developer app for renew the membership but still i couldn't renew it Kindly provide a solution for the same

So I got charged the annual developer fee on December 2024, and then again this February 2025. Worse, a few days after getting charged twice, I received an email from Apple saying my developer account subscription has been suspended due to failure in paying the annual fee. I already submitted a support ticket to Apple, but I haven't gotten a response yet. Is there something else I can do? Would appreaciate any help. Thanks!

I already asked this, although I want to ask again so it boots and gets more people; When I try to run my project on the simulator, it tells me there is a bug. It is not in the code I wrote, but I believe in the compiler. It would work perfectly, say the build succeeded, but the phone turns white and stops there. I don't know how to debunk it, what to do! Picture of what happens with the phone: Picture of the debugging area: Picture of my code: If I need to add more things, please let me know. Have a great day!

I am facing a problem. I have enrolled developer program on 7th may, 25. It says will take 2 days but I haven't received any confirmation. Again I submitted information on 11th February, 25 but still haven't received any email about confirmation or rejection. I tried to contact apple support. They created ticket for me. But haven't received any further information from them. It seems like I am a ghost and apple is not seeing me. Can anyone tell me what is the problem. Thank you

After changing the bundle identifier of my app, I’ve encountered several issues that I can’t seem to resolve, even though I’ve followed all the necessary steps. The app with the previous identifier was live on Testflight, and working perfectly fine, but now I’m facing the following problems: WeatherKit Authentication Issue WeatherKit has stopped working, and I’m getting authentication errors. I’ve updated the app in the Developer Portal to reflect the new bundle ID, but it still doesn’t authenticate properly. Xcode Cloud Configuration Issue: Xcode is asking me to set up Xcode Cloud again, which I understand is expected after a bundle ID change. However, during the setup process, it fails to recognize my remote repository, even though the repository is correctly added and visible under the Source Control tab. TestFlight Internal Testing Issue: I manually uploaded a build to TestFlight, but internal testers cannot use it because the invitation appears as invalid. This wasn’t an issue with the app’s previous identifier. It seems like the bundle ID change has caused some fundamental issues that I can’t resolve despite following all the usual instructions. Has anyone experienced this before or knows how to resolve these problems? I'm using the latest Xcode 16.2 on Mac OS Sequoia 15.2

I have been trying to enroll for the Apple developer program for almost a year now but Apple has been deliberately frustrating my efforts despite providing every requested information and ID. I have provided every single detail and have gotten to payment/purchase twice but Apple refused to debit/process my payments on both occasions. The latest being last week. I have successful $0.00 test transactions from Apple proving that my payment card is valid on Apple. There really isn't any excuse for not allowing me to complete purchase. After that, Apple disabled my enrollment on the web and directed me to restart on the developer mobile app which I still complied with. Yet, after uploading my ID via a link that was sent to me by a certain Jenny from Developer support (eurodev@apple) and filling in my address hoping to finally proceed to purchase, Apple has disabled my enrollment and I see the message "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time." The web option has also been disabled. No message or explanation was provided. Developer support and Apple support have refused to respond to my many mails since then. It's almost as if they were not expecting me to meet their requirements as EVERY SINGLE STEP has been met with some sort of restriction. I have successfully created and uploaded apps on the Google PlayStore till date using the same details without any hassles. I have no criminal records nor restrictions against my person and neither did Apple indicate anything that could prevent my enrollment so this treatment is distasteful. I believe Apple discriminates against locations because I am African. I doubt if US or European applicants face this type of discriminatory treatment from a supposed multinational corporation. I am not the only African complaining about this treatment too. It is sad because Apple generates revenue from Africa but does not consider us to be relevant enough. Shameful.

I am trying to name my app "Tata Daewoo Mobility Service" but in app showing without space like 'TataDaewooMobilityService. In korean language not showing the space. How to add the name in korean language with space in iPhone.

I don't want to throw anyone under the bus here, but I think the error handling for the D-U-N-S number verification step could be improved. Shown on page: The information you entered did not match your D&B profile. Before submitting your information, check your D&B profile. If you've recently changed your legal entity name, update your D&B profile. This message is confusing when the only information provided is the company name, which exactly matches the D&B profile. We get more information about the error in console than what is shown on the page: "resultCode": 20010, "resultString": "Your organizations information is not complete.", "userString": "Your organizations information is not complete.", "requestUrl": "https://developer.apple.com/services-enrollment/validateDunsDetails", Displaying a clearer error message in line with this would greatly improve user understanding of what went wrong.

I have the 'warnings as errors' policy set to Yes for Apple Clang and Swift compiler. As far as I know, there is no way to make exceptions to the warning policies from Swift compiler (correct me if I am wrong), what about Clang warning policies, specifically when it comes to header files from 3rd party pods? They don't show up on the Compile Sources so I can't apply flags such as -Wno-error=deprecated to them. Adding #pragma GCC... to them won't help as a fresh pod install will wipe the #pragma statements out. Is there a way to exclude the header files from pods from getting the warning policies from Clang so I won't see errors from them when compiling Clang modules that's a part of the build process?

Dear Apple Support Team, I am Tianwei Yue. I received your email this morning regarding the immediate termination of our Apple Developer Program License Agreement and Apple Developer Agreement, citing alleged fraudulent behavior and violations of certain terms. We are both surprised and deeply anxious about this decision. Firstly, the email mentioned that if we wish to file an official complaint under the applicable Platform Regulation, we could contact you via “Contact Us”. However, when I logged in with my account and clicked the “Contact Us” link, the system responded with “You’re not eligible to make this request.” We would appreciate guidance on how to properly submit an official complaint or if there is an alternative way to reach out for assistance. Secondly, I would like to emphasize that the “mathos ai” application operated under this account currently has over 3 million active users. Our application has consistently maintained a high user rating of 4.6 and a record of excellent service. The immediate deletion of our account has rendered the service inaccessible to a large number of customers who use Apple products, severely impacting their experience. We believe that this decision does not align with the shared values of customer care that both Apple and we have always upheld. We have always been proactive in handling user accounts, refunds, and payment issues, and we continuously strive to provide high-quality service to our users. Consequently, we are puzzled by the reason for the account suspension and believe that there might be some misunderstanding or miscommunication. We sincerely hope to connect with the relevant Apple personnel to understand the issue in detail and provide any necessary additional information to resolve any concerns and restore our service. Thank you very much for taking the time to read our email. We look forward to your prompt response so that we can resolve this issue and jointly safeguard the interests of our valued customers. Sincerely, Tianwei Yue

Like the title says, I'll commit some changes no problem with my Git name and email displayed properly, then work for a while longer and when use the integrate menu to stage and commit I find the git name/email are empty. My credentials are properly entered in settings. The only fix i've found is quitting and restarting. Any less frustrating option?

I have a warning on my AR app Virtual Tags that since July does not show its camera information telling: "ARCL.SceneLocationView implements focusItemsInRect: - caching for linear focus movement is limited as long as this view is on screen." I tried inserting the function, but documentation does not explain what it should return and how to generate it. Is someone able to help me? Thanks,

Is there any way to modify the behaviour of this command? I really dislike that it adds a break after the opening parenthesis and would also prefer it to use the traditional multi-line style where the lines are aligned with their semicolons. Alternatively, is there a way to run the "Format File with 'swift-format'" command without implicitly triggering "Format to Multiple Lines", as it apparently does? Having to reformat my method's signatures afterwards really makes this feature unattractive to me at the moment.

I'm trying to enrol in the apple developer program for the first time. When I sign in and attempt to enrol, it says “Your enrollment could not be completed.” - I am over the Age of 18 in Australia. My account is attached to a family account if that matters, but I am an Adult in the family. As far as I am concerned I have not done anything illegitmate on my account. My AppleID has always paid ontime etc. Just spoke to someone on the phone at Apple Developer Support. Firstly they were very unfriendly, don't know their name and sounded like they didn't want to be there. I said what my issue was, they had a look at my account and said "It says there is an issue with this apple ID and Support cannot be provided within Apple Developer Program for this AppleID" - I asked if this could be escalated and she audibly sighed and said "No" - I said may I speak to a supervisor - Spoke to the Supervisor and they said they can't help me and it just says We can't provide Apple Developer support to this AppleID and he kept repeating this. - I have not done anything illigetimate on my AppleID as far as I know. He also said can't verify my identity, even though I have never verified my identity. What do I do?

I regularly see questions from folks who’ve run into problems with their third-party IDE on macOS. Specifically, the issue is that their IDE is invoking Apple’s command-line tools — things like clang and ld — and that’s failing in some way. This post collects my ideas on how to investigate, and potentially resolve, issues like this. If you have any questions or comments, please put them in a new thread here on DevForums. Tag it appropriately so that I see it. Good tags include Compiler, Linker, LLVM, and Command Line Tools. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Investigating Third-Party IDE Integration Problems Many third-party IDEs rely on Apple tools. For example, the IDE might run clang to compile C code or run ld to link object files. These IDEs typically don’t include the tools themselves. Rather, they rely on you to install Xcode or Apple’s Command Line Tools package. These are available at Apple > Developer > Downloads Occasionally I see folks having problems with this. They most typically report that basic stuff, like compiling a simple C program, fails with some mysterious error. If you’re having such a problem, follow the steps below to investigate it. IMPORTANT Some IDEs come with their own tools for compiling and linking. Such IDEs are not the focus of this post. If you have problems with an IDE like that, contact its vendor. Select Your Tools macOS has a concept of the current command-line tools. This can either point to the tools within Xcode or to an installed Command Line Tools package. To see which tools are currently selected, run xcode-select with the --print-path argument. This is what you’ll see if you have Xcode installed in the Applications folder: % xcode-select --print-path /Applications/Xcode.app/Contents/Developer Note All of the tools I discuss here are documented in man pages. If you’re not familiar with those, see Reading UNIX Manual Pages. And this is what you’ll see with a Command Line Tools package selected. % xcode-select --print-path /Library/Developer/CommandLineTools There are two common problems with this: It points to something you’ve deleted. It points to something unexpected. Run the command above to see the current state. If necessary, change the state using the --switch option. For example: % xcode-select --print-path /Applications/Xcode.app/Contents/Developer % clang -v Apple clang version 14.0.3 (clang-1403.0.22.14.1) … % sudo xcode-select --switch ~/XcodeZone/Xcode-beta.app % clang -v Apple clang version 15.0.0 (clang-1500.0.38.1) … I have Xcode 14.3 in the Applications folder and thus clang runs Clang 14.0.3. I have Xcode 15.0b5 in ~/XcodeZone, so switching to that yields Clang 15.0.0. It’s possible to run one specific command with different tools. See Select Your Tools Temporarily, below. Run a Simple Test A good diagnostic test is to use the selected command-line tools to compile a trivial test program. Consider this C [1] example: % cat hello.c #include <stdio.h> int main(int argc, char ** argv) { printf("Hello Cruel World!\n"); return 0; } % clang -o hello hello.c % ./hello Hello Cruel World! IMPORTANT If possible, run this from Terminal rather than, say, over SSH. You may need to expand this test program to exercise your specific case. For example, if your program is hitting an error when it tries to import the Core Foundation framework, add that import to your test program: % cat hello.c #include <stdio.h> #include <CoreFoundation/CoreFoundation.h> int main(int argc, char ** argv) { printf("Hello Cruel World!\n"); return 0; } When you compile your test program, you might see one of these results: Your test program compiles. Your test program fails with a similar error. Your test program fails with a different error. I’ll explore each case in turn. [1] For a C++ example, see C++ Issues, below. If your test program compiles… If your test program compiles from the shell, that proves that your basic command-line tools setup is fine. If the same program fails to compile in your IDE, there’s something IDE-specific going on here. I can’t help you with that. I recommend that you escalate the issue via the support channel for your IDE. If your test program fails with a similar error… If your test program fails with an error similar to the one you’re seeing in your IDE, there are two possibilities: There’s a bug in your test program’s code. There’s an environmental issue that’s affecting your command-line tools setup. Don’t rule out the first possibility. I regularly see folks bump into problems like this, where it turns out to be a bug in their code. For a specific example, see C++ Issues, below. Assuming, however, that your test program’s code is OK, it’s time to investigate environmental issues. See Vary Your Environment, below. If your test program fails with a different error… If your test program fails with a different error, look at the test program’s code to confirm that it’s correct, and that it accurately reflects the code you’re trying to run in your IDE. Vary Your Environment If your test program fails with the same error as you’re seeing in your IDE, and you are sure that the code is correct, it’s time to look for environmental factors. I typically do this with the steps described in the next sections, which are listed from most to least complex. These steps only tell you where things are going wrong, not what is going wrong. However, that’s often enough to continue the investigation of your issue. Vary Your Shell Try running your commands in a different shell. macOS’s default shell is zsh. Try running your commands in bash instead: % bash … bash-3.2$ clang -o hello hello.c bash-3.2$ ./hello Hello Cruel World! Or if you’ve switched your shell to bash, try it in zsh. Vary Your User Account Some problems are caused by settings tied to your user account. To investigate whether that’s an issue here: Use System Settings > Users & Groups to create a new user. Log in as that user. Run your test again. Vary Your Mac Some problems are system wide, so you need to test on a different Mac. The easiest way to do that is to set up a virtual machine (VM) and run your test there. Or, if you have a separate physical Mac, run your test on that. Vary Your Site If you’re working for an organisation, they may have installed software on your Mac that causes problems. If you have a Mac at home, try running your test there. It’s also possible that your network is causing problems [1]. If you have a laptop, try taking it to a different location to see if that changes things. [1] I rarely see this when building a simple test program, but it do see it with other stuff, like code signing. C++ Issues If you’re using C++, here’s a simple test you can try: % cat hello.cpp #include <iostream> int main() { std::cout << "Hello Cruel World!\n"; } % clang++ -o hello hello.cpp % ./hello Hello Cruel World! A classic problem with C++ relates to name mangling. Consider this example: % cat hello.c #include <stdio.h> #include "hello-core.h" int main(int argc, char ** argv) { HCSayHello(); return 0; } % cat hello-core.cpp #include "hello-core.h" #include <iostream> extern void HCSayHello() { std::cout << "Hello Cruel World!\n"; } % cat hello-core.h extern void HCSayHello(); % clang -c hello.c % clang++ -c hello-core.cpp % clang++ -o hello hello.o hello-core.o Undefined symbols for architecture x86_64: "_HCSayHello", referenced from: _main in hello.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) The issue here is that C++ generates a mangled name for HCSayHello: % nm hello-core.o | grep HCSayHello 0000000000000000 T __Z10HCSayHellov whereas C uses the non-mangled name: % nm hello.o | grep HCSayHello U _HCSayHello The fix is an appropriate application of extern "C": % cat hello-core.h extern "C" { extern void HCSayHello(); }; Select Your Tools Temporarily Sometimes you want to temporarily run a command from a particular tools package. To continue my earlier example, I currently have Xcode 14.3 installed in the Applications folder and Xcode 15.0b5 in ~/XcodeZone. Xcode 14.3 is the default but I can override that with the DEVELOPER_DIR environment variable: % clang -v Apple clang version 14.0.3 (clang-1403.0.22.14.1) … % DEVELOPER_DIR=~/XcodeZone/Xcode-beta.app/Contents/Developer clang -v Apple clang version 15.0.0 (clang-1500.0.38.1) … Revision History 2025-01-27 Remove the full width characters. These were a workaround for a forums platform bug that’s since been fixed. Made other minor editorial changes. 2023-07-31 First posted.

I'm facing an issue with revoking an iOS Development certificate in the Apple Developer Console. The certificate is in "Pending Approval" status, and when I attempt to revoke it, I receive the following error: "The specified resource does not exist. There is no certificate with ID 'XXXXXXXXX' on this team." Despite this error, the certificate still appears in my list, and the only available action remains "Revoke." Steps I've tried so far: Refreshed the page and cleared the browser cache Logged out and back into my Developer account Tried using different browsers (Safari, Chrome) Checked Xcode &gt; Preferences &gt; Accounts for certificate status Contacting Apple Support (Not response since over 3 weeks) Additional Info: The certificate type is iOS Development, not Distribution. The status has been "Pending Approval" since creation.

Hello everyone =) I'm working at the moment on a project in Xcode 16 where I need to have multiple files with the exact same name, stored in different folders (for example, separate quest data files). When I compile, Xcode seems to treat these identically named files as duplicates, causing build errors. How can I properly organize (or configure) Xcode so that it recognizes these files as distinct? Any advice or best practices would be greatly appreciated. Thank you! ;)

Hi everyone, I’ve been experiencing a persistent issue with my MacBook Pro (M2 Pro, macOS 15.2) when using Xcode (version 16.2). If Xcode is open and my Mac goes into sleep mode, the screen size changes upon waking. Specifically, I notice 3mm bezels appear on each side of the screen, making the display slightly smaller, and everything scales down to fit this reduced size. This issue happens multiple times a day and has been ongoing for over a year. It’s quite disruptive to my workflow. Here is a video to illustrate the problem: Has anyone encountered this before? If so, do you have any suggestions for fixing it or steps I can take to debug the issue? Thanks in advance for your help and support!

Dear Team, I was previously able to access a non-secure HTTP API in my Ionic-built app. However, I am now encountering an error where the API requests are being rejected. Interestingly, this API works perfectly on Android and web platforms without any issues. As part of my troubleshooting, I have already added the following lines to my Info.plist file: <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key> <true/> </dict> Could you kindly suggest any alternative solutions or additional settings required to access this HTTP API? Your help would be greatly appreciated. Thank you, Mozib

Hello, I am doing the SwiftUI tutorial with Xcode 16.2 For the watch app the simulator working fine but the preview keep saying “This app cannot run on the selected target device.” while the preview is working …… For the macOS part the simulator working fine but the preview is totally broken with -> ”ContentView.swift” not found in any targets. While it is correctly added to the target … Please fix or make tutorial clear.