Switching to use DWARF masks the problem because it does not separate debug symbols, whereas DWARF with dSYM uses the strip and dsymutil commands, and it is typically these commands that tend to fail when there is malformed stuff in the binary. You generally want to use the DWARF with dSYM option for release builds because otherwise, debug symbols get shipped with the executable if they are turned on, so turning off dSYM generation by switching to the DWARF option is not a fix, it just masks the problem. Using the DWARF option keeps debug symbols in the executable instead of separating them into a separate dSYM file. Using DWARF with dSYM strips debug symbols from the executable and places them into a separate dSYM file. Might want to consider before removing 'with dSYM File':ĭWARF is the debug information format and the dSYM file is a package containing debug symbols.įor example, if you have a library libfoo.dylib, the debug symbol file would be. Hi here is some info I found in an old Apple Developer Forum post about DWARF. Warning: (i386) /Users/mikechoch/Library/Developer/Xcode/DerivedData/OneSignalSDK-hgznuhhoqujfbdezmyqrlfdkedbp/Build/Products/OneSignal.build/Debug-iphonesimulator/OneSignalFramework.build/Objects-normal/i386/OneSignalJailbreakDetection.o unable to open object file: No such file or directoryĮxamples of some of the 72 warnings on my project's scheme: Warning: (i386) /Users/mikechoch/Library/Developer/Xcode/DerivedData/OneSignalSDK-hgznuhhoqujfbdezmyqrlfdkedbp/Build/Products/OneSignal.build/Debug-iphonesimulator/OneSignalFramework.build/Objects-normal/i386/OneSignalNotificationCategor圜ontroller.o unable to open object file: No such file or directory Warning: (i386) /Users/mikechoch/Library/Developer/Xcode/DerivedData/OneSignalSDK-hgznuhhoqujfbdezmyqrlfdkedbp/Build/Products/OneSignal.build/Debug-iphonesimulator/OneSignalFramework.build/Objects-normal/i386/OneSignalNotificationSettingsIOS8.o unable to open object file: No such file or directory Warning: (i386) /Users/mikechoch/Library/Developer/Xcode/DerivedData/OneSignalSDK-hgznuhhoqujfbdezmyqrlfdkedbp/Build/Products/OneSignal.build/Debug-iphonesimulator/OneSignalFramework.build/Objects-normal/i386/OneSignalClient.o unable to open object file: No such file or directory Warning: (i386) /Users/mikechoch/Library/Developer/Xcode/DerivedData/OneSignalSDK-hgznuhhoqujfbdezmyqrlfdkedbp/Build/Products/OneSignal.build/Debug-iphonesimulator/OneSignalFramework.build/Objects-normal/i386/OneSignal.o unable to open object file: No such file or directory I found out that "mikechoch" (a name that appears on a path on the warnings) is the Github user of Michael DiCioccio, one of your Software Engineers, and that he made a commit just yesterday (09/03) ff0e938.Įxamples of some of the 72 warnings on OneSignalServiceExtension: Since I have tried cleaning derived data and rebuilding the project, and also pod deintegrate and pod install and it did not made the warnings disappear, I am opening this issue. I found this issue that sounds a lot like the issue I'm having #440. Update your project's One Signal SDK version to 2.10.2 using pod install.How did you add the SDK to your project (eg.What version of the iOS SDK are you using?.After updating to One Signal 2.10.2, I've got a lot of warnings on both my personal project and OneSignalServiceExtension schemes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |