No data seen in Flurry dashboard

Solar2D iOS
1

Is flurry working?

Here’s my code (straightforward as per the sample app):

main.lua: local applicationKey = "XXX..." local analytics = require "analytics" --analytics:setCurrentProvider("flurry") analytics.init(applicationKey) analytics.logEvent("Game Started") build.settings (in part): plugins = { ["CoronaProvider.ads.iads"] = { publisherId = "com.coronalabs", }, ["CoronaProvider.ads.vungle"] = { publisherId = "com.vungle", }, ["CoronaProvider.native.popup.social"] = { publisherId = "com.coronalabs", }, ["CoronaProvider.analytics.flurry"] = { publisherId = "com.coronalabs", }, },

After 24 hours I’ve seen nothing on the Flurry site when I check my application.

I’ve tried with and without analytics:setCurrentProvider(“flurry”)

I get a “You are not currently tracking any Events” in the Events section and Usage is an empty graph.

Build is 1206 and console shows "Flurry: Starting session on Agent Version …

I’ve tested on device and I’m a first time Flurry user. Thanks!

2

Hmmm…now I see some data.

It appears that the call to analytics:setCurrentProvider(“flurry”) was causing the failure.

3

I’m having exactly the same problem - extremely frustrating that I launched my new game (build 1210) and I’m not getting any analytics reporting back. Can someone from Corona confirm that skipping the “analytics:setCurrentProvider(“flurry”)” call will fix the problem?

4

I experienced the same thing.  Confusingly, placing analytics:setCurrentProvider(“flurry”) after the call to analytics.init() works fine, but placing it before (which seems more natural) causes Flurry not to load at all.

  • Andrew
5

Andrew - did you try not calling it at all like MAS1?

6

Yup, not calling setCurrentProvidrr at all also worked for me.

7

OK - I’ll give it a try.

Bloody frustrating as I lost a crap-load of extremely valuable data by not being able to get any usage data from my first week of release!

8

@beernathan,

Flurry is certainly working well since omitting the setCurrentProvider() call.

Now that I’ve seen user session lengths in Flurry I wish I hadn’t bothered - LOL! Hides head in sand… :) 

9

He, he, he, sob, sob, sob…

10

Hmmm…now I see some data.

It appears that the call to analytics:setCurrentProvider(“flurry”) was causing the failure.

11

Thanks for the info guys. I lost also all flurry data since my last build and I think that is the reason.

Has anyone submitted a bug for Corona?

12

By the way, just confirmed: I removed the setCurrentProvider()  and flurry is now working again.

13

Just in case, I submitted the bug (Case 27237)

14

Sorry - had been on the road.

No, I didn’t ever submit a case - just took out the call the setCurrentProvider().

So… what build did you get it working in?

Thanks,

Nathan.

15

I am using daily build 2013.1235.  But I got it only working by removing the function setCurrentProvider.

Corona people are already taking a look on it.

16

Ahh, OK thx.

17

I’m having exactly the same problem - extremely frustrating that I launched my new game (build 1210) and I’m not getting any analytics reporting back. Can someone from Corona confirm that skipping the “analytics:setCurrentProvider(“flurry”)” call will fix the problem?

18

I experienced the same thing.  Confusingly, placing analytics:setCurrentProvider(“flurry”) after the call to analytics.init() works fine, but placing it before (which seems more natural) causes Flurry not to load at all.

  • Andrew
19

Andrew - did you try not calling it at all like MAS1?

20

Yup, not calling setCurrentProvidrr at all also worked for me.