1

I am logging some custom events on Firebase Analytics, but some errors keep getting logged for automatic events (such as screen_view) along with the custom events, whether I call them explicitly or not. When I log regular custom events (a button click, for example), I can see them on DebugView without any errors.

I have validated the rules for names (maximum of 36 chars for event key, maximum of 100 for value) as this answer from Chintan points and confimed that no event has reserved names.

I keep getting the error code 13 - which means Event name is reserved, according to the Analytics Error Codes.

Any ideas of what might be happening? Anybody facing the same issue?

Here's how the error is shown at DebugView:

enter image description here

Thanks in advance!

Edit:

Adding a piece of the log, as requested:

A piece of the Logcat log

sednanre
  • 478
  • 5
  • 16
  • can you please provide some log from the debug log, especially those errors after the screen view events? Thanks – adbitx Feb 02 '18 at 17:58
  • @adbitx just added a piece of the log. I suppose the interesting part here is the error in red, where it says "Name is reserved", but I'm pretty sure I am not using any of the Firebase reserved names. – sednanre Feb 07 '18 at 11:58
  • Thank you. Do you have GTM SDK by any chance? – adbitx Feb 08 '18 at 16:55
  • @adbitx yes, it's imported in my app gradle file. – sednanre Feb 09 '18 at 11:07
  • As Dan stated below, do you log any event with the name "screen_view" too? – adbitx Feb 10 '18 at 18:01
  • @adbitx nope, I'm only using the `setCurrentScreen()` method, which is the default method for `screen_view` logging. None of my custom events gave "screen_view" in their names. – sednanre Feb 12 '18 at 17:46
  • Hey @sednanre, I'm facing the same issue on my side can you suggest me a better solution to solve the regular calling on screen_view and user engagement. – Mohit Lakhanpal Jul 13 '20 at 14:00
  • @MohitLakhanpal still haven't found an answer :/ We ended up using Amplitude to log all events we needed (both screen visualisation and button clicks for example). Took more work once I had to manually tag every event in every Activity/Fragment, but it did work - not sure it's still works like this to these days though. – sednanre Jul 15 '20 at 18:32

2 Answers2

4

Can you check to see if you are using your event names prefixed as "firebase_", "google_" or "ga_"?

As per the official documentation **The "firebase_", "google_" and "ga_" prefixes are reserved and should not be used.**

AniV
  • 3,997
  • 1
  • 12
  • 17
  • None of the events have these prefixes, I have checked the rules at the official documentation. They're all screen names in lowercase starting with alphabetic characters, with a lot less than 36 characters. I am also sending some custom button click events, but they also follow the rules (and these don't even log an error at DebugView). – sednanre Jan 24 '18 at 11:33
2

According to the API docs for Analytics.Event, screen_view is a reserved event name and cannot be used for logging your own custom event.

Dan Morenus
  • 1,068
  • 8
  • 12