Firebase Analytics Debug View does not show anything –

Development issue/problem:

I linked my Android application to Firebase using Android Studio
, which created and configured my google.jsonservice in my project.

When I debug my event in logcat, I get :

V/FA-SVC : Download successful. I got a response from the network. Code, mate: 204, 0

But there’s nothing in the debug view of the Firebase console.

How can I solve this problem?

Solution 1:

Tester Adjustment

To enable the DebugView data to be sent to the connected Android test device for the configured Firebase Analytics application, perform the following step:

  1. If you only work with one design variant, the following command is sufficient:

adb shell setprop [your_app_package_name]

  1. However, if you are working with different design variants with different application IDs that do not match the application package name, you must run the following command:

adb shell setprop [your_application_id]

Here, the application ID is the ID of your construction variant, which can be found in the corresponding classification file. For example, suppose you have x.gradle and y.gradle for two build options x and y and you have a common build.gradle file. To debug the design variant x with the application ID, the command is executed:

adb shell setprop

In the same way, to debug the build variant y with the application ID, execute the command:

adb shell setprop

This behavior remains until you explicitly disable it by executing the following command:

adb shell setprop

Solution 2:

After performing the steps to activate debug mode, check that the date and time are correct on the debugger or emulator and on the computer.

If you still don’t see any events in DebugView after setting the date and time, clear the application’s memory. Then restart the application and try again.

Solution 3:

Activating the debug mode is different from activating the debug mode. As Frank van Puffelen suggested in his comments, you need to set the property to the package name of your application to enable debug mode.

To do this, you can use adb with the following command:

adb shell setprop name

The name of your application’s package can be found in AndroidManifest.xml as a package attribute in the manifest element (the first element of the xml document).

Solution 4:

  1. Run your application in debug mode
  2. Photo developer options -> Select debugging application -> Select

You will see your device in the Firebase debug list.

Solution No 5:

Also make sure that the latest Google Play services are installed on your device/emulator, otherwise nothing will work.

If you go to the emulator settings, there is an Update button for that. Unfortunately, you have to sign up for this with your Google Account.

Solution No 6:

As others have said, I think the problem here is usually the use of the wrong package name. I had a problem with an application I started recently, and using the package attribute of AndroidManifest.xml didn’t work. I suspected that the construction added something to the name of the package, but I couldn’t figure out where it was defined. The easiest method I found to find the real package name was to launch the Attach debugger to Android process in the top bar of Android Studio, which then displays a list of processes with their respective package names on AVD. Of course, the use of the package name that was correctly added to this list caused Firebase Analytics to wake up the debug display.

Solution No 7:

Disable all advertising blocking mechanisms in the debugger. That was the problem. I turned on AdAway.

I know it’s an old question, but maybe this will help somebody.

Solution No 8:

For me, the problem was to use the package name in the adb command as suggested in the documentation. What you do need to use is an application for your construction. Although they are identical in many cases, they may be different if you specify a different application in the build.gradle file or if you add postfixes for specific build variants.

I don’t know why they always use a package name for this word, because it just means the way we organize our code.

Solution No 9:

In my case, I replaced the old google-services.json file with the new one. In this case, I had to delete the build directory, rebuild the project, debug the device and perform other steps such as setting adb shell setprop your package name. Then it worked.

Good luck!

Related Tags:

firdebugenabled,firdebugenabled react-native,firebase analytics not working android,adb shell setprop log.tag.fa verbose,firebase analytics uuid,firebase analytics set id,react-native-firebase debugview,unable to open firebase debug log,firebase enable logging ios,adb logcat firebaseperformance,debug view firebase not working,analytics logevent not working,firebase console,firebase debug view no devices available ios,sdk → platform-tools → adb,ios firebase analytics debug mode,debug firebase analytics web,no devices available in debug view firebase,debug view google analytics,debugging google analytics,google analytics tester,firanalyticsdebugenabled,tag manager,ga4 debug view,command not found: adb,google analytics debugger,install adb,adb shell setprop,firebase analytics flutter,google analytics,firebase analytics debug view not working,disable firebase analytics debug android,firebase analytics debug enable,flutter firdebugenabled,flutter firebase analytics debug,firebase analytics debug web

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *