How to remove answered mark

The "Save" or "Update" button text does not load properly. https://developer.apple.com/profile/finish

... and yet, Apple's staff think it's appropriate to post lame responses thanking them for their interest in the forums. Come on, guys! It's obvious spam! Mark it as such and delete it. It's not beyond your abilities to stop people posting the word "WhatsApp" plus a phone number. You already stop us posting certain web links, so you can do this. If you continue ignoring the spam problem, then these forums will become less and less useful. Why should I contribute my free time to help others when you won't even help us?

I would like to delete this post, but I can't. Please add this fundamental feature.

Hello, I tried posting about an issue I'm experiencing with HCE, and no matter the text I type, I get error "This post contains sensitive language. Please revise it in order to continue." Is there any option to resolve it?

It would be helpful to have an option for filtering searches on the Developer Forums by date created or date of last activity. FB21588346 https://github.com/feedback-assistant/reports/issues/742

I watch some topics in the developer forums and when those topics are updated, I receive email notifications. That notification contains a link with the text "View the thread" which I believe is meant to take you to the corresponding latest reply in that topic. For example, I was watching this thread https://developer.apple.com/forums//thread/792453 and when the latest reply there was posted to I received the notification with the "View the thread" link which pointed to https://developer.apple.com/forums//thread/792453?answerId=872080022&replyId=872080022. However, clicking on that link redirects me to the login page. I think it would be better if that link was https://developer.apple.com/forums//thread/792453?answerId=872080022#872080022 which would have taken me to the appropriate reply without forcing a login. Is that something that can be considered?

Nothing ever shows in my "Watching" tab. I've tried toggling the watch (bell) button on & off for threads I'm trying to watch, but this doesn't help. The setting sticks per thread, meaning that if I start watching a thread and reload the page, the icon shows as filled. These threads just never show up in the "Watching" tab for me. The only thread I saw mentioning this is from 2021 (https://developer.apple.com/forums/thread/681641). Starting a new thread since that was was marked as answered.

Hello, I need some assistance with changing my Dev Forum username. I am no longer associated with the company/organization that my username is presenting

Issue solved. Retracting question.

Hello, I notice the link on top of this site is incorrect: https://developer.apple.com/forums/tags/sign-in-with-apple-rest-api Its target (https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_rest_api) does not exist. It should probably be https://developer.apple.com/documentation/signinwithapplerestapi

This is supposed to be a photo of a screen shot I took of this site and this box saying there is no text it is empty when I tried to post my previous post And the box was not empty and the character counter was backwards it was in the negative -. Was -6870/7000 characters. The original post was for a force reset analytic that I found suspicious and malicious towards my device and apple. will not let me post the image

My original thread ID was: https://developer.apple.com/forums/thread/805350 This was a technical post with no links to products or services, but directly to native code designed to solve the problem I was posting about. I believe a single unhappy user may be abusing the flagging/reporting feature. I am contesting what this single user has alleged, namely that my content is “advertising.” Under my rights as per the Apple Developer Forums Agreement, I am requesting a review per Apple’s right to monitor and correct moderation actions. Thank you.

The "Remind me later" button doesn't work on the "Customize your experience with Apple Developer" page on the Developer Forums. It just redirects me back to the same page. https://github.com/feedback-assistant/reports/issues/723

It would be helpful to be able to upload short videos to the Developer Forums. FB21241023 https://github.com/feedback-assistant/reports/issues/725

Dragging and dropping images to forum posts doesn't work. It just inserts text with the image file path. FB21252859 https://github.com/feedback-assistant/reports/issues/726

I used to resize images (editing width and height when writing the post) in order to avoid ridiculously large images in reading published post. Since a few weeks, that does not work anymore. When I edit, I see the reduced size in Live Preview: But once posted, images are much larger as seen below: Looks like the image is now resized to fill full width. I filed a bug report: Dec 27, 2025 at 1:43 PM – FB21446929 PS: that change ignores @eskimo wise advice "Quinn’s Top Ten DevForums Tips" n°10 (https://developer.apple.com/forums/thread/706527).

Currently when searching on the Apple Developer Forums it shows the current page number but doesn't show how many pages of results there are total. It would be nice if it also showed the total number of pages of results. FB21655261 https://github.com/feedback-assistant/reports/issues/744

Thanks for your engagement, participation, and contributions to the Apple Developer Community! We’ve made some minor updates today to the Forums - curious about what’s changed? Here’s the rundown: Customize your experience with a developer profile Creating a developer profile allows you, if you choose, to share your interests and preferences so we’re better able to support you. In Developer Forums, creating a profile and choosing to share it publicly is an easy way to connect with fellow developers. Soon, having a profile will help unlock a more personalized experience across developer.apple.com - powering smarter surfacing of recommendations, activities, and opportunities tailored to your interests. Learn more. Other features and improvements With this release, we’ve also made some enhancements and fixed a few bugs based on feedback you’ve submitted. These include: Expanded save draft functionality from posts to replies so you don’t lose those drafts unexpectedly Added line numbers in code blocks Restored text highlighting back to system default Syntax coloring carries through to code blocks within posts Fixed a time stamping issue which was impacting ‘last updated’ sort functionality Wish there was a feature or improvement on Developer Forums? We welcome feedback and feature requests.

I file a lot of bug reports. I also ask a lot of third-party developers to file bug reports about problems they see. This post is my attempt at collecting together some hints and tips about Apple’s bug reporting process. To file a bug report, use Feedback Assistant. To file an enhancement request, use Feedback Assistant. In the “What type of issue are you reporting?” popup, choose Suggestion. If you’re filing a bug against an API, choose Developer Technologies & Resources at the top level. The technologies popup should then list familiar items, from Accelerate Framework to XPC. If you can’t find the correct item, select “Something else not on this list”. Feedback Assistant is both a website and an app. For details on how to access the app, see Opening the app on the Developer > Bug Reporting page. For lots of great hints and tips about filing bugs, see File effective bug reports. I may repeat some of the info covered by that article, but only where I think it’s particularly important. After filing a bug report, please include the bug number in your DevForums post. Feedback Assistant shows the bug number in both the bug list and the bug detail view. Bug numbers start with FB and continue with a sequence of digits. For example, a recent bug report posted here on DevForums was FB11357055. Including the FB prefix avoids any confusion as to what type of bug number this is. Occasionally you’ll see other types of bug numbers. In release notes they are just in parens, so (99071807), and in DTS documents they have an r. prefix, so (r. 99071807). These are Radar numbers. Radar is the internal bug system here at Apple. Other developers can’t see your bug report. However, posting the bug number is still important for a couple of reasons: It allows Apple folks to quickly track down your issue. If another developer wants to file a related bug, they can reference your bug number in their bug report. You can share bug reports with other members of your team. For details on how to do that, see Collaborating with your team on the Developer > Bug Reporting page. Otherwise you can’t see a bug report filed by another developer, or one filed internally at Apple. One option here is to file your own bug and request that it be marked as a duplicate of the original bug. You’ll then be notified when the original bug is closed. The File effective bug reports article discusses the importance of including a sysdiagnose log with your bug report. I have a few additional tips: Include a sysdiagnose log from the machine that’s having the problem. Sometimes I see folks with an iOS problem include a sysdiagnose log for their development Mac )-: Include a sysdiagnose log even if you attach a test project that reproduces the problem. The contents of the log help with screening, making sure that your bug gets to the right person quickly. And that person will be very grateful to have your test project! If multiple machines are involved — for example, you’re reporting a Handoff problem — include a sysdiagnose log from each machine. Trigger the sysdiagnose log as soon as possible after you see the problem. The sooner you trigger the log, the more likely it is to capture relevant info. If the problem is hard to reproduce, see Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem for hints on how to capture an actionable sysdiagnose log. If you install a debug profile, install it before you reproduce the problem. These profiles typically enable more logging, and you want that logging to be active at the time of the problem. Most profiles activate immediately but some require that you restart. Follow the instructions that came with the profile. When reproducing the problem, make a rough note of the time and include that in your bug report. This doesn’t have to be super precise. Just note down the time, with seconds, shortly after you reproduce the problem. If the bug involves a crash, reproduce the crash outside of Xcode and then take your sysdiagnose log. This means running your code as the user would, so running an app from the Finder on macOS, running an app from the Home screen on iOS, and so on. If you reproduce the crash inside Xcode, the Xcode debugger catches the crash and prevents the system from generating a crash report to include in the sysdiagnose log. File focused bug reports. Imagine you’re seeing two problems, A and B, related to the same API. Don’t file a single bug that covers both A and B. Rather, file separate bugs for A and B. Feel free to reference your A bug in your B bug, and vice versa. Finally, some personal notes: DevForums is not an official support channel. Mentioning a problem here is not the same as filing a bug about it. That’s true even if you’re discussing your issue with an Apple person. Apple is a big company, and it’s very unlikely that the person you’re talking to is directly responsible for fixing your bug. Historically I used to post a lot of Radar links, of the forms rdar:nnn, where nnn includes the bug number. I no longer use these links because I’ve found that they confuses folks. They click the link and wonder why it does nothing. If you post an FB number here, DevForums automatically turns it into a link. However, that link is only useful to you. Other folks can’t access the bug via that link. I’ve filed a bug against DevForums requesting that it only generate this link for the bug’s originator (r. 92946014). In the meantime, I work around this by putting FB numbers in code style, which disables this link generation. If you want to share bug information outside of DevForums, one popular option is Open Radar (https://openradar.appspot.com/). Apple uses a lot of open source and many open source projects maintain their own bug tracker. Two big examples are Swift and WebKit. If your bug originates in such an open source project, consider filing it in the project’s bug tracker. You can then go on to submit a pull request with the fix (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History 2025-08-07 Updated “Developer Technologies & SDKs” to “Developer Technologies & Resources”. 2024-03-07 Made minor editorial changes. 2023-10-26 Added a link to Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Added a recommendation to file focused bug reports. 2023-06-28 Updated the advice on how to file an API-level bug based on recent changes to Feedback Assistant. Corrected some link titles. 2023-03-21 Added a bunch of bullets to the personal notes section. 2023-03-13 Extended the discussion of seeing other folks’ bugs to make it clear that you can’t see bugs filed internally at Apple. 2022-12-13 Added advice about the “Something else not on this list” option. 2022-09-01 Added a personal notes section at the end. Added a new bullet in the sysdiagnose section about running your app outside of Xcode. Made other minor editorial changes. 2022-08-29 Added a note about filing duplicate bugs. 2022-08-24 First posted.