android.view.InflateException: Binary XML file line #4: Error inflating class fragment On Tue, May 24, 2016 at 5:08 PM, 'Doug Stevenson' via Firebase Google Group <fireba...@googlegroups.com> wrote: > Currently there is a delay of about 20 minutes from the time of the crash > to the moment it appears in the dashboard. We're working on improving this. > > If you're still not seeing the crash in the console, check logcat to see > if there is a message that confirms the crash was sent. It should try to > send immediately, but if it can't for some reason, it should retry. Also > try relaunching the app to stimulate a retransmission. > > On Tuesday, May 24, 2016 at 12:24:51 PM UTC-7, Dale King wrote: >> >> That appears to be the issue with mine. I switched to my phone and that >> error went away. I still cannot get it to report crashes from our app, but >> I can from the quickstart sample app. Doesn't report any errors and it >> shows that FirebaseCrash caught the error, but I don't see it being sent in >> the log and it never shows up on the server. >> >> On Tuesday, 24 May 2016 14:42:40 UTC-4, Doug Stevenson wrote: >>> >>> Also, it's worth mentioning that Crash Reporting won't initialize in >>> Android emulators that: >>> >>> - Don't have "Google APIs" (Play Services) installed. Be sure to choose >>> an image with Google APIs. >>> - Have an old Play Services (prior to version 9.0.0). >>> >>> Today, it looks like the emulator images for API level 22 and 23 that >>> include Google APIs have a 9.0+ Play Services, so that should work OK. Be >>> sure that you have revision 14 of the "Google APIs Intel x86 Atom System >>> Image" for API level 23, or revision 7 of the x86 image for API level 22. >>> >>> Doug >>> >>> On Monday, May 23, 2016 at 4:54:10 PM UTC-7, Ian Barber wrote: >>>> >>>> This looks very much like its running on an older version of Google >>>> Play Services. Firebase needs Google Play services 9.0+ on the device in >>>> order to work. Which version are you running? >>>> >>>> On Monday, 23 May 2016 06:30:47 UTC-7, Kumar Vivek wrote: Hello I have recently started building android app on firebase platform, but >>>>> i am facing an issue with Crash Reporting (Which is in BETA now). I followed as instructed in the doc, and added the gradle dependency >>>>> for crash reporting, also I have added Firebase SDK and JSON data of Google >>>>> Services in my project. But I am getting this error in Logcat: 05-23 17:41:34.964 3380-3380/com.phoenixapplabs.myjobber >>>>> E/FirebaseCrash: Failed to initialize crash reporting com.google.firebase.crash.internal.zzg$zza: >>>>> com.google.android.gms.internal.zzqi$zza: No acceptable module found. Local >>>>> version is 0 and remote version is 0.

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

    • android.view.InflateException: Binary XML file line #4: Error inflating class fragment On Tue, May 24, 2016 at 5:08 PM, 'Doug Stevenson' via Firebase Google Group <fireba...@googlegroups.com> wrote: > Currently there is a delay of about 20 minutes from the time of the crash > to the moment it appears in the dashboard. We're working on improving this. > > If you're still not seeing the crash in the console, check logcat to see > if there is a message that confirms the crash was sent. It should try to > send immediately, but if it can't for some reason, it should retry. Also > try relaunching the app to stimulate a retransmission. > > On Tuesday, May 24, 2016 at 12:24:51 PM UTC-7, Dale King wrote: >> >> That appears to be the issue with mine. I switched to my phone and that >> error went away. I still cannot get it to report crashes from our app, but >> I can from the quickstart sample app. Doesn't report any errors and it >> shows that FirebaseCrash caught the error, but I don't see it being sent in >> the log and it never shows up on the server. >> >> On Tuesday, 24 May 2016 14:42:40 UTC-4, Doug Stevenson wrote: >>> >>> Also, it's worth mentioning that Crash Reporting won't initialize in >>> Android emulators that: >>> >>> - Don't have "Google APIs" (Play Services) installed. Be sure to choose >>> an image with Google APIs. >>> - Have an old Play Services (prior to version 9.0.0). >>> >>> Today, it looks like the emulator images for API level 22 and 23 that >>> include Google APIs have a 9.0+ Play Services, so that should work OK. Be >>> sure that you have revision 14 of the "Google APIs Intel x86 Atom System >>> Image" for API level 23, or revision 7 of the x86 image for API level 22. >>> >>> Doug >>> >>> On Monday, May 23, 2016 at 4:54:10 PM UTC-7, Ian Barber wrote: >>>> >>>> This looks very much like its running on an older version of Google >>>> Play Services. Firebase needs Google Play services 9.0+ on the device in >>>> order to work. Which version are you running? >>>> >>>> On Monday, 23 May 2016 06:30:47 UTC-7, Kumar Vivek wrote: Hello I have recently started building android app on firebase platform, but >>>>> i am facing an issue with Crash Reporting (Which is in BETA now). I followed as instructed in the doc, and added the gradle dependency >>>>> for crash reporting, also I have added Firebase SDK and JSON data of Google >>>>> Services in my project. But I am getting this error in Logcat: 05-23 17:41:34.964 3380-3380/com.phoenixapplabs.myjobber >>>>> E/FirebaseCrash: Failed to initialize crash reporting com.google.firebase.crash.internal.zzg$zza: >>>>> com.google.android.gms.internal.zzqi$zza: No acceptable module found. Local >>>>> version is 0 and remote version is 0. at com.google.firebase.crash.internal.zzg.zzah(Unknown Source) at com.google.firebase.crash.FirebaseCrash.<init>(Unknown Source)
    No Bugmate found.