Open mickeyl opened 8 years ago
On-device symbolication works for your own code, but Apple redacted method names within the cocoa SDKs some time ago. Instead you can symbolicate crash reports manually. There is possibly some additional info in #86.
I did some more tests now and can sadly confirm that on-device-symbolication is impossible once you're using bitcode – which is going to be a requirement soon (it's already for watchOS and tvOS). @kstenerud do you have another idea or is that the death of on-device-symbolication?
Is there a way to do the whole bitcode thing without going through Apple's servers? I actually haven't messed with it yet, so if you could give me some pointers on how to do bitcode deployment to my ios device, I might be able to figure something out.
I'm afraid not. Apple is recompiling it and delivering it via the AppStore. If you could do this on your own, they would not offer to download the (modified) dSYMs via Xcode's organizer. Then again though, I never been able to download any dSYMs via this button and the ones that have been created through my compilation process obviously don't match, at least I don't get any reliable symbolication (neither on- nor off-device) with them. sigh
It's more than two years and bitcode is still not required for iOS (and macOS). And honestly I think it will never be as the assured complications are way more than the possible benefits if something bad, like some hacker stealing the bitcode, happens on Apple's side...
@mickeyl Hey, Does on device symbolication still work for you with out bitcode?
I did not change anything in my projects, but it looks that for quite some time (since iOS9, Xcode 7?, I don't know) I no longer get symbolicated crash reports.
I remember having read somewhere that Apple plans to disable this feature for anyone but themselves, but I can't recall where and when this was supposed to happen.
Can anyone confirm or deny that it's no longer working?