Flurry noob - how to init?

Solar2D Monetization (in-app purchases, ads, etc.)
#1

I’ve got my flurry app ID and required the library. Calling analytics.init(<code>) seems to lock the app up.

How do I get this working? What small piece have I forgotten?

Yes, I had this working in my previous game, but now it just freezes the XCode sim, iOS device and Android devices.

Thanks and sorry!

#2

@horacebury,

Are you including Flurry as a plugin in build.settings?  (It changed to a plugin starting in build 1203.)

It would be helpful if you posted your exact code.

  • Andrew
#3

Damn. I thought that’s what had happened but I couldn’t find any reference to that in the regular API docs. Didn’t think to check the Plugin docs.

Thanks,

M

#4

For those finding this and wanting to know:

http://docs.coronalabs.com/daily/plugin/flurry/index.html

#5

Also, a word to the wise/warning: After including the plugin in build.settings, the following does not work.  

[lua]

    analytics:setCurrentProvider(“flurry”)

    analytics.init(“FLURRYID”)

[/lua]

The project will build fine, but Flurry will not actually get initialized and analytics won’t get reported.

Instead, you have to put setCurrentProvider after init (which seems strange, since how would analytics “know” what the ID was for when it was called):

[lua]

    analytics.init(“FLURRYID”)

    analytics:setCurrentProvider(“flurry”)

[/lua]

Even more surprisingly, you can omit setCurrentProvider entirely and just write:

[lua]

    analytics.init(“FLURRYID”)

[/lua]

  • Andrew
#6

@horacebury,

Are you including Flurry as a plugin in build.settings?  (It changed to a plugin starting in build 1203.)

It would be helpful if you posted your exact code.

  • Andrew
#7

Damn. I thought that’s what had happened but I couldn’t find any reference to that in the regular API docs. Didn’t think to check the Plugin docs.

Thanks,

M

#8

For those finding this and wanting to know:

http://docs.coronalabs.com/daily/plugin/flurry/index.html

#9

Also, a word to the wise/warning: After including the plugin in build.settings, the following does not work.  

[lua]

    analytics:setCurrentProvider(“flurry”)

    analytics.init(“FLURRYID”)

[/lua]

The project will build fine, but Flurry will not actually get initialized and analytics won’t get reported.

Instead, you have to put setCurrentProvider after init (which seems strange, since how would analytics “know” what the ID was for when it was called):

[lua]

    analytics.init(“FLURRYID”)

    analytics:setCurrentProvider(“flurry”)

[/lua]

Even more surprisingly, you can omit setCurrentProvider entirely and just write:

[lua]

    analytics.init(“FLURRYID”)

[/lua]

  • Andrew