I encountered the same crash when loading my MainMenu.nib and I have found the reason of the crash. I had several shared objects in the MainMenu.nib, such as NSDocumentController and others. These shared objects "init" are called twice. The first is from my own code and the second is from [NSClassSwapper initWithCoder]. In the first call, [super init] is called but in second call [super init] is not called because it is the shared object. The crash occurs when these shared object's second "init" call. To work around this problem, I modified my code not to call the shared object "init" twice. I hope this helps! Satoshi Matsumoto

Answer from Apple DTS: The behavior and resulting limitations you describe are by design. This is because the destination path is outside of the app sandbox. You’ll have to ask the user to pick the destination. If you believe an alternative approach should be considered by Apple, we encourage you to file an enhancement request with information on how this design decision impacts you, and what you’d like to see done differently. Although there is no promise that the behavior will be changed, it is the best way to ensure your thoughts on the matter are seen by the team responsible for the decision. While a Technical Support Incident (TSI) was initially debited from your Apple Developer Program account for this request, we have assigned a replacement incident back to your account.

I have encountered the same problem when purchasing a license on TestFight in Japanese AppStore. Is this bug is only in TestFight environment? Is it okay to release it while ignoring this bug?