“Apple Maps Guides”

Is there any way to opt out of the case-insensitive collision check per domain? No. The problem here is that this: A supportsCaseSensitiveNames property on NSFileProviderDomain would solve this. ...would only move the problem further up the stack without actually fixing it. FileProvider ultimately needs to store the files it's syncing somewhere and, on the vast majority of systems, that location is a case-insensitive file system. Theoretically, it could layer on some system to handle that (for example, using side metadata or some kind of name encoding system), but the major benefit of a sync directory over a secondary volume is that the file sync solution lets you move files in/out of the sync directory without a formal copy operation. That means any support FileProvider introduced that objects moved out of the directory either: Modify the names to remove the collision. OR Fail or only partially complete the move. ...both of which break the expected behavior of the local volume. One thing to keep in mind is t

Thank you for sharing your findings. As far as I can see, I don't see other reports about drawHierarchy causing a crash. Are you able to attach a sample project that builds and runs so that we have the same project when following the steps to reproduce? It would be best if you uploaded a copy to Feedback Assistant as well as share the relevant code snippet here on the Forums so those outside of Apple could offer and learn workarounds as well.  Travis

Thanks for the post and welcome to the community! This is something I saw long time ago when I was looking at how Mac Catalyst works and how the bundle id adds this prefix maccatalyst I think, but not positive as this is from memory. The issue you are running into may be caused by a conflict between how Mac Catalyst originally worked and how Apple handles bundle id registration today. When Mac Catalyst was first introduced Xcode automatically prepended maccatalyst. to your existing iOS bundle ID. However later changed allowing you to sell your iOS and Mac apps together under the exact same App Store Connect record. Do you have the latest Xcode release? Is it happening there? I would upgrade to the latest Xcode, however if not you need to tell Xcode to stop generating that maccatalyst. prefix so your Mac app shares the exact same bundle ID as your iOS app. Here is how to do that from this documentation: https://developer.apple.com/documentation/uikit/mac-catalyst https://developer.apple.com/documentat

Please looks at this thread https://developer.apple.com/forums/thread/818209?answerId=879540022#879540022 where the Apple DTS engineer went over the terminal scripts if you don't mind trying in the terminal % curl -v https://gdmf.apple.com % curl -v https://download.developer.apple.com % curl -v https://devimages-cdn.apple.com Let us know if that fixes your issue and the issues from those commands. Thanks Albert
  Worldwide Developer Relations.

Thanks for the post. I believe still the short answer is that you do not need a paid Apple Developer Program membership, but you do need a free Apple ID, which Xcode refers to as a Personal Team. Is that still the terminology? As the free account allows you to: https://developer.apple.com/get-started/ Access beta versions of Xcode and operating systems
 Test your apps directly on your own devices using Xcode
 Engage on the Apple Developer Forums
Submit bugs with Feedback Assistant 
Participate in online Meet with Apple events Apple requires all apps installed on a physical device to be signed. This ensures the device knows exactly who built the app and prevents malicious software from being installed silently. To do this, Xcode needs an identity to sign the app with, which it calls a Team. You can use your standard, everyday Apple ID to create this team for free. Xcode will now automatically generate the free provisioning profiles and certificates needed t

Virtualization is not daemon safe [1]: % dyld_info -linked_dylibs /System/Library/Frameworks/Virtualization.framework/Versions/A/Virtualization … weak-link /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit … So if you use it from outside of a non-GUI login context you will inevitably encounter some weirdness. I think it’d be reasonable for you to file an enhancement request for documentation as to what is or isn’t expected to work in these contexts. And if you do that, please post your bug number, just for the record. Having said that, I’ve been talking with some folks here and we have a theory as to what might be going on in this specific case. When you log in via SSH, it doesn’t unlock the keychain, and those errors you posted suggest that the keychain is involved. If you manually unlock the keychain, does that help? Specifically: Boot the host Mac without autologin, so there’s no GUI login context. SSH into that Mac. From the SSH session, run this command: % security unlock-keychain password to

[quote='884547022, rbmanian75, /thread/822025?answerId=884547022#884547022, /profile/rbmanian75'] Given this, my current focus has shifted to resolving the port forwarding issue. [/quote] Fair enough. I just post an update to your other thread about that specific issue. Regarding the issue here, I don’t think vmnet can do what you want, for the reasons you’ve identified: [quote='884547022, rbmanian75, /thread/822025?answerId=884547022#884547022, /profile/rbmanian75'] The primary challenge is that the network configuration cannot be modified while it is active. [/quote] I’m gonna check on that though, just to be sure. [quote='884547022, rbmanian75, /thread/822025?answerId=884547022#884547022, /profile/rbmanian75'] The documentation suggests using CFRelease, but this is not directly compatible with ARC. [/quote] Right. If you’re using ARC, or Swift, the equivalent technique is to drop any strong references you have to the object. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple