Developer Forums

RSS for tag

Ask questions about how to use the Apple Developer Forums. Discuss forums bugs and enhancements requests that you’ve filed via Feedback Assistant.

Post

Replies

Boosts

Views

Activity

DevForums Improvements 2024-06-07
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"
2
3
805
Jun ’24
What’s New with Apple Developer Forums
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 ✨
5
4
1.3k
May ’24
Tips on writing forums posts
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.
0
0
586
May ’24
Apple Developer Forums post is not published
■Confirmation My post on the Apple Developer Forums is not published even though it have been reviewed. Does any work need to be done at the time of submission or after review in order to be published? ■Background of the question I posted one on the Apple Developer Forums yesterday. Immediately after posting, a message saying "It will be published if it passes the review" was displayed on the screen. This morning, that message disappeared, so I thought the post had been published, but my post was not displayed on the post list screen. I tried searching for the post title, but it doesn't appear for a while.
3
0
755
May ’24
Test
This is a testing thread to try attaching crash report that was unable to be attached few days earlier when I tried to create a new thread. This test is requested by Apple DTS to help isolating the issue. For more context: https://forums.developer.apple.com/forums/thread/747480 Crash report: crash-log-iOS-17.crash
2
0
736
Mar ’24
Problems attaching crash reports?
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"
15
0
1.5k
Feb ’24
New 'Same Here' button on the forum
I've noticed there is a new 'Same Here' button showing on any post (except your own posts). I first thought it was a link to a similar question… Specially when the button just says 'Same here' without any badge value. But no, it is just similar to a like… I guess the goal is to avoid and speed up instead of posting a reply or a comment 'Same here'. Unfortunately, it is not possible to undo and no way to know who posted. As your own posts do not show the button, does it mean you cannot know how many share the same issue than the one you posted ? If so, that's bizarre. Hope it will show the counter at least when it is non zero. Let me see how many 'Same here' on this post… .
5
1
1.1k
Feb ’24