[URGENT] Apple rejects apps using IDFA, issue with analytics.* (Flurry)

Solar2D iOS
#1

Hi guys,

Following discussion on IRC channel, I post here:

http://techcrunch.com/2014/02/03/apples-latest-crackdown-apps-pulling-the-advertising-identifier-but-not-showing-ads-are-being-rejected-from-app-store/

The problem is, Flurry version 4.2.4 uses IDFA and people already report their apps were rejected because of this.

People also say that Flurry version 4.3.1 has this problem fixed.

Docs on analytics are outdated, saying version 4.1 (iOS) is used. From what I can see in the Flurry console, Corona plugin “CoronaProvider.analytics.flurry” actually uses version 4.2.3

I don’t know if this version uses IDFA too, but it well may be as it is close to troublesome 4.2.4

Corona staff, could you advise?

#2

Jack227 - we are looking into this and will have more info soon…

#3

Flurry has recently learned that Apple has rejected some apps it believes are using the Identifier for Advertising (IDFA) without including ad functionality.  Flurry does not collect the IDFA unless an app includes the AdSupport.framework for ad functionality. We are seeking clarification with Apple and we will update our affected customers as we learn more over the next several days.  If you believe your app has been rejected for similar reasons, please email support@flurry.com with details.

  • The Flurry Team
#4

Update:

New version of one of our apps was approved for iTunes today, with Flurry plugin being there. Either we got lucky, or version 4.2.3 might not have this IDFA usage, or who knows what :slight_smile:

#5

Update:

Flurry has fixed this problem only in recent 4.3.2, so version 4.3.1 is not good too.

Any ETA on a fix for analytics plugin?

#6

I have several projects that might be affected.  Any news?

#7

We understand that some developers recently experienced a rejection from the App Store for use of the IDFA without the AdSupport.Framework. Flurry’s SDK does not collect the IDFA unless an app includes the AdSupport.Framework, but we believe a reference to the term “IDFA” in our SDK code may have triggered the rejection by Apple. We have updated our SDK code to resolve the issue.

Please download the updated SDK, now available in the Flurry portal, for use with any future submissions to the App Store.

This issue has been a high priority for Flurry over the last several days. We appreciate your patience as we worked to resolve it.

#8

is flurry plug-in for corona fixed?

#9

If you do a build with 2169 or later, it will now include the latest Flurry SDK.  The reason we chose 2169 is because that is the build of Corona which takes out the references to ASIdentifierManager.  Be advised that we just replaced the SDK and rebuilt the plugin and have not tested it yet.

#10

where to get this build 2169 cause im using build 2100 right now.

#11

You need access to daily builds which means you have to be Pro/Enterprise to get it.

#12

@domskie13, Daily builds are only available to Pro and Enterprise subscribers.  The forums say you are  a starter (which isn’t always accurate) and if that’s the case, you will have to wait until we release a new public build, and I do not have an ETA on that yet.

Rob

#13

oh…sorry…im using other account in corona

#14

If I understand this correctly the corona core ( in daily builds below 2169 ) has references to ASIdentifierManager.

Does this mean that any app we submit to apple with builds below 2169 might get rejected if it doesn’t serve adds?

#15

According to the Tech Crunch article, Apple is going to reject apps that use the ASidentiferManager library that doesn’t show ads.  We had it in our core as an API call that let you get the identifier even though you likely don’t use it.  I don’t know that we’ve heard any reports about Corona Apps being rejected because of this, but as a precaution, we’ve moved anything using this library and identifier to a plugin as of 2169.

Rob

#16

Does that mean we have to require a plugin to call:

system.getInfo ( “advertisingIdentifier” ) and system.getInfo ( “identifierForVendor” )

from now on?

I really hope they do not reject all apps thats built with DB below 2169, because then I am in deep trouble…

I have to submit an app ( I have started working on for a client over a year ago ) thats built with GE 1.0 and it is far to complex to port to GE 2.0.

#17

I don’t think you need to require a plugin.  There are some features that we include based on just the API call but I’ll ask Engineering.

Rob

#18

Good news

After experiencing this problem this past couple of weeks, Apple just accepted our app with the latest Flurry build.

#19

Can we get this Flurry update in the pre-graphics 2.0 build as well? I am also pretty far past the point of being able to upgrade my game to Graphics 2.0 as I am using Spriteloq for sprites and it won’t work with the latest builds.

#20

Have you tried downloading the legacy sprite  library from our github repository and just dropping it in the folder with your main.lua and setting graphicsCompatibility = 1 in your config.lua?  That should get you very close to Graphics 1 behavior with a Graphics 2.0. 

The other work around is to include at least 1 ad in the app.

Rob