Firebase screen views double up?

[Ricky D'Amelio]

We are seeing some very high screen view numbers, and as much as I'd like them to be true, I did some debug digging in the console.

It appears that every time I change tabs, or push onto a navigation stack in our iOS app, two "screen_view" events are fired. 

You can see here I've come from a tab called Today and gone into the News tab. Why are there two screen_view events, and scarily, does this mean that we are reporting two screen views whenever someone changes tabs or pushes something onto the navigation stack?

P.S: I will just add, again, that this is just one reason why automatic screen tracking is a bad thing to force people to participate in. We have no idea of what activity is occurring in our own app and it's very annoying.

[Kato Richardson]

Hi Ricky,

Can you make sure you're on the latest SDK versions, turn on debug logging, and share some of the output around the screen switching? If you have BigQuery enabled, might also be interesting to see what that's reporting.

☼, Kato

--
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-tal...@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/11f812e3-484f-46ed-a81f-d794c5be9269%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Ricky D'Amelio]

Hi Kato.

Thanks for the response. We are indeed using BigQuery and the results there are much more realistic. The below query reports 36% of the total that Firebase does for the same date range. I am querying by screen name because all the screens we want to track in the app are named.

SELECT 

  count(1) as count

FROM 

  `xxx_*`,

  UNNEST(event_params) as params

WHERE

  (_TABLE_SUFFIX BETWEEN FORMAT_DATE("%Y%m%d", "2019-05-06") AND FORMAT_DATE("%Y%m%d", "2019-05-08"))

   AND

  (event_name = "screen_view" AND params.key = "firebase_screen")

We are on one of the latest Firebase SDK versions, version 5.20.1. All our view controllers receive the right sequence and number of viewWillAppear:, viewDidAppear:, etc methods. I am uploading a snippet of the console when I change from one tab (Today) to another tab (News). For brevity I am uploading it to a separate file here.

Please let me know if you require anything further to try pinpoint this issue.

On Saturday, 25 May 2019 01:46:43 UTC+10, Kato Richardson wrote:

Hi Ricky,

Can you make sure you're on the latest SDK versions, turn on debug logging, and share some of the output around the screen switching? If you have BigQuery enabled, might also be interesting to see what that's reporting.

☼, Kato

On Thu, May 23, 2019 at 6:52 AM Ricky D'Amelio <ricky....@crocmedia.com> wrote:

We are seeing some very high screen view numbers, and as much as I'd like them to be true, I did some debug digging in the console.

It appears that every time I change tabs, or push onto a navigation stack in our iOS app, two "screen_view" events are fired. 

You can see here I've come from a tab called Today and gone into the News tab. Why are there two screen_view events, and scarily, does this mean that we are reporting two screen views whenever someone changes tabs or pushes something onto the navigation stack?

P.S: I will just add, again, that this is just one reason why automatic screen tracking is a bad thing to force people to participate in. We have no idea of what activity is occurring in our own app and it's very annoying.

--
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 fireba...@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/11f812e3-484f-46ed-a81f-d794c5be9269%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ricky D'Amelio]

Okay so have been doing some further digging, it seems if I disable the "naming" of view controllers, the double events stop.

Example:

- (void)viewDidAppear:(BOOL)animated

{

    [super viewDidAppear:animated];

    [FIRAnalytics setScreenName:@"News" screenClass:nil]; // Commenting out this line works.

}

I struggle to understand how this is happening or wrong. Your documentation states:

/// ...
/// The class name can optionally be overridden by calling this

/// method in the viewDidAppear callback of your UIViewController and specifying the

/// screenClassOverride parameter. setScreenName:screenClass: must be called after

/// [super viewDidAppear:].
/// ...

And I believe this is what we are doing?

On Saturday, 25 May 2019 01:46:43 UTC+10, Kato Richardson wrote:

Hi Ricky,

Can you make sure you're on the latest SDK versions, turn on debug logging, and share some of the output around the screen switching? If you have BigQuery enabled, might also be interesting to see what that's reporting.

☼, Kato

On Thu, May 23, 2019 at 6:52 AM Ricky D'Amelio <ricky....@crocmedia.com> wrote:

We are seeing some very high screen view numbers, and as much as I'd like them to be true, I did some debug digging in the console.

It appears that every time I change tabs, or push onto a navigation stack in our iOS app, two "screen_view" events are fired. 

You can see here I've come from a tab called Today and gone into the News tab. Why are there two screen_view events, and scarily, does this mean that we are reporting two screen views whenever someone changes tabs or pushes something onto the navigation stack?

P.S: I will just add, again, that this is just one reason why automatic screen tracking is a bad thing to force people to participate in. We have no idea of what activity is occurring in our own app and it's very annoying.

--
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 fireba...@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/11f812e3-484f-46ed-a81f-d794c5be9269%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kato Richardson]

Hm, that seems odd. I would guess this is a bug. Could you file it here with the details you shared above? 

Feel free to ping me the case id (found in the auto reply subject) if you need any help.

☼, Kato

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@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/0874c612-036a-4475-bf57-992156110f95%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ricky D'Amelio]

Thanks Kato.

Filed a brief report so far with the ID 1-2398000026805. Any urgency on this would be greatly appreciated, as it is causing significant reporting challenges.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/0874c612-036a-4475-bf57-992156110f95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kato Richardson]

After looking over the internal discussion, it looks like these are the relevant threads. Recommend adding your findings and thoughts there. 

https://github.com/firebase/firebase-ios-sdk/issues/1894

https://github.com/firebase/firebase-ios-sdk/issues/2181

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@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/8b7fa5bb-e00c-4fb2-b4c5-0e7f9212c6c0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.