Our app's build process builds a .xcarchive, then exports that to a .ipa for internal distribution to testers.I am finding it impossible to symbolicate crash logs that testers provide. The problem is that the exportArchive process changes the UUIDs of the executables, and they no longer match the .dSYM UUIDs in the archive.I looked to see if there are new dSYMs in the .ipa, but no. The export directory contains a Packaging.log file and this contains several entries like:warning: Cannot genarte useful dsym from input macho file: /var/folders/lb/mq_07k7s7kbbbkx448dprstr0000gn/T/ipatool20180201-54548-1v2lhdj/thinned/armv7/Payload/MyApp.app/MyAppSo maybe it is trying to create new dSYM but failing.How can I use xcodebuild exportArchive and get matching .dSYMs for symbolication use?
Post
Replies
Boosts
Views
Activity
After watching the WWDC 2023 “What’s new in web apps” session, I am unclear on current best practice for custom icons and custom splash screens in iOS PWAs (progressive web apps). Should we now use manifest.json entries, or the old link/meta tags way still?
Is there any Apple sample code for a PWA that, when added to the Home Screen on iOS, shows an app with custom icon and a custom splash screen compatible with all devices? The Configuring Web Applications documentation is marked as Archived. Is there a newer version?
Specifically, do we still have to provide a splash screen PNG for every possible device resolution? This is a serious burden and likely to break whenever a new device is released. It would be ideal if a splash screen could be synthesized by centering an icon on a background of a given color. I can’t get that to work.