quickstart-ios: Crash reporting - SymbolUpload issues

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

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 13
Comments: 26 (1 by maintainers)

Links to this issue

ios - Firebase crash report dump_syms is not permitted in iTunes connect upload - Stack Overflow

Most upvoted comments

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.”

saldous on Nov 22, 2016

Nice ! We just need to wait now 😃

floriangbh on Nov 22, 2016

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

floriangbh on Nov 22, 2016

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 stephen.aldous@gmail.com 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 notifications@github.com 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 on Jan 31, 2017

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 notifications@github.com 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 on Jan 12, 2017

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 notifications@github.com 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 on Jan 31, 2017

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 notifications@github.com 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.

saldous on Jan 19, 2017