Hi, I am encountering a linking issue with a project for an iOS .NET MAUI application that I am developing using Visual Studio 17.11.4. This project includes a custom static library (.a). The custom static library (.a) depends on the libxml2 library. However, it appears that libxml2 is not included in Xcode 15.4 (Sonoma OS), resulting in the following error: error : Undefined symbols for architecture arm64: error : "_xmlBufferCreate", referenced from: .... I have set the following additional arguments for compilation: -cxx -gcc_flags "-lz -lxml2". Despite my efforts to install libxml2 using Homebrew, I have not been successful. Could you please advise on how I can resolve this issue? Specifically, what is the path that Xcode uses to include libxml2?

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.

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, Apple Developer Forums (aka DevForums) is: 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, hover over the help (?) button next to 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 post a crash report, follow the instructions in 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. 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 correct. 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 correct. If you accidentally post two copies of the same question, choose one as the primary and, in the other one, add a comment that links to it. 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 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.

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.

Hi, I noticed that the "View the thread" button recently stopped working in emails of replies from my watched threads. The link's path seems fine but the subdomain is odd / inexistent, since Safari tells me it cannot find the server. Did anybody else notice this issue?

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

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

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"