Quickstart-ios: Crash reporting - SymbolUpload issues

[Doubletaps76]

I'm using cocoapods to install FirebaseCrash(1.0.6),
and I setting up Firebase Crash Reporting on my project (including add roles in firebase permission/service accounts, imported necessary json file, add run script in build Phases). After I build/run project on my iPhone, I got multiple upload symbol issues warning :

warning: dump_syms: /var/folders/dt/cx1btjxs0n546bsr0_941pqr0000gn/T/com.google.FirebaseCrashReporter.I7QUjQOr/project_name.dSYM/Contents/Resources/DWARF/project_name: in compilation unit '/Users/mikelehen/firebase/firebase-client-objc/Firebase/Firebase/Utilities/FUtilities.m' (offset 0x2a6b6):
warning: dump_syms: /var/folders/dt/cx1btjxs0n546bsr0_941pqr0000gn/T/com.google.FirebaseCrashReporter.I7QUjQOr/project_name.dSYM/Contents/Resources/DWARF/project_name: the DIE at offset 0x2ac44 has a DW_AT_abstract_origin attribute referring to the die at offset 0x2acd4, which either was not marked as an inline, or comes later in the file
warning: dump_syms: /var/folders/dt/cx1btjxs0n546bsr0_941pqr0000gn/T/com.google.FirebaseCrashReporter.I7QUjQOr/project_name.dSYM/Contents/Resources/DWARF/project_name: warning: function at offset 0x2ac44 has no name
warning: dump_syms: /var/folders/dt/cx1btjxs0n546bsr0_941pqr0000gn/T/com.google.FirebaseCrashReporter.I7QUjQOr/project_name.dSYM/Contents/Resources/DWARF/project_name: in compilation unit '/Users/mikelehen/firebase/firebase-client-objc/Firebase/APLevelDB/APLevelDB.mm' (offset 0x64085):

And I found the same issue in StackOverFlow

[bizibizi]

I have the same, 12 warnings

[zxl777]

How to fix these warnings (dump_syms 85 warnings)?

[martolini]

+1

[jlaws]

Can we get this fixed? Excessive warnings can mask actual important issues.

[reallyseth]

Agree with @jlaws, would be great to have a fix, or at least to be able to silence the warnings for dump_syms.

[simonbengtsson]

This does not happen on a new project with only firebase as dependency. It still happens in our project however despite having the latest v3.8. We still have the issue of non symbolicating crashes, not sure if that is related.

http://stackoverflow.com/questions/40204969/wrong-symbol-files-uploaded-by-firebase-crash-reporting

[karthikAdaptavant]

+1

[victory1908]

I have 600 warning of this type. Don't know why

warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: in compilation unit '/Volumes/Data/OneDrive/Singpost/App/Version8c/SingPost/Pods/Realm/Realm/ObjectStore/src/impl/collection_change_builder.cpp' (offset 0x119870):
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x15c1b4 has a DW_AT_specification attribute referring to the die at offset 0x15c14f, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x163207 has a DW_AT_specification attribute referring to the die at offset 0x149890, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x1639cd has a DW_AT_specification attribute referring to the die at offset 0x1498dd, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x165500 has a DW_AT_specification attribute referring to the die at offset 0x14bfb8, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x1662c9 has a DW_AT_specification attribute referring to the die at offset 0x14c0a7, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x166745 has a DW_AT_specification attribute referring to the die at offset 0x16552a, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: warning: function at offset 0x166745 has no name
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16690d has a DW_AT_specification attribute referring to the die at offset 0x14c0e3, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16be72 has a DW_AT_specification attribute referring to the die at offset 0x15354c, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16c725 has a DW_AT_specification attribute referring to the die at offset 0x16beae, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16c7aa has a DW_AT_specification attribute referring to the die at offset 0x153597, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16e8cb has a DW_AT_specification attribute referring to the die at offset 0x154dbf, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x16f21e has a DW_AT_specification attribute referring to the die at offset 0x15539b, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x173b7b has a DW_AT_specification attribute referring to the die at offset 0x15cfc5, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x173c00 has a DW_AT_specification attribute referring to the die at offset 0x15d012, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x173c85 has a DW_AT_specification attribute referring to the die at offset 0x15ef60, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: the DIE at offset 0x173f6a has a DW_AT_specification attribute referring to the die at offset 0x15d05f, which either was not marked as a declaration, or comes later in the file
warning: dump_syms: /Users/victory1908/Library/Developer/Xcode/DerivedData/SingPost-bsyrfyuoahxzibgwthrzgvnckyff/Build/Products/Debug-iphonesimulator/SingPost.app.dSYM/Contents/Resources/DWARF/SingPost: in compilation unit '/Volumes/Data/OneDrive/Singpost/App/Version8c/SingPost/Pods/Realm/Realm/ObjectStore/src/collection_notifications.cpp' (offset 0x17413a):

[floriangbh]

Same issue, 300 warning for a little project...

Crash report work in debug, but got warning only when archiving project

[saldous]

I have the same problem, 586 issues reporting this same warning. How to fix?

[floriangbh]

Got this answers after report this issue at Firebase :

Hi Florian,

Thank you for reaching out. I'm currently looking into this and I'll update you once I have enough information to share. I might go back to you for some more information if needed. So please hang in there.

Regards,
Alvin

[saldous]

They just emailed me the following:

"These warnings are innocuous and do not have any impact on the behavior or the output of the app.
We are working on suppressing these warnings so that the developers are not confused.
Won't be able to provide any timeline or ETA for the fix. Keep an eye on the upcoming releases."

[floriangbh]

Nice ! We just need to wait now :-)

[ajonno]

prior to installing Firebase Crash Reporting (after reading it had gone GA) I had 1 build warning. After installing, I am seeing ...865 BUILD WARNINGS and it's increased the build time significantly. Please resolve this soon as possible !

[saldous]

I emailed their support earlier today chasing this issue. They says it's innocuous messages, but there are so many that devs can't find real warnings as they get buried. Very annoying.

Regards,
Stephen

On Jan 4, 2017, at 20:03, Angus Johnston [e-mail] wrote:

prior to installing Firebase Crash Reporting (after reading it had gone GA) I had 1 build warning. After installing, I am seeing ...865 BUILD WARNINGS and it's increased the build time significantly. Please resolve this soon as possible !

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[cyurtbil]

I have 685 warnings on this matter when archived, so +1

[kennyqiyenkan]

This needs to be addressed. 774 warnings is.. excessive.

[saldous]

Firebase team just emailed me to say they fixed it and to look out for an update soon :-)

Regards,
Stephen

On Jan 10, 2017, at 14:36, Kenny Qi Yen Kan [e-mail] wrote:

This needs to be addressed. 774 warnings is.. excessive.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[saldous]

I still get the same issue, even with this update. Anyone else?

Regards,
Stephen

On Jan 18, 2017, at 04:20, Simon Bengtsson [e-mail] wrote:

Fix is live! https://firebase.google.com/support/release-notes/ios

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[floriangbh]

I think there is no fix, just need to wait crashlytics into Firebase : https://fabric.io/blog/fabric-joins-google

[saldous]

Just got an update that the launch for this bug fix is scheduled for the end of Jan.

Regards,
Stephen

On Jan 19, 2017, at 02:28, Florian Gabach [e-mail] wrote:

I think there is no fix, just need to wait crashlytics into Firebase : https://fabric.io/blog/fabric-joins-google

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[hassanmah]

Hi,

Any updates on this fix?

Thanks

[iAviatorJose]

Even i am getting 400 odd warnings while archiving, this issue still exist.
Any Solution ...

[saldous]

I just did a pod update and see Firebase 3.12.0 is now available. Looking
at the release notes:
https://firebase.google.com/support/release-notes/ios#3.12.0

FIXED: Adjusted the verbosity of messages logged to the console.

Let's hope so!

Anyone tried it yet?

On 31 January 2017 at 01:53, Jose Varghese [e-mail] wrote:

Even i am getting 400 odd warnings, this issue still exist.
Any Solution ...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/46#issuecomment-276288624,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLgotKcVjUDM8EG1qSCoNPreN3HnHDMks5rXtpbgaJpZM4I4EZq
.

[saldous]

I just archived a build with this new update and can confirm the issue is
resolved! :)

On 31 January 2017 at 16:12, Stephen Aldous [e-mail]
wrote:

I just did a pod update and see Firebase 3.12.0 is now available. Looking
at the release notes: https://firebase.google.com/support/release-
notes/ios#3.12.0

FIXED: Adjusted the verbosity of messages logged to the console.

Let's hope so!

Anyone tried it yet?

On 31 January 2017 at 01:53, Jose Varghese [e-mail]
wrote:

Even i am getting 400 odd warnings, this issue still exist.
Any Solution ...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/46#issuecomment-276288624,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLgotKcVjUDM8EG1qSCoNPreN3HnHDMks5rXtpbgaJpZM4I4EZq
.

[morganchen12]

Thanks for confirming, @saldous. Feel free to comment or reopen if you see this regress.