I see data but I am using the old version before the fix.
Adrian
I see data but I am using the old version before the fix.
Adrian
The sample code works!
I am not sure what is wrong with mine. I have already disabled all other plugins, leaving only Google analytics but still it doesn’t work.
I finally found what is the issue!
googleAnalytics.logScreenName() does not send the logs to the Google Analytics server. Logs are only sent only when googleAnalytics.logEvent is called. As such, for my apps which log only the screens will not work. Can this be fixed?
To add, logScreenName will save the logs locally. Only when logEvent is called, all saved logs (including the screens) will be sent.
This makes more sense. I am not using googleAnalytics.logScreenName() so I would not see the issue.
The sample app has screen logging. Is it not working?
Hi Rob. If you are just logging the screen, then data will not be sent. In the sample app, you need to trigger log event call like pressing the buttons for the screen logs (saved previously) to be submitted to Google Analytics.
I know that when I wrote the announcement, I used the sample app and I saw screen events being sent to the server They may have been attached to buttons in the sample, but the API calls for screens was sending data.
If you use the sample and press the buttons for the screens and see events, then the API calls are working as expected.
Maybe it’s time to share some code?
Rob
Basically you can test it by launching the sample app and then exit it without taking pressing anything on screen, the log screen function will be called in the show function of scene 1 but no data will be sent to the server.
In the Xcode console, you will also notice each time logScreen is being called, the log is only saved but not submitted. Only when the logEvent is being called, all logs (screens and events) will be submitted together.
This is an issue if I have an app that uses only logScreen. Of course, a workaround that I am using now is to do a logEvent call when the app exit which will trigger the submission of screen logs saved earlier.
I’m observing the same behavior. The logScreenName method is not submitting to the analytics server until a logEvent call is made. This is only a problem on iOS.
Then we need a bug report. If our sample isn’t working, you can use it as the project that you need to submit. Please post the case ID # back here when you get it.
Thanks
Rob
Good to know it is happening only to iOS as I have not really checked out the logs for Android. Some of my apps have a mix of log screen and log events so can’t really tell if there is an issue or not.
I have submitted a bug report and once again I did not receive any email on the case number. This is the third time I have tried submitting a bug report and not getting any response. Can you help me look into the bug tracking system? I am able to receive other emails from Corona like the newsletters and the forum notification on new posts.
Thanks.
Case 45724
Any updates for this issue?
According to Engineering this has been fixed. Since its a plugin, you should get the changes the next time you build without needing a new Corona build.
Can someone confirm this?
Rob
Just tested it with a new build. Still the same issue.
This thread is kind of long and I think there are multiple issues being talked about.
Specifically what is not working?
What errors are you seeing?
I’ll update the bug report because the engineers feel they have fixed this.
Rob
If I’m following this correctly, the plugin doesn’t report logScreenName activity to Google Analytics until the app reports a logEvent activity. This only happens on iOS. Falcon777 please correct me if I’m wrong.
Well the thread started out about IFDA errors. This is why hijacking threads is a bad thing. I can bounce this back, but I have to have confirmation that the logScreenName is still a problem.
Rob
Yes, that’s right. Sorry for the late reply. Seems like the thread notification feature is not working thus I did not get notified that there is a new update to this thread.