Cannot see events in firebase analytics debug view
I'm trying to run a sample app with firebase analytics. I followed the firebase analytics guides to log a test event but I cannot see any events in the debug view. I log a test event on my main activity as below:
public class MainActivity extends AppCompatActivity
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(this);
Bundle bundle = new Bundle();
bundle.putString("test_parameter", "test_value");
mFirebaseAnalytics.logEvent("test_event", bundle);
And I use the following command to see my events in the debug view:
adb shell setprop debug.firebase.analytics.app com.example.firebaseanalyticssample
And I see the logs with the following commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
I think maybe the problem is the null pointer exception appeared in the logs (the last line):
05-25 09:25:53.056 V/FA (21533): Processing queued up service tasks: 2
05-25 09:25:53.086 V/FA-SVC ( 5655): Logging event: origin=auto,name=_e,params=Bundle[mParcelledData.dataSize=132]
05-25 09:25:53.101 V/FA-SVC ( 5655): Saving event, name, data size: _e, 87
05-25 09:25:53.106 V/FA-SVC ( 5655): Event recorded: EventappId='com.example.firebaseanalyticssample', name='_e', params=Bundle[_o=auto, _r=1, _et=52395, _sc=MainActivity, _si=-5268297315019047641, _dbg=1]
05-25 09:25:53.106 V/FA-SVC ( 5655): Upload scheduled in approximately ms: 500
05-25 09:25:53.111 V/FA-SVC ( 5655): Background event processing time, ms: 31
05-25 09:25:53.621 V/FA-SVC ( 5655): Device receiver got: com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.646 V/FA-SVC ( 5655): Device PackageMeasurementService called. startId, action: 194, com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.651 D/FA-SVC ( 5655): Uploading events. Elapsed time since last upload attempt (ms): 544
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I searched a lot and just found this link regarding the exception above that says it must be an error from another application. but whenever my activity is resumed this exception occurs. I don't think that in my case this exception is caused by another apps.
I checked my sample app a lot of times so that every configuration would be exactly as the guides say. Have you any idea what can be the problem?
android firebase google-analytics firebase-analytics
add a comment |
I'm trying to run a sample app with firebase analytics. I followed the firebase analytics guides to log a test event but I cannot see any events in the debug view. I log a test event on my main activity as below:
public class MainActivity extends AppCompatActivity
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(this);
Bundle bundle = new Bundle();
bundle.putString("test_parameter", "test_value");
mFirebaseAnalytics.logEvent("test_event", bundle);
And I use the following command to see my events in the debug view:
adb shell setprop debug.firebase.analytics.app com.example.firebaseanalyticssample
And I see the logs with the following commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
I think maybe the problem is the null pointer exception appeared in the logs (the last line):
05-25 09:25:53.056 V/FA (21533): Processing queued up service tasks: 2
05-25 09:25:53.086 V/FA-SVC ( 5655): Logging event: origin=auto,name=_e,params=Bundle[mParcelledData.dataSize=132]
05-25 09:25:53.101 V/FA-SVC ( 5655): Saving event, name, data size: _e, 87
05-25 09:25:53.106 V/FA-SVC ( 5655): Event recorded: EventappId='com.example.firebaseanalyticssample', name='_e', params=Bundle[_o=auto, _r=1, _et=52395, _sc=MainActivity, _si=-5268297315019047641, _dbg=1]
05-25 09:25:53.106 V/FA-SVC ( 5655): Upload scheduled in approximately ms: 500
05-25 09:25:53.111 V/FA-SVC ( 5655): Background event processing time, ms: 31
05-25 09:25:53.621 V/FA-SVC ( 5655): Device receiver got: com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.646 V/FA-SVC ( 5655): Device PackageMeasurementService called. startId, action: 194, com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.651 D/FA-SVC ( 5655): Uploading events. Elapsed time since last upload attempt (ms): 544
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I searched a lot and just found this link regarding the exception above that says it must be an error from another application. but whenever my activity is resumed this exception occurs. I don't think that in my case this exception is caused by another apps.
I checked my sample app a lot of times so that every configuration would be exactly as the guides say. Have you any idea what can be the problem?
android firebase google-analytics firebase-analytics
add a comment |
I'm trying to run a sample app with firebase analytics. I followed the firebase analytics guides to log a test event but I cannot see any events in the debug view. I log a test event on my main activity as below:
public class MainActivity extends AppCompatActivity
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(this);
Bundle bundle = new Bundle();
bundle.putString("test_parameter", "test_value");
mFirebaseAnalytics.logEvent("test_event", bundle);
And I use the following command to see my events in the debug view:
adb shell setprop debug.firebase.analytics.app com.example.firebaseanalyticssample
And I see the logs with the following commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
I think maybe the problem is the null pointer exception appeared in the logs (the last line):
05-25 09:25:53.056 V/FA (21533): Processing queued up service tasks: 2
05-25 09:25:53.086 V/FA-SVC ( 5655): Logging event: origin=auto,name=_e,params=Bundle[mParcelledData.dataSize=132]
05-25 09:25:53.101 V/FA-SVC ( 5655): Saving event, name, data size: _e, 87
05-25 09:25:53.106 V/FA-SVC ( 5655): Event recorded: EventappId='com.example.firebaseanalyticssample', name='_e', params=Bundle[_o=auto, _r=1, _et=52395, _sc=MainActivity, _si=-5268297315019047641, _dbg=1]
05-25 09:25:53.106 V/FA-SVC ( 5655): Upload scheduled in approximately ms: 500
05-25 09:25:53.111 V/FA-SVC ( 5655): Background event processing time, ms: 31
05-25 09:25:53.621 V/FA-SVC ( 5655): Device receiver got: com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.646 V/FA-SVC ( 5655): Device PackageMeasurementService called. startId, action: 194, com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.651 D/FA-SVC ( 5655): Uploading events. Elapsed time since last upload attempt (ms): 544
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I searched a lot and just found this link regarding the exception above that says it must be an error from another application. but whenever my activity is resumed this exception occurs. I don't think that in my case this exception is caused by another apps.
I checked my sample app a lot of times so that every configuration would be exactly as the guides say. Have you any idea what can be the problem?
android firebase google-analytics firebase-analytics
I'm trying to run a sample app with firebase analytics. I followed the firebase analytics guides to log a test event but I cannot see any events in the debug view. I log a test event on my main activity as below:
public class MainActivity extends AppCompatActivity
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(this);
Bundle bundle = new Bundle();
bundle.putString("test_parameter", "test_value");
mFirebaseAnalytics.logEvent("test_event", bundle);
And I use the following command to see my events in the debug view:
adb shell setprop debug.firebase.analytics.app com.example.firebaseanalyticssample
And I see the logs with the following commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
I think maybe the problem is the null pointer exception appeared in the logs (the last line):
05-25 09:25:53.056 V/FA (21533): Processing queued up service tasks: 2
05-25 09:25:53.086 V/FA-SVC ( 5655): Logging event: origin=auto,name=_e,params=Bundle[mParcelledData.dataSize=132]
05-25 09:25:53.101 V/FA-SVC ( 5655): Saving event, name, data size: _e, 87
05-25 09:25:53.106 V/FA-SVC ( 5655): Event recorded: EventappId='com.example.firebaseanalyticssample', name='_e', params=Bundle[_o=auto, _r=1, _et=52395, _sc=MainActivity, _si=-5268297315019047641, _dbg=1]
05-25 09:25:53.106 V/FA-SVC ( 5655): Upload scheduled in approximately ms: 500
05-25 09:25:53.111 V/FA-SVC ( 5655): Background event processing time, ms: 31
05-25 09:25:53.621 V/FA-SVC ( 5655): Device receiver got: com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.646 V/FA-SVC ( 5655): Device PackageMeasurementService called. startId, action: 194, com.google.android.gms.measurement.UPLOAD
05-25 09:25:53.651 D/FA-SVC ( 5655): Uploading events. Elapsed time since last upload attempt (ms): 544
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I searched a lot and just found this link regarding the exception above that says it must be an error from another application. but whenever my activity is resumed this exception occurs. I don't think that in my case this exception is caused by another apps.
I checked my sample app a lot of times so that every configuration would be exactly as the guides say. Have you any idea what can be the problem?
android firebase google-analytics firebase-analytics
android firebase google-analytics firebase-analytics
asked May 25 '17 at 5:21
Melika Barzegaran HosseiniMelika Barzegaran Hosseini
330623
330623
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
To enable sending of DebugView data on a connected Android test device for a configured Firebase Analytics app, execute the following command:
adb shell setprop debug.firebase.analytics.app <package_name>
This behavior persists until you explicitly disable it by executing the following command:
adb shell setprop debug.firebase.analytics.app .none.
iOS test device setup is as easy as Android, just use there Xcode command line arguments correspondingly:
–FIRDebugEnabled
and
–FIRDebugDisabled
add a comment |
I changed my development android phone and it got worked. it got worked with samsung SM-P601 and Huawei ِY560-U02 but it just kept throwing the exception below for android mobile phone samsung SM-J120F:
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I checked google play services version in these three mobile phones and it was the same in all of them. I don't know what causes SM-J120F not to work.
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
add a comment |
Try this
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(getApplicationContext());
mFirebaseAnalytics.setAnalyticsCollectionEnabled(true);
mFirebaseAnalytics.setMinimumSessionDuration(10000);
mFirebaseAnalytics.setSessionTimeoutDuration(300);
Bundle bundle = new Bundle();
bundle.putString(FirebaseAnalytics.Param.ITEM_ID,"ID");
bundle.putString(FirebaseAnalytics.Param.ITEM_NAME,"NAME");
bundle.putString(FirebaseAnalytics.Param.CONTENT_TYPE,"image");
mFirebaseAnalytics.logEvent(FirebaseAnalytics.Event.SELECT_CONTENT, bundle);
You can enable verbose logging with a series of adb commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
REF: https://firebase.google.com/docs/analytics/android/start/
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
add a comment |
After performing Enabling debug mode make sure that date&time in your debug device or emulator and in your pc is correct.
add a comment |
Didn't work for me. But from logs, I've found that you need to add flavor name too. So, I had a flavor named "internal" and had to write com.package.name.internal in that adb command above.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44172826%2fcannot-see-events-in-firebase-analytics-debug-view%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
To enable sending of DebugView data on a connected Android test device for a configured Firebase Analytics app, execute the following command:
adb shell setprop debug.firebase.analytics.app <package_name>
This behavior persists until you explicitly disable it by executing the following command:
adb shell setprop debug.firebase.analytics.app .none.
iOS test device setup is as easy as Android, just use there Xcode command line arguments correspondingly:
–FIRDebugEnabled
and
–FIRDebugDisabled
add a comment |
To enable sending of DebugView data on a connected Android test device for a configured Firebase Analytics app, execute the following command:
adb shell setprop debug.firebase.analytics.app <package_name>
This behavior persists until you explicitly disable it by executing the following command:
adb shell setprop debug.firebase.analytics.app .none.
iOS test device setup is as easy as Android, just use there Xcode command line arguments correspondingly:
–FIRDebugEnabled
and
–FIRDebugDisabled
add a comment |
To enable sending of DebugView data on a connected Android test device for a configured Firebase Analytics app, execute the following command:
adb shell setprop debug.firebase.analytics.app <package_name>
This behavior persists until you explicitly disable it by executing the following command:
adb shell setprop debug.firebase.analytics.app .none.
iOS test device setup is as easy as Android, just use there Xcode command line arguments correspondingly:
–FIRDebugEnabled
and
–FIRDebugDisabled
To enable sending of DebugView data on a connected Android test device for a configured Firebase Analytics app, execute the following command:
adb shell setprop debug.firebase.analytics.app <package_name>
This behavior persists until you explicitly disable it by executing the following command:
adb shell setprop debug.firebase.analytics.app .none.
iOS test device setup is as easy as Android, just use there Xcode command line arguments correspondingly:
–FIRDebugEnabled
and
–FIRDebugDisabled
answered May 2 '18 at 9:16
HDTHDT
1,2991127
1,2991127
add a comment |
add a comment |
I changed my development android phone and it got worked. it got worked with samsung SM-P601 and Huawei ِY560-U02 but it just kept throwing the exception below for android mobile phone samsung SM-J120F:
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I checked google play services version in these three mobile phones and it was the same in all of them. I don't know what causes SM-J120F not to work.
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
add a comment |
I changed my development android phone and it got worked. it got worked with samsung SM-P601 and Huawei ِY560-U02 but it just kept throwing the exception below for android mobile phone samsung SM-J120F:
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I checked google play services version in these three mobile phones and it was the same in all of them. I don't know what causes SM-J120F not to work.
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
add a comment |
I changed my development android phone and it got worked. it got worked with samsung SM-P601 and Huawei ِY560-U02 but it just kept throwing the exception below for android mobile phone samsung SM-J120F:
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I checked google play services version in these three mobile phones and it was the same in all of them. I don't know what causes SM-J120F not to work.
I changed my development android phone and it got worked. it got worked with samsung SM-P601 and Huawei ِY560-U02 but it just kept throwing the exception below for android mobile phone samsung SM-J120F:
05-25 09:25:53.666 E/FA-SVC ( 5655): Task exception on worker thread: java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference: vgq.s(:com.google.android.gms:2650)
I checked google play services version in these three mobile phones and it was the same in all of them. I don't know what causes SM-J120F not to work.
answered May 25 '17 at 11:49
Melika Barzegaran HosseiniMelika Barzegaran Hosseini
330623
330623
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
add a comment |
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
Same problem, it works with one samsung but with another one it doesn't o_O.
– mrroboaat
Sep 26 '17 at 9:53
add a comment |
Try this
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(getApplicationContext());
mFirebaseAnalytics.setAnalyticsCollectionEnabled(true);
mFirebaseAnalytics.setMinimumSessionDuration(10000);
mFirebaseAnalytics.setSessionTimeoutDuration(300);
Bundle bundle = new Bundle();
bundle.putString(FirebaseAnalytics.Param.ITEM_ID,"ID");
bundle.putString(FirebaseAnalytics.Param.ITEM_NAME,"NAME");
bundle.putString(FirebaseAnalytics.Param.CONTENT_TYPE,"image");
mFirebaseAnalytics.logEvent(FirebaseAnalytics.Event.SELECT_CONTENT, bundle);
You can enable verbose logging with a series of adb commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
REF: https://firebase.google.com/docs/analytics/android/start/
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
add a comment |
Try this
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(getApplicationContext());
mFirebaseAnalytics.setAnalyticsCollectionEnabled(true);
mFirebaseAnalytics.setMinimumSessionDuration(10000);
mFirebaseAnalytics.setSessionTimeoutDuration(300);
Bundle bundle = new Bundle();
bundle.putString(FirebaseAnalytics.Param.ITEM_ID,"ID");
bundle.putString(FirebaseAnalytics.Param.ITEM_NAME,"NAME");
bundle.putString(FirebaseAnalytics.Param.CONTENT_TYPE,"image");
mFirebaseAnalytics.logEvent(FirebaseAnalytics.Event.SELECT_CONTENT, bundle);
You can enable verbose logging with a series of adb commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
REF: https://firebase.google.com/docs/analytics/android/start/
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
add a comment |
Try this
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(getApplicationContext());
mFirebaseAnalytics.setAnalyticsCollectionEnabled(true);
mFirebaseAnalytics.setMinimumSessionDuration(10000);
mFirebaseAnalytics.setSessionTimeoutDuration(300);
Bundle bundle = new Bundle();
bundle.putString(FirebaseAnalytics.Param.ITEM_ID,"ID");
bundle.putString(FirebaseAnalytics.Param.ITEM_NAME,"NAME");
bundle.putString(FirebaseAnalytics.Param.CONTENT_TYPE,"image");
mFirebaseAnalytics.logEvent(FirebaseAnalytics.Event.SELECT_CONTENT, bundle);
You can enable verbose logging with a series of adb commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
REF: https://firebase.google.com/docs/analytics/android/start/
Try this
private FirebaseAnalytics mFirebaseAnalytics;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mFirebaseAnalytics = FirebaseAnalytics.getInstance(getApplicationContext());
mFirebaseAnalytics.setAnalyticsCollectionEnabled(true);
mFirebaseAnalytics.setMinimumSessionDuration(10000);
mFirebaseAnalytics.setSessionTimeoutDuration(300);
Bundle bundle = new Bundle();
bundle.putString(FirebaseAnalytics.Param.ITEM_ID,"ID");
bundle.putString(FirebaseAnalytics.Param.ITEM_NAME,"NAME");
bundle.putString(FirebaseAnalytics.Param.CONTENT_TYPE,"image");
mFirebaseAnalytics.logEvent(FirebaseAnalytics.Event.SELECT_CONTENT, bundle);
You can enable verbose logging with a series of adb commands:
adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC
REF: https://firebase.google.com/docs/analytics/android/start/
edited May 25 '17 at 12:30
Francisco Melicias
302111
302111
answered May 25 '17 at 6:28
san666san666
1
1
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
add a comment |
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
1
1
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
it didn't make any difference.
– Melika Barzegaran Hosseini
May 25 '17 at 7:44
add a comment |
After performing Enabling debug mode make sure that date&time in your debug device or emulator and in your pc is correct.
add a comment |
After performing Enabling debug mode make sure that date&time in your debug device or emulator and in your pc is correct.
add a comment |
After performing Enabling debug mode make sure that date&time in your debug device or emulator and in your pc is correct.
After performing Enabling debug mode make sure that date&time in your debug device or emulator and in your pc is correct.
answered Oct 9 '17 at 15:15
Ashraf AtefAshraf Atef
7114
7114
add a comment |
add a comment |
Didn't work for me. But from logs, I've found that you need to add flavor name too. So, I had a flavor named "internal" and had to write com.package.name.internal in that adb command above.
add a comment |
Didn't work for me. But from logs, I've found that you need to add flavor name too. So, I had a flavor named "internal" and had to write com.package.name.internal in that adb command above.
add a comment |
Didn't work for me. But from logs, I've found that you need to add flavor name too. So, I had a flavor named "internal" and had to write com.package.name.internal in that adb command above.
Didn't work for me. But from logs, I've found that you need to add flavor name too. So, I had a flavor named "internal" and had to write com.package.name.internal in that adb command above.
answered Nov 12 '18 at 15:21
GudinGudin
1,28831433
1,28831433
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44172826%2fcannot-see-events-in-firebase-analytics-debug-view%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown