Post not yet marked as solved
Just wanted to add a bit to this since I came to this thread looking to resolve why my framework builds did not include simulator binaries for both M1 Macs (ARM) and Intel.
I was using the same "xcodebuild archive -scheme StructKit -destination "generic/platform=iOS Simulator" ..." command mentioned before, however for me I only ever saw an intel binary in the resigning framework generated.
What ended up being the fix, was that inside my .xcproj file some old version of Xcode has left a default "archs" value for simulators that looked like this:
VALID_ARCHS[sdk=iphonesimulator]
I removed those from two places in the .xcodeproj file, and after that the xcodebuild command produced a framework that had a fat binary with both ARM and Intel.
Post not yet marked as solved
One thing you can do in Xcode 12 is to test purchases in the simulator, if you set up a StoreKit Configuration file and enable it in the project scheme... Then you can do the full range of purchase testing in the simulator.
On device Sandbox should still present a login (make sure your scheme does not have a StoreKit configuration active if you want to test using Sandbox), if you go to Settings->AppStore are you already logged in to a testing account? If you are it would not present a new login.
I get the same crash in Xcode using the Transactions window and clicking on "manage subscriptions", though Xcode 12.2 seems to have a release candidate now and that might fix things.
Post not yet marked as solved
I'm filing a radar on this issue, as the simulator should load products from AppStoreConnect if a StoreKit configuration profile has not been specified in the Scheme you are running.
Post not yet marked as solved
@rich SKProducts have been able to load in the simulator right up until my run in iOS 14... indeed, even running from Xcode 12 beta, in an iOS 13.2 simulator SKProducts load just fine.
I also test product loads on a device, but that is pretty cumbersome to do all the time compared to using the simulator. Also Sandbox is often pokey at loading SKProducts where the simulator is always pretty much instant.
I'm more looking to get a sense from Apple if starting from iOS 14 SKProducts will not load from the App Store, or if this is a bug... I'll file a radar and see what they say I guess.
I ran into the same issue.The problem is that in the Swiftinterface file, you have a class named FastSocket, but the module is also called FastSocket. The generated file includes many module references that Swift thinks are class references because it uses the class ahead of the module...There is a workaround, edit all of the .swiftinterface files to remove the module references (FastSocket.). There are many .swiftinterface files (one per architecture supported) so an easy way to do them all at once is to run this in the root of the .xcframework directory:find . -name "*.swiftinterface" -exec sed -i -e 's/FastSocket\.//g' {} \;You may want to check that has only removed module references, in the case where you have some subelements of the FastSocket class that might need more refining to get right.After running that do a clean build of a project using that framework and try again, the erorrs should be gone.Apple is working on a fix for this so before too long hopefully this step of XCFramework generation will not be required.
Post not yet marked as solved
This turned out not to be the issue I was having, but I wanted to point out a slight bug in the solution code you posted:if (!fileManager.fileExists(atPath: placecholderDirectoryUrl.absoluteString)) {should be:if (!fileManager.fileExists(atPath: placecholderDirectoryUrl.path)) {otherwise it will always try to cretae the folder - not a huge problem, but may as well not do that work if not needed.
Post not yet marked as solved
Wanted to report this also worked for me on an iPhone X with iOS 11.2.1, of note is that it's a very short button press, not a long press that triggers the power off, and it did take a few tries - each time it took a screenshot but eventually along with the screenshot I felt a vibration as well indicating it had triggered the sysdiagnose. After waiting a few minutes according to the instructions on the Bluetooth logging profile I had installed from here:https://developer.apple.com/bug-reporting/profiles-and-logs/I was able to find a sysdiagnose log in Settings > Privacy > Analytics > Analytis Data by scrolling down. It looked blank but that's just becuse it was so large, at something like 197MB I had to use AirDrop to send it to my laptop. It's a tar.gz file that expands into quite a lot of files and folders, under logs I found the bluetooth log I was looking for in a pklg file that requires the packetlogger app to read (I think you get that if you have XCode installed).
