Thanks so much for contributing to Apple Developer Forums. We'd love to help you get an answer, but we need a little bit more information from you first. Here's some tips on what to add to your post in order to help us help you. Provide context to your post Did you provide enough context of when and how this issue is occurring? Things like platform and Xcode version and language can go a long way. Posting items like the version can also help you to remember to test on the latest software. If it's a bug that you're noticing, it may have been fixed in a recent update. Avoid stating that you're using the "current version" since these change quickly. Example to improve on: Current iOS, Swift Better example: iOS 17.5, Swift (UIKit) Best example: iOS 12 - iOS 17.5, Swift (UIKit), Xcode 15.4 Specific questions to answer: What platform are you targeting? And what version of that platform? What version of Xcode are you using? What version of the OS are you testing on? Add test code Check that it's as easy as possible for someone to reproduce your issue. If you've asked a question along the lines of: "Why isn't ##INSERT_ACTION_HERE## working?", test code can go a long way. If you're posting a link to a project, be sure that it's a newly created project created from one of Xcode's templates that's stripped down to the bare minimum amount of code and files needed to reproduce the issue. Remove any third-party dependencies to focus your project completely on Apple's APIs. See Creating a Test Project for more details. If you're posting a code snippet, make sure you've posted enough context so that someone helping you can copy the code into their own project without having to read between the lines on the rest of your project. Also, make use of the Code Block button, which inserts triple backquote delimiters, for code snippets or logs. Example of code block formatting. Give a thorough description Don't forget to add a detailed description to your post. If you only posted code, or have a minimal description, please add some details to describe your issue and, if applicable, steps needed to reproduce it and what you've tried. Specific questions to answer: What specific API are you using? What are the exact steps you took? If nothing failed, what results did you see? And what were you expecting? If you filed a bug, what was the bug number? What else have you tried? Describe any errors If you're seeing an error message, post the exact wording or a screenshot. If it results in a crash, attach the crash logs to your post. Specific questions to answer: If something failed, what are the symptoms of that failure? If an API returned an error, what was that error? Re-read the post Come back to your post as if you'd never seen it before. Pretend you're going to answer it and think about what it may be missing, even if it wasn't mentioned in the above list. Any of this information, the more the better, is helpful to someone reading your post for the first time. A detailed description goes a long way in getting more detailed answers. These tips should result in some more helpful answers from us and the developer community! Revision History 2024-05-29 Initial version.

Users can upvote their own posts, yet they don't by default upon posting them. Reddit, for comparison, continues to allow users to remove their own-post upvotes, but upvotes them for the user by default. Other forums like Stack Overflow disallow own-post upvoting. This forum has the worst of both worlds, for users can gain an algorithmic advantage by upvoting their own. It might seem like a minor issue, because it is. But it's an issue in my eyes regardless.

I've always thought that it just didn't work for me, because there was no feedback.

Posted in the wrong subtopic, and I can't figure out how to delete this post.

Is it only me ? I received recently a notification that an answer was "recommended by Apple", with a link to the post. But when going to the post, this recommendation (with small Apple icon) do not show. And the forum scores are not updated. This is not the first time I get problems with forum notifications. I filed a bug report: FB14172207

I'm trying to ask a (presumably) straight-forward question regarding some of the new features that were announced at WWDC. However, the website won't let me post, claiming my question "contains sensitive language", and asks me to revise it. Is it ok to ask questions about new features announced at WWDC or is this off limits? Is anybody else experiencing something like this? I'm confused about what could be wrong with my message.

I see this message for the first time: It is inserted in the OP (https://developer.apple.com/forums/thread/757852) but the link leads to nowhere (just the general page of the forum). In … what ?!? So I wonder what is the meaning of the message, its intent and use ? Or is it just a forum bug ? PS: surprisingly, this post appears in Forums general page (https://developer.apple.com/forums/latest), but not in forums feedback (https://developer.apple.com/forums/tags/forums-feedback) PS2: it appears, but after all the pinned messages which are older. Really confusing… I posted a bug report on this: Jun 23, 2024 at 9:29 PM – FB14024970

As the title suggests, Please someone at Apple add this feature on priority. This website is too bright for the eyes to read causing straining issues. Need complete dark mode asap. Thank you!

I'm in trouble in posting a question on SwiftUI forum. I had revised text and tried several times to post it, but it didn't work. There is nothing in my query that is remotely ‘sensitive’. I don’t know what to do next. Thanks in advance for any advice. Regards,

I have recently been added as an apple developer in an organization by our main developer. On my mac, within keychain access, I have two certificates, one under my name and one under the company name. Both are not trusted. I am not sure what steps I need to perform to get those certificates to be trusted. I suspect that maybe my account does not have the privileges required regarding generating trusted certificates despite me being a developer in the organization. I get the error mentioned in the title when trying to deploy my app on a real device for testing which I am convinced is tied to the fact that my certificates on my target machine are not trusted. All the solutions that I have read online have failed me and its quite impossible for me to proceed forward at this point without any assistance.

Please delete this one!

I've recently seen answers to posts that are apparently automatically generated but signed as App Store Connect Engineer. In several cases the answer is misinterpreting the OP. Here is an example: https://developer.apple.com/forums/thread/758391 The OP was really a developer question. Not related to a consumer feature. Is it really an automatic answer (which would be a bad trend for the forums IMHO)?

All-New Developer Forums"Connect with over 1000 Apple engineers and learn directly from experts. Redesign coming June 18."

Hear me out, developers at Apple! You've done an amazing job with privacy so far. The introduction of ContactAccess and the Contact Access Button this year is truly an amazing work of art. Well done. However, all the way back to the first iPhone I got in 2007, I wished Apple would make API's available to access the users installed apps (in a privacy way). This would (further) open up apps in the category of App Managers and App Launchers. Back in the early days the trick was to use deep link, but that was also awkward, since you needed to know the deeplink upfront and the apps needed to support it. Not ideal. It also had a side effect that Apple noticed, that evil party's used it to scan your device to know which apps you had installed and create a profile from that. Apple fixed that by using LSApplicationQueriesSchemes. Now you have to tell the App upfront which apps you will be calling (up to 50), or use Universal Link to be freed from this limitation again. Again not ideal. Why not turn it around and let the user decide? User central. Imagine an App Launcher app. There is a button in the launcher app where you as a user can click on to add an app. It calls an api available from Apple to launch a privacy shielded sheet with the apps the user got installed on its device. These are not exposed to the launcher app. When the user clicks on the installed app (or apps) it likes to add, the launcher app will get identifiers to launch the app. That's it. This would be limited access, perhaps the api could also expose full access, so permission could be granted once and the app will get all identifiers available. The choice will be up to the user. One step further, but this would be more nice-to-have, is the ability to access meta data of the app, such as icon, title, last launched, app size, etc. This way App Launchers can make decisions such as putting the most recent launched app in front or App Managers can use this to decide which apps you are not using and can advise to remove them to clean up space. Love to hear everyone's opinion. So let it be the start of the discussion.

The Apple Developer Forums have been redesigned for WWDC24 to help developers connect with Apple experts, engineers, and each other to find answers and get advice. Curious on what’s changed? Here’s some insight into what's different: Hello Homepage, Hello Topics Content across forums has been reorganized into topics and subtopics, supported by tags. Doing this helps you hone in on specific areas of interest while also connecting the resources, tools, and content that are most closely related. We hope the new format simplifies your forums experience, and allows you to easily locate the information and guidance you need. Not into topics? Not a worry: we’ve kept the all-forums-posts view open just for you - on the “Latest” tab. The RSS subscribe feature remains as well - allowing users to pipe a particular forums topic, subtopic, or tag area directly into feeds. Fresh look, fresh features Forums have also been redesigned to simplify how information is presented, lighten the cognitive load, and improve visual cues to allow you to scan and sort posts quickly with helpful information. UI changes include: Structure and layout improvements that condense the way information is presented on screen to improve readability Improved visual cueing for posts with clearer Apple Recommended Responses and/or Accepted Answer icons and placement Threads now have a highly visible “Boosts” count which allows forums participants to enhance visibility of the post. New thread navigation floats along the side of a post while to keeping the “watch” and “reply” buttons always accessible and right on screen Backed by Apple Experts One of the biggest changes to the Apple Developer Forums is one you can’t see – yet. Behind the scenes is a robust set of tools supporting Apple teams who are here every day to answer your questions in more efficient ways. Apple Developer Relations and Apple engineering are joining forces to field your questions and work to solve your technical issues. You’ll have access to an expanded knowledge base and enjoy quick response times — so you can get back to creating and enhancing your app or game. Wish there was a feature or improvement on Developer Forums? We welcome feedback and feature requests. Welcome to the all new Developer Forums; we’re all in, and hope you’ll be too ✨

Overnight we rolled out a number of minor fixes to the DevForums platform. Thanks to those of you who spotted these bugs and reported them. Here are the highlights: The reply editor now expands to full width when you uncheck the Live Preview checkbox (r. 128882713). Fixed an issue that resulted in the onboarding tour showing up repeatedly (r. 128882936). Copying text no longer frames it as a quote (r. 128883038). To insert a quote into your reply, click the quote button next to the selection. We’ve improved the handling of very long lines in a code block 128883131). Added support for applefeedback: links (r. 129165197). Fixed a few bugs including several rendering bugs with hovering, comments, text selection, multi-paragraph comments, and the editor’s attachment menu (r. 128875241, 128953001, 129046050, 129043503, 128987536). And more! (r. 129094445, 128931034) Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

The UI of the forum is profoundly changed. For what benefit ? It seems forum is more and more painful to use at each major revamp. Is it only me who cannot see the improvements ?

I’ve seen a number of comments recently from folks who are unable to attach a crash report to their post. I’d like to gather some examples so that I can escalate this issue. If you’re affected by this, please reply here to let me know. Ideally I’d like that reply to contain a copy of your crash report. That’s problematic if you can’t post it! One workaround is to upload it to your favourite file sharing service and then post a link here. That’ll work as long as you post the link in the clear. See tip 14 of Quinn’s Top Ten DevForums Tips For general info on how to post a crash report, see Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

Create an Apple account for developers on the X platform

It looks like these new forums are based on the new Apple Support Communities code. I frequently post on ASC so I know what does and does not work there. I will focus on features that need to be imported from ASC and features that don't. Email notifications - Some people really like to work from e-mail notifications. ASC has notifications for participation, following, points, etc. Just make sure they always default to "OFF". Subscriptions - ASC already has this and is (in my opinion) the ideal way to find and respond to questions. Essentially, this is just searching on multiple tags. The subscriptions is an interface to let me define what tags I want to search for by default. Sorting - Primarily, we need to see messages sorted by descending timestamp. Sorting - I would like to be able to sort by both created or updated timestamps. Sometimes I want to see bona fide new messages. Searching - This is ASC's big weak spot. Search is virtually useless on ASC. You have to really tweak the "filters" to get anything useful out of it. Re-do this and then back-port it to ASC please. Threads - Thread view is all messed up. This thread (https://developer.apple.com/forums/thread/134075) is a good example. It seems to be organized hierarchically, with new replies to individual posts appearing immediately after the post being replied to. This is really confusing. Just order it by timestamp. ASC has a feature to automatically guess the target forum (tag in these forums) from the content of the question being asked. That would be useful here. Otherwise, you risk everything going into "iOS". Provide an easy way to see my own posts to see if anything has been updated. ASC doesn't really offer this. I have found a custom filter query that I use to simulate the "Inbox" of an old version of ASC. None of those custom filters seem to work over here. This is another opportunity to fix and then port back to ASC. Filtering - ASC has a complicated system of filtering. Please don't import that. 10. Subscriptions - If you do implement a subscriptions system like ASC, pay attention to unpopular forums. Otherwise, new question in popular forums will drown out questions in more specific forums. The "Top Tags" list has already started that. Of course "iOS" and "macOS" will be most popular. But if everybody uses only those tags, they become useless. Specialties - This is part of ASC gamification system. I don't necessarily mind them, but they aren't implemented very well on ASC. One has to perform specific actions, such as asking a question, to start earning a speciality. What about people who don't ask questions? How do you handle people with multiple specialties? ASC seems to pick one at random and display it, which is very annoying. Guidelines - I think the Terms of Use need to be expanded and be crystal clear about what is allowed and not. I've just seen my first help wanted ad here. Is that allowed? I don't know. Other comments: Very nice use of Markdown in the editor. This is probably not something that could be ported back to ASC. Developers should be able to handle it though. I like the documentation links at the top of tag results pages.