Can't Post On This Forum

Sorry for the delay responding. I’m running out of workdays for 2025, so I can’t address everything upthread. Instead, I want to post some general guidelines.

If DevForums blocks you from posting reasonable content with the message “This post contains sensitive language”, I’d appreciate you filing a bug about that. For instructions on how to do that, see the end of this post.

After that, you’ll need a workaround. Here’s how to use a binary search to find the problematic text:

1. As part of the bug reporting process, you saved a copy of your post to a text file. Make a copy of that file.
2. Open it in your text editor of choice.
3. Select half of the file and delete it.
4. Copy the remaining text and try to post that.
5. If it works, undo the delete, select the other half, delete that, and go back to step 4. Make sure to click the Edit button next to your post rather than posting a second reply.
6. If it fails, go back to step 3 and continue dividing.

Eventually you’ll get down to something super small and you can usually find a way to reword things to avoid the problem. For example, in this post I found that one of the numbers in the crash report was causing problems so I changed it to hex (0x0c00000d9de112c0) and that was fine.

Obviously this is less than ideal, hence my request for bug reports that contain real world examples of this problem.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

To file a bug about this:

Note I’m assuming you’re using a recent Safari on the Mac. All of this is possible with other browsers and other platforms, you’ll just have to figure out how to map these instructions to your environment.

1. Copy the text of your message and save it to a text file.
2. In Safari, bring up Web Inspector. For instructions on how to do that, see Inspecting Safari on macOS.
3. In Web Inspector, switch to the Network tab.
4. Back on the forums webpage, hold down option and choose View > Reload Page from Origin.
5. Now copy the text from the text file you created in step 1 and paste it into the message box.
6. Try to post that.
7. If it works, this was a transient error and you shouldn’t continue with this process [1].
8. If it fails with a “This post contains sensitive language” message, first take a screenshot of the failure.
9. Then flip back to Web Inspector and, still in the Network tab, click the Export button.
10. Save the HAR log somewhere convenient.
11. Now file a bug. In Feedback Assistant, when it asks where you want to start your feedback, select Developer Tools & Resources.
12. And in the problem area popup, select Developer Forums.
13. Make sure to attach:
    • The text file from step 1.
    • The screenshot from step 8.
    • The HAR log from step 10.
14. Fill in the rest of your bug report and submit it. For general advice on the bug reporting process, see Bug Reporting: How and Why?.
15. Reply here with the bug number.

[1] Not that such problems aren’t bugworthy, but the process I’m describing here won’t yield actionable debugging information.