[Unity] Bugs discovered in version 1.0.1

[Alessandro Lacroce]

Hi, 

we've successfully integrated the latest Unity SDK (1.0.1) into our Unity project. On our devices everything works fine, but we keep receiving a lot of crash reports from our users (in order of magnitude): 

Bug #1

Fatal Exception: java.lang.Error: FATAL EXCEPTION [IntentService[FIREBASE_MSG_FWDR]]

Unity version     : 5.4.1f1

Device model      : samsung GT-N8010

Device fingerprint: samsung/p4notewifiub/p4notewifiww:4.1.2/JZO54K/XXXXXXX:user/release-keys

Caused by java.lang.NullPointerException

       at com.google.firebase.messaging.RemoteMessage.getFrom(Unknown Source)

       at com.google.firebase.messaging.cpp.ListenerService.onMessageReceived(ListenerService.java:59)

       at com.google.firebase.messaging.MessageForwardingService.onHandleIntent(MessageForwardingService.java:34)

       at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)

       at android.os.Handler.dispatchMessage(Handler.java:99)

       at android.os.Looper.loop(Looper.java:137)

       at android.os.HandlerThread.run(HandlerThread.java:60)

Bug #2

Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain]

Unity version     : 5.4.1f1

Device model      : Positivo S480

Device fingerprint: positivo/S480/S480:5.0.2/LRX22G/XXXXXXX:user/release-keys

Caused by java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00040001

Build fingerprint: 'positivo/S480/S480:5.0.2/LRX22G/XXXXXXX:user/release-keys'

Revision: '0'

pid: 16554, tid: 16589, name: UnityMain  >>> com.WhatWapp.BuracoOnlineBR <<<

    r0 b9cf6560  r1 00040001  r2 b9d06080  r3 00000006

    r4 00040001  r5 b9cf6560  r6 00000004  r7 a0a8b2b8

    r8 bb59f308  r9 0000450f  sl a2c7445c  fp a1c0f240

    ip b6f54694  sp a1c0f1f0  lr 95d4e70d  pc 95d4e852  cpsr 36313032

       at libApp.std::__1::__tree<std::__1::__value_type<firebase::Variant, firebase::Variant>, std::__1::__map_value_compare<firebase::Variant, std::__1::__value_type<firebase::Variant, firebase::Variant>, std::__1::less<firebase::Variant>, true>, std::__1::allocator<std::__1::__value_type<firebase::Variant, firebase::Variant> > >::destroy(std::__1::__tree_node<std::__1::__value_type<firebase::Variant, firebase::Variant>, void*>*)(__1:7)

       at libApp.firebase::Variant::Clear(firebase::Variant::Type)(Variant:104)

       at libApp.firebase::Variant::operator=(firebase::Variant const&)(Variant:12)

       at libApp.Firebase_Analytics_CSharp_LogEvent__SWIG_5(Firebase_Analytics_CSharp_LogEvent__SWIG_5:50)

       at Unknown.00007cec(Unknown Source)

       at FirebaseAnalyticsPINVOKE.LogEvent__SWIG_5(Unknown Source)

       at FirebaseAnalytics.LogEvent(<0x000ec>:236)

       at FirebaseAnalyticsManager.LogCustomEvent(<0x0018f>:399)

       at Analytics.PushEvent(<0x0055b>:1371)

       at <Start>c__IteratorBB.MoveNext(<0x001b3>:435)

       at SetupCoroutine.InvokeMoveNext(<0x00067>:103)

       at <Module>.runtime_invoke_void_object_intptr(Unknown Source)

       at libmono.00021cd3(Unknown Source)

       at libmono.mono_runtime_invoke(mono_runtime_invoke:136)

       at libunity.004161f8(Unknown Source)

       at libunity.00376f54(Unknown Source)

       at libunity.00376c60(Unknown Source)

       at libunity.0019d1a0(Unknown Source)

       at libunity.003dfd30(Unknown Source)

       at libunity.0050cf34(Unknown Source)

       at libunity.0050fb3c(Unknown Source)

       at data@app@com.00509a23(Unknown Source)

#Bug 3

Non-fatal Exception: java.lang.Exception: InitializationException :   Firebase modules failed to initialize: messaging (missing dependency)

       at Firebase.FirebaseApp.CreateAndTrack(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.Create(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.get_DefaultInstance(Firebase.FirebaseApp)

       at Firebase.Analytics.FirebaseAnalytics..cctor(Firebase.Analytics.FirebaseAnalytics.)

       at FirebaseAnalyticsManager.LogScreen(FirebaseAnalyticsManager)

       at Analytics.PushScreen(Analytics)

       at Genesis+<Start>c__IteratorAA.MoveNext(Genesis+<Start>c__IteratorAA)

       at UnityEngine.SetupCoroutine.InvokeMoveNext(UnityEngine.SetupCoroutine)

Is this the right place to report bugs?

Thank, 

Alessandro

[Benjamin Wulfe]

Firebase developer here.  Thank you for reporting these issues to us!

We prefer you file a support ticket through our support team here:

https://firebase.google.com/support/contact/troubleshooting/

This way, it will be better tracked and the issues get better visibility in case others ask about them.

Thanks again.

-Ben

[Stewart Miles]

Bug #1 is a new one for us, thanks for the report.  We'll take a look and get back to this thread.

Bug #2 is a regression in the C++ SDK's handling of null strings.  For the moment you'll need to construct events with at least a zero length string.  We'll have a fix in the next release.

Bug #3 is due to devices with out of date Google Play Services.  Are you calling FixDependenciesAsync() ? 

https://github.com/firebase/quickstart-unity/blob/master/analytics/testapp/Assets/TestApp/UIHandler.cs#L42

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/1e921ffc-56ec-4716-bd5e-02aed5847c5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Phan Dinh Nham]

I also get bug in my phone. Hope can fix early it.

FATAL EXCEPTION: IntentService[FIREBASE_MSG_FWDR]

                                                 java.lang.Error: FATAL EXCEPTION [IntentService[FIREBASE_MSG_FWDR]]

                                                 Unity version     : 5.4.3f1

                                                 Device model      : samsung Galaxy Nexus

                                                 Device fingerprint: samsung/yakjusc/maguro:4.2.2/JDQ39/SC04DOMMD4:user/release-keys

                                                 

                                                 Caused by: java.lang.NullPointerException

                                                     at com.google.firebase.messaging.RemoteMessage.getFrom(Unknown Source)

                                                     at com.google.firebase.messaging.cpp.ListenerService.onMessageReceived(ListenerService.java:59)

                                                     at com.google.firebase.messaging.MessageForwardingService.onHandleIntent(MessageForwardingService.java:34)

                                                     at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)

                                                     at android.os.Handler.dispatchMessage(Handler.java:99)

                                                     at android.os.Looper.loop(Looper.java:137)

                                                     at android.os.HandlerThread.run(HandlerThread.java:60)

Vào 06:33:33 UTC+7 Thứ Bảy, ngày 26 tháng 11 năm 2016, Alessandro Lacroce đã viết:

[Alessandro Lacroce]

Hi Stewart,

#1 It seems to be the biggest issue so far (you can have more info on devices affected and other data from this link )
#2 Ok, we'll make sure every event has a zero length string

#3 Yes, in our first release we didn't check for the Play Services status. Yesterday we published an update that check for this, but we still experiencing the issue... is it possible that devices that tried to use Firebase in the first release are still trying to use it in the second one (skipping somehow our new control)? 

Thanks, 

Alessandro

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

[Stewart Miles]

On Wed, Nov 30, 2016 at 1:15 AM, Alessandro Lacroce <alessandr...@whatwapp.com> wrote:

Hi Stewart,

#1 It seems to be the biggest issue so far (you can have more info on devices affected and other data from this link )

Noted, we're on it :)

 

#2 Ok, we'll make sure every event has a zero length string

#3 Yes, in our first release we didn't check for the Play Services status. Yesterday we published an update that check for this, but we still experiencing the issue... is it possible that devices that tried to use Firebase in the first release are still trying to use it in the second one (skipping somehow our new control)? 

Is it possible you still have devices out there that are running the older release where you're not checking for Google Play Services availability which are still reporting crashes?

What do you do if Google Play Services is not available?  Do you try running the update and if that fails, disable Firebase?

 

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/0ac12ec2-a5f0-4d32-bd34-02422cf087fe%40googlegroups.com.

[Stewart Miles]

On Wed, Nov 30, 2016 at 9:47 AM, Stewart Miles <smi...@google.com> wrote:

On Wed, Nov 30, 2016 at 1:15 AM, Alessandro Lacroce <alessandro.lacroce@whatwapp.com> wrote:

Hi Stewart,

#1 It seems to be the biggest issue so far (you can have more info on devices affected and other data from this link )

Noted, we're on it :)

For the record it looks like issue #1 has been cross posted multiple places:

https://github.com/firebase/quickstart-unity/issues/18

https://groups.google.com/d/msg/firebase-talk/rqWZ2frS_VY/ISNmhzfFAwAJ

https://groups.google.com/d/msg/firebase-talk/jYPUWndzbEg/TzyFVKMyBQAJ

[Alessandro Lacroce]

No, we are filtering the crash report for app version and it is present in the latest version as well. If the Google Play Services are not available (or need to be updated) we disable all the call to the Firebase SDK, should we do something else?  

[Stewart Miles]

w.r.t #3 if you're seeing that exception you're still attempting to use analytics even though Google Services isn't available.

Non-fatal Exception: java.lang.Exception: InitializationException :   Firebase modules failed to initialize: messaging (missing dependency)

       at Firebase.FirebaseApp.CreateAndTrack(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.Create(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.get_DefaultInstance(Firebase.FirebaseApp)

       at Firebase.Analytics.FirebaseAnalytics..cctor(Firebase.Analytics.FirebaseAnalytics.)

       at FirebaseAnalyticsManager.LogScreen(FirebaseAnalyticsManager)

       at Analytics.PushScreen(Analytics)

       at Genesis+<Start>c__IteratorAA.MoveNext(Genesis+<Start>c__IteratorAA)

       at UnityEngine.SetupCoroutine.InvokeMoveNext(UnityEngine.SetupCoroutine)

When we create FirebaseApp we attempt to initial all modules included in the application and if any require Google Play Services on the device we throw an exception.

It looks like you need to disable FirebaseAnalyticsManager when Firebase initialization fails or just catch the InitializationException and fail silently.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/8dd669f7-c6fa-461e-a330-e04ae3de21a2%40googlegroups.com.

[Stewart Miles]

I'm pleased to announce that we released:

• Firebase C++ SDK 2.1.0 (release notes here, download here)
• Firebase Unity SDK 1.1.0 (release notes here, download here)

We hope this resolves your issue.  If not, please let us know and we'll take a look.

Cheers,

Stewart

On Wednesday, November 30, 2016 at 10:29:51 AM UTC-8, Stewart Miles wrote:

w.r.t #3 if you're seeing that exception you're still attempting to use analytics even though Google Services isn't available.

Non-fatal Exception: java.lang.Exception: InitializationException :   Firebase modules failed to initialize: messaging (missing dependency)

       at Firebase.FirebaseApp.CreateAndTrack(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.Create(Firebase.FirebaseApp)

       at Firebase.FirebaseApp.get_DefaultInstance(Firebase.FirebaseApp)

       at Firebase.Analytics.FirebaseAnalytics..cctor(Firebase.Analytics.FirebaseAnalytics.)

       at FirebaseAnalyticsManager.LogScreen(FirebaseAnalyticsManager)

       at Analytics.PushScreen(Analytics)

       at Genesis+<Start>c__IteratorAA.MoveNext(Genesis+<Start>c__IteratorAA)

       at UnityEngine.SetupCoroutine.InvokeMoveNext(UnityEngine.SetupCoroutine)

When we create FirebaseApp we attempt to initial all modules included in the application and if any require Google Play Services on the device we throw an exception.

It looks like you need to disable FirebaseAnalyticsManager when Firebase initialization fails or just catch the InitializationException and fail silently.