Post not yet marked as solved
This seems to be resolved in Xcode 15 Beta 2 (yet my bug report in Feedback Assistant remains open with no reply from Apple).
Post not yet marked as solved
Again, thanks eskimo.
I tried several other of the APIs using the standard pattern as a solution. This does eliminate crashes but the results returned are not always the same as before when a value was provided instead of nil. In a different, but very similar API call to the getAvailableItemList, an NSMutableArray is to be returned but instead I get a SDK_RESULT value indicating that the invalid parameters have been supplied. If I use the workaround that I have instead (that does crash and provides a non-nil value), then I get a success SDK_RESULT along with the values in the array parameter. So I think each will need to be tested. I just wish I had worked as before without crashing.
I have also tried replicating the same crash with sample Object-C code with no success. Do you know if there might be some interoperbility differences with a framework compiled with an older Xcode but used with Swift code under Xcode 14 (with -O)?. I can try and ask the vendor what Xcode they use to build their frameowrk. Based on the warning in the usage sample code they provide...it is not a recent version.
Post not yet marked as solved
I am having a similar issue but it is with a third-party framework where I cannot change the interface. If you have any further insight or help, please let me know.
Post not yet marked as solved
Thanks, eskimo.
I notice another post with a similar issue:.
The header file for the framework had the following protocol...
@protocol itemSDK <NSObject>
- (SDK_RESULT) getAvailableItemList:(NSMutableArray**)itemList;
// ...
@end
I tested this specific API with the "standard pattern" and it does not fail. I will give it a try with the many other SDK interfaces for this framework and see if this can be the best solution. BTW, where is the standard pattern documented as the proper way to pass a value for an AutoreleasingUnsafeMutablePointer?. I found very few examples and most assign an initial value. I reviewed many of the videos from WWDC on unsafe pointers but none cover this particular pointer. Maybe I missed something.
Post not yet marked as solved
I was playing around with this and found that I was able to rotate an App created for an iPad by double-clicking the title bar on a Mac Mini M1. I do not know if this is documented but it worked for me.
Post not yet marked as solved
See: https://developer.apple.com/forums/thread/659693
Post not yet marked as solved
NOTE: This seems to be corrected using Xcode 12.2 beta (12B5018i) on Catalina 10.15.6
Post not yet marked as solved
It is still there with Xcode 12 GM. I reported this bug to Apple Feedback on Aug 27th (Xcode 12 beta 6) but I think it was there even on earlier betas. I then discovered this appears to only occur on macOS 10.15.6 (or earlier?). On a Mac with macOS 11.0 Beta (20A5354i) installed, this does not seem to occur.
