When Corona will update Flurry plugin?

Corona Marketplace Corona Community Plugins
1

Flurry latest version is 7.5.2 while Corona still uses Flurry 4.3.2 ! (more than 2 years old!!)

That 4.3.2 version is old and still sends requests without using HTTPS, which is unacceptable for several companies. In fact, iOS 9 blocks by default non-https requests, which makes the flurry plugin not work unless you whitelist the flurry domain.

We have people in the forum requesting a update for years and I really don’t get why Corona can just update it… It wouldn’t event take 1 day to do it…

2

Engineering is looking into it

3

Thanks Rob and Engineering. We really appreciate.

If I can help with anything, just ping me.

4

Any news Rob?

5

We are reporting users in Flurry are only at about 10% of actual users as reported by Apple and Google. So Flurry is not working in all cases perhaps it’s not working in iOS 9 as pointed out by @Renato’s https discovery.

Any word when from Engineering on this matter?

6

Engineering is working on it. No ETA. It’s not a simple case of just dropping in their new SDK and hitting build.

Rob

7

What about just making the enable httpS option available for us on the current version? This should be simple enough. Flurry has that option since version 3 (it was just not set ON by default).

8

For future viewers, it appears that Corona updated Flurry (https://docs.coronalabs.com/plugin/flurry-analytics/index.html).

Can u confirm that Rob?

9

Hi Renato,

You have a keen eye. :slight_smile: Yes, this is true, but we’re putting a few finishing touches on this so I suggest you wait a couple days before you dive into it.

Brent

10

We are getting close but we have not officially announced it yet. I don’t know that all the pieces are in place yet. Watch the blog for an announcement soon.

11

Awesome! I’ll close my other thread.

12

The new Flurry Analytics plugin is here!  See: https://coronalabs.com/blog/2016/04/12/new-flurry-analytics-plugin-now-available/

Rob

13

Thanks @Rob, @Brent and Eng team.

14

Does this mean apps using the old one have to be updated to the new one or are they still “safe” for the time to come?

15

If you’re happy with the current Flurry and it’s reporting values you expect and you have put in the ATS bypass in your build.settings to allow it to reach http: addresses instead of https: then for now I don’t see why you would have to update. But at some point we will deprecate and then remove the old one. I just don’t know when.

Rob