I spend a lot of time here on DevForums. Over the years I’ve read many posts, both good and bad. This page is my attempt at writing down what makes a good one. Hopefully some of you will find it useful. Before you read this, read the official Apple Developer > Support > Developer Forums page. If you have questions or feedback about any of the points raised here, start a new thread in the Developer Tools & Services > Developer Forums subtopic. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Quinn’s Top Ten DevForums Tips Here are my top ten DevForums tips: Is DevForums right for you? Search before you ask Keep your expectations realistic Topic, subtopic, and tags Craft a quality post Prefer text over images Include details with your questions Crash reports Cross posting courtesy Resize screenshots Include a Spinal Tap reference Close your threads Think about your title Post URLs in the clear Many of these boil down to one word: Empathy. Think about the person who’s reading your post. Can they read it? Will they understand it? Will it help them? 1. Is DevForums right for you? To quote Apple Developer > Support > Developer Forums, the Apple Developer Forums (aka DevForums) are: a great place to post questions, exchange knowledge, and connect with fellow developers and Apple engineers on a variety of development topics. DevForums is focused on developer issues. That includes the APIs in Apple’s platform SDKs, Apple tools, developer-oriented Apple services like App Store Connect, and accessory development. If you have a user-level question, you’ll have more luck over in Apple Support Communities, run by Apple Support. DevForums is focused on Apple technologies. If you’re using a third-party tool or library, feel free to ask questions about it here, but you’re more likely to find folks with relevant expertise in that technology’s dedicated support channel. If you want to file a bug report, do that using Feedback Assistant. If you want to discuss a bug you’ve already filed, DevForums is a great place for that. Make sure to include your bug number in your post. For more hints and tips on the bug reporting process, see Bug Reporting: How and Why?. 2. Search before you ask DevForums has a history stretching back to 2015. Many questions have been asked and answered here. Before you start a thread, search the forums for similar threads. For details about the search syntax, see Apple Developer > Support > Developer Forums. For a quick summary, click in the search field. Remember that DevForums is world readable and thus indexed by Internet search engines. 3. Keep your expectations realistic DevForums is an informal support channel; no one is being paid to answer DevForums questions full time. Keep that in mind when you post. Apple provides a number of formal support channels. To request formal support, go to the Apple Developer > Contact Us page. One of those support channels is the code-level support provided by Apple Developer Technical Support (DTS). For more information about DTS, see Apple Developer > Support > Requesting Technical Support. Asking about Apple’s unannounced plans is unlikely to yield useful results. Apple folks can’t discuss The Future™, and non-Apple folks can only speculate. Apple folks can’t discuss Apple’s internal business practices. For example, we can’t answer why question — “Why did Apple do this?” or “Why hasn’t Apple done that?” — unless there’s existing documentation that offers an explanation. If you think Apple should do something differently, file a bug that explains what you’d like to see change and the rationale for that. Not everyone works the same hours as you do. DevForums is a worldwide community, so there are time zones to consider, but there’s also just individual preferences. This is especially relevant around weekends, where your reply on Friday may not be seen by other folks until Monday. Different folks use DevForums in different ways. Some folks lean in to the notification system, whereas others allocate certain times of the day, or the week, to help out. 4. Topic, subtopic, and tags DevForums organises threads by two attributes: A high-level topic and subtopic A fine-grained set of tags Folks willing to offer help often monitor a specific set of subtopics or tags, and only see threads with those attributes. To increase the odds of getting a response, choose your subtopic and tags carefully. The list of subtopics is immediately visible on the top-level page. For a list of tags and their descriptions, go to Developer > Support > Forums Tags. That’s a lot of tags! When choosing a subtopic, choose the most specific one. For example, if you have a question about SwiftUI, choose UI Frameworks > SwiftUI rather than Programming Languages > Swift. The latter is primarily focused on the Swift language itself. When choosing a tag, read the description of that tag. With so many tags there are inevitably cases where a tag doesn’t mean what you think it means. For example, the Exception Handling tag is about the rarely used Exception Handling framework, not about exception handling in general, and the description makes that clear. 5. Craft a quality post When replying, use a reply rather than a comment. Comments are best reserved for short messages, like “Thanks!” or “See this other thread.” IMPORTANT If you reply in the comments, other folks on the thread may not be notified of your reply. DevForums supports Markdown formatting, similar to that used on GitHub and by DocC. The editor UI has buttons for the most common things, like Bold and Italic, but don’t feel the need to limit yourself to that. Correct formatting is particularly important for preformatted text: Use the Inline Code button, which inserts single backquote delimiters (```), for inline text in code style: identifiers and so on. Use the Code Block button, which inserts triple backquote delimiters (`````), for blocks of text in code style: code snippets, logs, and so on. After submitting your post, look it over to make sure that it reads well. If not, you have a short window where you can edit the post to fix things. 6. Prefer text over images Don’t use screenshots for data that’s essentially textual, like code snippets and logs. For example, if you want to post a log message, include that as text rather than adding a screenshot. That makes it much easier for your readers to work with the text. Use the Code Block button, which inserts triple backquote delimiters (`````), to format blocks of text in code style. Reserve screenshots for situations where the issue is visual, for example: When discussing view layout problems When posting instructions to achieve some task in a GUI app, like Xcode 7. Include details with your questions When starting a thread, try to include all the relevant details in your post. If you skimp on these details, folks will have to reply asking for them, and that slows things down. Specifically, anticipate the following questions: 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? What specific API are you using? What are the exact steps you took? If something failed, what are the symptoms of that failure? If an API returned an error, what was that error? If nothing failed, what results did you see? And what were you expecting? If you filed a bug, what was the bug number? Have you tried reproducing the issue in a small test project? What else have you tried? For more thoughts on this, see Tips on writing forums posts. Oh, and if you’re having a build problem, consider attaching a full build log. 8. Crash reports If you’re trying to get help with a crash, include a crash report. For advice on how to do that, see Posting a Crash Report. 9. Cross posting courtesy Don’t start multiple threads for the same issue. That just wastes everyones time. Sometimes this happens by accident. If that’s the case, add a comment to one of the threads redirecting folks to the other one. If you find a bunch of old threads that might be related to your issue, don’t post full replies to all of them. Pick a lead thread and post your full reply there, then reply on the other threads with a link to the lead thread. Alternatively, start a new thread and reply on all the old threads with a link to that. That’ll help focus the discussion on your specific issue. If you post your question to another support channel, provide a link to that in your DevForums question, and vice versa. That avoids folks working on a question that’s already been answered elsewhere. 10. Resize screenshots If your post includes an image, make sure it renders well. Screenshots from Retina displays are often ridiculously large. Use Preview to crop the screenshot and, if necessary, downsample it by 50% (using Tools > Adjust Size). 11. Include a Spinal Tap reference To be clear, this is a joke. While the occasional Spinal Tap reference is allowed, please don’t add one to all your posts (-: 12. Close your threads If someone replies with the answer you need, mark that as accepted. That gives them some credit and helps other folks with similar questions find that answer. If you find the answer by yourself, please post a short summary of what you did. Feel free to mark that as accepted. There’s no way to change the accepted answer. See this thread for specific advice. You can’t delete your own threads. If you accidentally post two copies of the same question, choose one as the primary and, in the other one, add a reply that links to it. Beyond that, see this thread for more advice. 13. Think about your title When creating a thread, think carefully about your title. Your title is your thread’s ‘marketing statement’, a way to entice folks to read your post. Try to summarise your issue in 15 words or less. Adding tags to your title makes it harder to read. Instead, add your tags with the tagging UI. See tip 4 for more on tags. 14. Post URLs in the clear DevForums has a list of websites you can link to at will. For example, it places no restrictions on links to Swift Forums. To link to a site that’s not on the allowlist, skip the Markdown link syntax and post your link in the clear. So, this won’t work: Apple is based in [Cupertino](https://www.cupertino.org). but this will: Apple is based in Cupertino. https://www.cupertino.org Revision History 2025-12-02 Tidied up and expanded tip 12. 2025-06-19 Made minor editorial changes. 2024-08-29 Added a link to Creating a test project. 2024-08-07 Add more hints to tip 7. 2024-05-27 Reworked tip 4 to account for the new topic and subtopic model. Made other minor editorial changes. 2023-11-16 Added a link to [Public and Private Tags][refPaPT]. 2023-02-22 Expanded tip 3. 2023-02-10 Added a note about why questions to tip 3 (another great suggestion from Scott). Added a link to Bug Reporting: How and Why?. 2023-01-09 Added a note about tags to tip 13. 2022-12-09 Expanded tip 12. 2022-08-22 Expanded tip 5 to explain why you shouldn’t reply in the comments. 2022-08-11 Expanded tip 9. 2022-06-17 Added tip 14. Updated the preamble to include a link to the main DevForums page. 2022-06-04 Added a discussion of unannounced plans to tip 3 (thanks to Scott). 2022-06-03 Added tip 13. 2022-05-24 Added tips suggested by Claude31 and Scott. 2022-05-23 First posted.

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

Hello, i had in 2023 active apple developer license and i created alpha version of my app, when test was concluded i didnt renew my subscription because i started to create my company. Fast forwarding 2 years i have company now and company has now apple developer license, i wanted to create app identifier and i found out that its taken and then i realized i left that app id on my personal account. So because of that i cannot create app id on company account. I contacted apple developer support on tuesday and didnt get any answer back. I Thought i did wrong topic, so i made another on wednesday and still nothing, replied to the 2nd case and nothing. I was simply asking to either transfer the app id to company account or remove it, so i can create it again on company account. Can someone tell me what i can do next to resolve it? I dont want to pay $100 just to remove app identifier. Application on my personal profile was never in AppStore, it only reached TestFlight. Case IDs: 102795542798 , 102795563781

I set up a sandbox account to test in-app purchases in my development app. I went to settings > dev > sandbox accounts and updated my login in the app store. But I received a 'block'; I can no longer download new versions or anything from the store. I've already removed the sandbox account, and even using my real Apple ID, I can't use the functions.

When I have a TextField or TextEditor, tapping into it produces these two console entries about 18 times each: CHHapticPattern.mm:487 +[CHHapticPattern patternForKey:error:]: Failed to read pattern library data: Error Domain=NSCocoaErrorDomain Code=260 "The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} <_UIKBFeedbackGenerator: 0x600003505290>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 "The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} My app does not use haptics. This doesn't appear to cause any issues, although entering text can feel a bit sluggish (even on device), but I am unable to determine relatedness. None-the-less, it definitely is a lot of log noise. Code to reproduce in simulator (xcode 26.2; ios 26 or 18, with iPhone 16 Pro or iPhone 17 Pro): import SwiftUI struct ContentView: View { @State private var textEntered: String = "" @State private var textEntered2: String = "" @State private var textEntered3: String = "" var body: some View { VStack { Spacer() TextField("Tap Here", text: $textEntered) TextField("Tap Here Too", text: $textEntered2) TextEditor(text: $textEntered3) .overlay(RoundedRectangle(cornerRadius: 8).strokeBorder(.primary, lineWidth: 1)) .frame(height: 100) Spacer() } } } #Preview { ContentView() } Tapping back and forth in these fields generates the errors each time. Thanks, Steve

Hello everyone, I have an app that is used in the education sector for high stakes assessment testing. I reviewed a lot of the WWDC2025 information in June, however, it seems we missed something critical in the What's new in UIKIt presentation. That would be the deprecation of UIRequiresFullScreen. We currently use this in our app and have been using it since iOS/iPad OS 9 when our app was written. The deprecation of this property has caused some major issues in our layout. Keep in mind we are a hybrid app so our mobile app is self-hosting a fullscreen version of WKWebView under the hood. This is common across assessment developers in the education sector. I removed the property and went through the migration guide (https://developer.apple.com/documentation/technotes/tn3192-migrating-your-app-from-the-deprecated-uirequiresfullscreen-key) and it doesn't appear to be straight forward on how to lock the orientation in landscape. I tried several different approaches: Requesting the screen orientation lock we had issues where if a user launched it in portrait it would be locked to portrait but we would want to update the display to shift it to landscape as a business requirement supporting both landscape right and landscape left. We also tried overriding the method supportedInterfaceOrientations and utilizing the .landscape enum with no success. It fires just fine but nothing takes effect. Backwards compatibility support there is no guidance on backwards compatibility support and Xcode wants us to do an availability check when using some of the new methods for updating geometry. What is the guidance in this case because we support back to iPadOS 16.0 as a business requirement. Can anyone give us some insight as we are current trying to get ahead of this while 26.3 is still in beta as this would affect our customers deeply because of the UI jank we get as a result of this deprecation.

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).

It's so bad seeing this light mode... Can I ask Apple to give me an access to their frontend, so I can contribute to their repo with a dark mode feature? Not asking Apple to make the dark theme, but rather asking them let me do it.

Since recently, when I try to close a thread I created on an answer of mine, I get the following error: Trying later, next day, does not solve it. In the list of all threads, the post is not marked as answered. But if I look via Chrome or plain Safari, I see the answer itself is marked as correct: Which is not the case when opening in Safari Technology Preview (Release 233) where the same answer is still to be accepted:

Trying to post a question about packages on this forum, I keep cueing the message: 'This post contains sensitive language. Please revise it in order to continue.' 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, Lar

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

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

How to remove answered mark

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

In a completely different thread mungbeans wrote: [quote='865903022, mungbeans, /thread/806960?answerId=865903022#865903022, /profile/mungbeans'] the forum only seems to archive posts from 2021 onwards. [/quote] I didn’t want to hijack that thread so I’ve started this thread for it. AFAICT forums hasn’t lost any content since we moved to a world-readable platform back in 2015. See here for more about that. A quick search suggests that your earliest thread was this: importing Contacts fails with "Cannot import module being compiled". (I’m not sure why I didn’t reply at the time.) What is interesting is that your profile page is only showing threads back to 2021. I see two parts to that: You have to choose Created as the sort order. That’ll show threads you created back to Jul 2016. However, there are still a few threads before Jul 2016 that aren’t showing up. I’m not sure what’s going on there, but I’ve reported it internally (i. 99636235). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"

I've tried several times to post a reply to a message, but I got an error message instead, telling me to try again in a few minutes. I just found out that it did post my replies, without telling me. So now there's many duplicates of the same reply, one for each of my attempts. I'm using Firefox 144.0.2 (aarch64) on macOS 26.1 (25B78).

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.

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

I tried to post a reply to a thread. It seems to be posted, but does not appear in the thread once sent…

It appears that on older posts the code blocks are completely broken. For example https://developer.apple.com/forums/thread/678075 show the code block as a single inline value. Looking at the HTML this is what I see generated <code class="hljs block shell language-shell">Code Block shell#!/bin/bashrm -rf output/rm -rf simulator_fat/mkdir simulator_fatlibs=( "lib_static" ) #Add for i in "${libs[@]}"do lipo -create arm64_simulator/$i.a x86_64/$i.a -output simulator_fat/$i.a xcodebuild -create-xcframework -library simulator_fat/$i.a -library arm64/$i.a -output output/$i.xcframeworkdone</code> Obviously newer code blocks seem to be working (as long as the one above is) but it wreaks havoc trying to look at older posts.