-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Partially missing symbols in crash reports #8463
Comments
I wanted to clarify that, in the Symbolicated / Unsymbolicated examples above, the Symbolicated log is also only partially symbolicated:
The "_hidden" symbol in this particular case would've been:
|
It appears that this is a bug in more recent versions of Xcode and a side affect of Bitcodeification. A very similar issue was reported in this open radar. I downloaded the dSYM file from iTC for the first Symbolicated (that was actually partially symbolicated) crash report noted above and performed the repro steps noted in that radar. I confirmed that the dSYM Apple sends back contains many "_hidden" symbols:
Happily, the Open Radar report was updated with a response from Apple Developer Relations and it does look like there is a chance this will be fixed in Xcode 8.3. I don't think there is much we can do at the moment other than hope for the best with Xcode 8.3 and also file a duplicate of https://openradar.appspot.com/28503166. I think we should move this issue of the 3.5.1 milestone but keep it open for our own tracking purposes. I'll update this ticket with the Open Radar dupe once I file it. |
Sounds reasonable, @boundsj. It seems like Apple’s track record with bitcode and dSYMs isn’t great, judging by these Crashlytics users' experiences. |
We are publicly tracking in a duplicate Open Radar. |
Still seeing this (via Crashlytics) in a TestFlight app built with Xcode 8.3. |
https://openradar.appspot.com/28503166 was closed as resolved in Xcode 8.3, but inspection of dSYMs downloaded from TestFlight don’t show any significant differences between those built with 8.2 or 8.3. We’ll keep an eye on this issue and close when crash logs are consistently usefully symbolicated. In the meantime, v3.5.2 will be built with Xcode 8.3.1. |
I seem to have the same problem, using the iOS SDK version 3.7.3 I get a crash that appears frequently in my app, and I can't seem to get more info than this:
|
We’ve been seeing a related issue for some time (since around For example, here’s one such crash that ended up being #11940 (and ultimately ended up with a very different stack trace):
|
Stabbing in the dark here, but could this be an unrelated issue caused by |
|
Both of these issues (the original Symptoms I observed:
Unknowns:
Helpful links |
Until we put out a new podspec/release with a fix for this, here’s a workaround:
You can verify that this worked by looking in the |
#12257 has CocoaPods keep our As for properly symbolicating crashes in apps that were submitted without our |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
Still CocoaPods fail to load these files even though these are there in Mapbox-iOS-SDK dynamic folder. Any one know fix? by commenting these lines in project-name-framewroks.sh works but that is not a solution |
@waris117 See #12257 (comment) for our suggested workaround. The CocoaPods team is working on fixing this in 1.7.0 (CocoaPods/CocoaPods#8470), which will eventually obviate these extra steps. |
@khaskheliAyaz That appears to be a missing dSYM, rather than a partially-unsymbolicated crash report (as this issue covers) — see Crashlytics’ missing dSYM help page for advice on how to symbolicate that crash. |
Platform: iOS
Mapbox SDK version: v3.4.2, v3.5.0-beta.3, v3.5.0-rc.1
Some crash reports are only partially symbolicating. Known affected versions of the SDK are listed, but this probably is not limited to those.
If the unsymbolicated crash report retains the unsymbolicated addresses, the dSYM for that version of Mapbox.framework can still be used to symbolicate. But, if the crash report comes from Apple via iTunesConnect/Xcode, the unsymbolicated addresses have been replaced with
_hidden
and the report cannot be symbolicated after the fact.Here’s the same crash, in different versions of the same TestFlight-distributed app, bitcode enabled, using different iOS SDK versions:
Symbolicated (v3.5.0-beta.2)
Click to expand crash log
Unsymbolicated (v3.5.0-rc.1)
Click to expand crash log
/cc @mapbox/ios
The text was updated successfully, but these errors were encountered: