Awesome, Thank you so much for your responses Joshua. Its so helpful to know that someone at corona is listening and bouncing ideas so we can narrow it down. Working together knowing someone is listening/caring really matters to us developers!
Anyway, I tried your suggestion and it worked, so I went through and found out the issue (I believe, we’ll have to wait a couple hours for flurry to update and see what events made it through). Here was the problem.
I had this:
local analytics_logEvent = analytics.logEvent
and then down below:
analytics_logEvent(“MyEvent”)
So what I believe was happening is that there is a default implementation of analytics.logEvent that gives the unsupported warning, until you make a successful analytics.init and then the variable changes to a different implementation. Since I was using the cached version, it wasn’t getting the logged in version, so I just changed my analytics_logEvent to analytics.logEvent and stuff started working (or at least not reporting errors)
Are flurry event parameters going to work with the flurry api build into 1031? thats why I originally built my own flurry support for ios, but I believe they are supported there now. If event parameters work with the analytics.logEvent api we are going to be good to go! (assuming I see my stuff show up later tonight) [import]uid: 122310 topic_id: 36091 reply_id: 143366[/import]