René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"FirebaseCrashlytics run vs upload-symbols -- missing optional dsyms","articleBody":"\u003c!-- DO NOT DELETE\r\nvalidate_template=true\r\ntemplate_path=.github/ISSUE_TEMPLATE/bug_report.md\r\n--\u003e\r\n\r\n### [REQUIRED] Step 1: Describe your environment\r\n\r\n  * Xcode version: 11.2.1\r\n  * Firebase SDK version: 6.17.0, 6.24.0\r\n  * Firebase Component: Crashlytics\r\n  * Component version: 6.17.0, 6.24.0\r\n  * Installation method: Carthage\r\n\r\n### [REQUIRED] Step 2: Describe the problem\r\n\r\nWe're seeing missing optional dsym for our apps since a month now and we can't explain why it's happening. As said in the Firebase console, it's only affecting result and grouping, but still we would like to understand why it's like this and what did broke our integration. We've seen this behavior on ad-hoc build without bitcode (we generate dsym) and also on store build (bitcode enabled, dsym pulled from ASC).\r\n\r\n#### Steps to reproduce:\r\n\r\nTo reproduce the issue, I've run a test outside of our CI, to ensure the problem is not there.\r\nInitial steps to ensure app is compiled and dsym are uploaded:\r\n- Xcode clean\r\n- Xcode build for device arch\r\n- Xcode archive\r\n\r\nAs seen in screenshot below, it seems everything is fine during symbols upload:\r\n\r\n![Capture d’écran, le 2020-05-11 à 14 32 20](https://user-images.githubusercontent.com/2801605/81601733-5dba6f00-9399-11ea-860c-ea0d8a68acce.png)\r\n\r\nIn the app, we have a way from our debug menu to trigger a crash, to easily test our Crashlytics integration is working from release to release. After the build is installed on a device (ad-hoc distribution), I simply open the debug menu and crash the app. Result in Firebase console:\r\n\r\n![Capture d’écran, le 2020-05-11 à 14 40 11](https://user-images.githubusercontent.com/2801605/81601792-762a8980-9399-11ea-993c-9a482289c73f.png)\r\n\r\n![Capture d’écran, le 2020-05-11 à 14 31 02](https://user-images.githubusercontent.com/2801605/81601805-7c206a80-9399-11ea-84d5-3545452e7d32.png)\r\n\r\nThis is telling us we're missing the AA71654B-XXX dsym, with turns to be the one generated for Eureka third-party. Having a look within the Xcode archive and using dwarfdump, I can confirm this dsym has been properly generated:\r\n\r\n\u003cimg width=\"835\" alt=\"Capture d’écran, le 2020-05-11 à 14 31 38\" src=\"https://user-images.githubusercontent.com/2801605/81601829-880c2c80-9399-11ea-893f-622d217eff04.png\"\u003e\r\n\r\nI then manually upload-symbols. End result is now the console is able to properly symbolicate new crashes (not older ones):\r\n\r\n\u003cimg width=\"731\" alt=\"Capture d’écran, le 2020-05-11 à 15 11 10\" src=\"https://user-images.githubusercontent.com/2801605/81602041-ea652d00-9399-11ea-94d8-83a14047ac4e.png\"\u003e\r\n\r\n![Capture d’écran, le 2020-05-11 à 14 55 34](https://user-images.githubusercontent.com/2801605/81602091-fcdf6680-9399-11ea-922a-8f4285b180f8.png)\r\n\r\n\r\n\r\nDoes it means that during build, upload was somehow not successful? Or we're missing something in our integration?\r\nAs for our full update path, we were using Fabric Crashlytics for a while, and we did migrate to FirebaseCrashlytics with Firebase 6.17.0 in Feb. I'm currently updating Firebase to latest (6.24.0), but it seems the issue is still there.\r\n\r\nThanks for your help!\r\n","author":{"url":"https://github.com/dloic","@type":"Person","name":"dloic"},"datePublished":"2020-05-11T19:17:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":48},"url":"https://github.com/5569/firebase-ios-sdk/issues/5569"}