Posts

Post not yet marked as solved
8 Replies
5.7k Views
Got emailed three .txt crash files. Cannot for the life of me figure out how to get Xcode to do something with them. Tried: renaming .txt to .crash Dropping onto "devices and simulators" window Dropping on to "devices and simulators > select device > View device logs" "Download debug symbols" for the archive in Xcode (says "dowloaded debug symbols" so did it) ... and many other things Xcode 13 simply refuses to respond to the drag-and-drop of the file no matter the file extension and no matter where in Xcode's various windows/tools I drop it. Has anyone done this with a crash .txt file from app review and Xcode 13?
Posted Last updated
.
Post not yet marked as solved
2 Replies
867 Views
Suddenly getting this error after making minor (storyboard) updates to app, when trying to upload to App Store connect. App uses Firebase and RealmSwift API's, so I assume one of them is referencing the API in question. However, I have not updated either framework for months, and previous build was accepted and approved by apple. Searching forums, it appears similar problems were occurring for developers about 3 moths ago. Apple declared it a problem with backend and "fixed." Appears to possibly not be fixed any more...
Posted Last updated
.