Search results for

dsym file

77,665 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode 16 warning about missing symbols of static framework
I'm having this same issue. I want to upload my app to the app store, but the functionality relies on Firebase (as I access a Firebase/Firestore function I've created). Should I downgrade Xcode to version 15 and validate the app there? Upload Symbols Failed The archive did not include a dSYM for the openssl_grpc.framework with the UUIDs [C10C567E-5647-3F05-87BE-20E45D5E2EFE]. Ensure that the archive's dSYM folder includes a DWARF file for openssl_grpc.framework with the expected UUIDs. I am getting 5 of these, but they are just warnings, so I will try uploading still. Wish me luck!
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Oct ’24
Reply to Xcode 16 warning about missing symbols of static framework
@paulb777, it's likely that the frameworks are not static, but dynamic. Here's a test I just ran that produced dynamic libraries. Firebase is a third-party library with its own support from its vendor and not Apple, so I'm configuring it in an Xcode project here for testing in the simplest way possible for vetting what's happening with Xcode, rather than what's happening with Firebase: File > New Project > iOS app. Add a package dependency to https://github.com/firebase/firebase-ios-sdk Select FirebaseAnalytics and add it to the test app target Build > Archive Here's the file layout of the archive, edited down for clarity: TestApp 10-9-24, 6.32 PM.xcarchive ├── Info.plist ├── Products │ └── Applications │ └── TestApp.app │ ├── Frameworks │ │ ├── FirebaseAnalytics.framework │ │ │ └── FirebaseAnalytics │ │ ├── GoogleAppMeasurement.framework │ │ │ └── GoogleAppMeasurement │ │ └── GoogleAppMeasurementIdentitySupport.framework │ │ └── GoogleAppMeasurementIdentitySupport │ ├── Info.plist
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Oct ’24
Reply to symbolicatecrash failing because it can't find dSYM
mdimport -L does list the uuid importer from xcode. I figured it would because if I just create a test project and archive it the dsym does show up when I run mdfind 'com_apple_xcode_dsym_uuids = *', so the system does seem to work when the build is archived with xcode. Unfortunately the build and dsym I have are from a build produced by a build machine that doesn't archive builds (something I should try and fix I think).I got this output when I tried to manually import the dsym:UG-iMac:DodgersArchive UG_iMac$ mdimport -d 4 -g /Applications/Xcode.app/Contents/Library/Spotlight/uuid.mdimporter Dodgers.app.dSYM mdimport loading plugin at path '/Applications/Xcode.app/Contents/Library/Spotlight/uuid.mdimporter' for all files (Import.Debug:1319) file:/Users/UG_iMac/Desktop/DodgersArchive/Dodgers.app.dSYM plugin:file:///Applications/Xcode.app/Contents/Library/Spotlight/uuid.mdimporter/ /Applications/Xcode.app/Contents/Library/Spotlight/uuid.mdimporter Trace/BPT trap: 5(Note: I h
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Mar ’16
Unable to manually symbolise iOS crash log despite having dSYMs
I was unable to get Xcode 7 to symbolise a crash log I was sent in by an App Store user, and when trying to manually symbolise it it fails, despite me having all the required dSYMs.Crash log excerpt: Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000100fa990c Triggered by Thread: 0 Filtered syslog: None found Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libswiftCore.dylib 0x0000000100fa990c 0x100e64000 + 1333516 1 libswiftCore.dylib 0x0000000100fa990c 0x100e64000 + 1333516 2 MyApp 0x00000001002cdc50 0x1000a4000 + 2268240 ... Binary Images: 0x1000a4000 - 0x10079ffff MyApp arm64 <29a862b975b335ae91c2615c775e064f> /var/mobile/Containers/Bundle/Application/CC9E1FB1-22BB-4723-B28A-95EBE21522A1/MyApp.app/MyAppMy app has Bitcode enabled so I downloaded the dSYMs from Xcode > Organiser > Archives. I then confirmed that `29A862B9-75B3-35AE-91C2-615C775E064F.dSYM` did indeed exist within the archive for the build that was submitted to
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
3.5k
Jan ’16
How to symbolicate macCatalyst X86-64 crash files on M1/2
Got some crashes in Xcode Organizer from a macCatalyst app and they are not symbolicated. The crashes are from an X86-64 machine, and my work machine is M1. When trying to symbolicate them in Organizer I get an error: Unable to Symbolicate Crash - An error occurred attempting to symbolicate crash. Unable to locate dSYMs for .... It makes sense, as I only run the app on M1, and maybe the X86-64 was not built on this machine. I then went to download the dSYM file from AppStoreConnect/TestFlight/Build Metadata, but there is no Download dSYM link, even though the app page says Includes Symbols Yes. I then tried to compile the app for AnyMac (Mac Catalyst, Apple Silicon, Intel), and now I get a binary with two images, the arm64 and the x86, but the UUID of x86 image is different than the one from the crash file. How can I get the original dSYM to symbolicate crashes from production?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
681
Aug ’23
Reply to Crashlytics
Is there any updates? We've come across this issue as well. Previous archives don't contain dsyms, tried archive it again but still no luck. AppStoreConnect also no longer provides link to download dsyms.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’21
Reply to How to Symbolicate an Apple Silicon Panic?
First off, please file a bug about the documentation side of this and then post the number back here. We really should do a much better job of explaining exactly what all this involves. Next, a clarification on this: That's not even a program instruction - that's within a cstring. No, that cstring isn't involved in anything pertaining to the intentional panic I am expecting to see. Which gives the following incorrect result: Address: KextName[0x0000000000003e40] (KextName.__TEXT.__cstring + 14456) Summary: ffer has %d retainsn That's not even a program instruction - that's within a cstring. No, that cstring isn't involved in anything pertaining to the intentional panic I am expecting to see. What you described here isn't exactly what's going on. The symbolication process is inherently, for lack of a better word, stupid. Conceptually, your symbol file is basically just a long list of strings and offset pair, so all symbolication does is find the closest offset smaller than the address it was
Topic: App & System Services SubTopic: Drivers Tags:
Aug ’24
Reply to How to get the dSYM for frameworks?
If you are building the framework as a dependency of your app target, the dSYMs for the framework will be present in the archive you create when archiving the app for distribution. If you are using a framework provided by a vendor that is already compiled, you will need to contact the framework vendor about the dSYMs.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’17