Posts

Post not yet marked as solved
7 Replies
0 Views
Here's what you need as of 2022 if you're getting warnings like ITMS-90890, ITMS-90892: Filename Size (px) IconName@2x.png 120x120 IconName@3x.png 180x180 IconName@2x~ipad.png 152x152 IconName@3x~ipad.png 167x167 Note the lack of capitalization on ~ipad! Source: https://stackoverflow.com/a/70186649/702870
Post not yet marked as solved
26 Replies
0 Views
It appears that when using Bitcode, dSYMs are downloadable from AppStoreConnect. When not using Bitcode, the developer is responsible to keep archived apps (.xcarchive bundles) on the computer, so that dSYMs can be searched by Xcode. If you're using fastlane to archive an app, it's a good idea to call backup_xcarchive so that you have access to dSYMs in the future. For my case, i will turn on Bitcode compilation & upload, which should allow downloading from ASC later. If you distribute your app through the App Store with bitcode enabled, your Mac won’t contain the dSYM files that match the final build, because the final compilation of your app from bitcode occurs in the App Store. This final App Store created build has a different build UUID and different dSYM files than the build in the orginial Xcode archive. Use the Xcode Organizer to download the dSYM files for the build created by the App Store. https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report
Post not yet marked as solved
26 Replies
0 Views
I see the same in AppStoreConnect: "Includes Symbols Yes", but no link. I have Fastlane configured to upload symbols, but not upload nor compile Bitcode. I need the symbols to debug PROD crashes, come on ASC Team!