Flurry Blog

Flurry Product Updates

Current Articles | RSS Feed RSS Feed

About iPhone Developer Program License Agreement (3.3.9)

Posted by Peter Farago on Wed, Apr 14, 2010 @ 10:27 AM
  
  
  
  
Add to delicious  delicious  
  

 

Dear developer,

As you may be aware, Apple included new language in the iPhone Developer Program License Agreement that it made available along with the OS 4.0 SDK beta last Thursday, April 8.

Part of section 3.3.9 states:

"Notwithstanding anything else in this Agreement, Device Data may not be provided or disclosed to a third party without Apple's prior written consent. Accordingly, the use of third party software in Your Application to collect and send Device Data to a third party for processing or analysis is expressly prohibited."

We believe that this affects our services as well as most if not all ad network services.

Flurry has contacted Apple and is seeking clarification on the language. Our goal is to move forward in a way that continues to provide valuable insight to developers about how to build better apps, while complying with the new Agreement. We believe this is possible, and in a way that still serves your needs for real-time information.

More than anything, we want you to be aware that we are focused on this issue and looking to resolve it as soon as possible, which could include issuing an updated SDK. We understand that not having accurate information can be unsettling. In the meantime, the application submission process appears to be unchanged at Apple, and we are closely monitoring the situation.

We will continue to keep you abreast of any developments.

Thanks,

The Flurry Team


Tags: ,

Comments

Your service is awesome. Thanks for clarifying your position.
Posted @ Wednesday, April 14, 2010 11:15 AM by Chad Smith
I second Chad's comment. I'm sure that Apple don't intend to kill the entire middleware & tools sector, surely they're just after FLASH and people dumping low-grade ports on their nice platform and ruining the experience for everyone.
Posted @ Wednesday, April 14, 2010 2:21 PM by Ian Harper
Uh Ian, 3.3.1 is about Flash and middleware. This 3.3.9 change has nothing to do with Flash, and everything to do with getting rid of services like Flurry.
Posted @ Wednesday, April 14, 2010 4:18 PM by Matt Rix
So does this mean if we include Flurry analytics in our app it will get rejected?
Posted @ Thursday, April 15, 2010 1:56 PM by Adam Levy
@Adam. Still in line with our comment in the blog, the Apple submission process appears to be unchanged. There is also some coverage you can refer to on VentureBeat that includes information the reporter received from other sources. 
 
http://venturebeat.com/2010/04/14/apple-ad-analytics/
Posted @ Thursday, April 15, 2010 11:09 PM by Peter Farago
My app got rejected for using the Flurry analytics with location library. They cited that you can't use CoreLocation libraries for analytic purposes. When I replaced it with the regular Flurry libraries, the accepted the app...
Posted @ Friday, April 16, 2010 12:42 PM by Dave
Dave - 
Does your app normally use CoreLocation? 
 
Posted @ Monday, April 19, 2010 9:28 AM by Candemir
Dave -  
 
Your application was probably rejected because it only uses CoreLocation for analytic/advertising purposes. Apple has stated that they do not approve of such uses, and only if your application uses location information will it be allowed.
Posted @ Wednesday, April 21, 2010 7:54 PM by Dan
Any clarification on this yet? I really want to use Flurry, but if it will get me rejected, then of course I won't.
Posted @ Friday, May 14, 2010 2:04 AM by Lynn
Just a follow up to Lynn's comments really, but any clarification yet? Also if we submit and get approval before OS 4.0 comes out, do you think we'll get approved AND remain approved after OS 4.0 is released?
Posted @ Tuesday, May 18, 2010 7:21 AM by Mark Allen
My app was just rejected citing 3.3.8 and I do not use any location anything in the app. I'm using the basic FlurryLib and not using the location part of Flurry at all.
Posted @ Wednesday, May 19, 2010 8:34 PM by Andria
Hi Andria, 
 
I'm not sure why you would have been rejected citing 3.3.8 due to use of the FlurryLib as it makes no use of CoreLocation. Do you include the CoreLocation framework in your application at all? Feel free to contact support@flurry.com for more help on this issue as we'd love to help you resolve it. 
 
Sean
Posted @ Thursday, May 20, 2010 10:07 AM by Sean
I had an update approved on May 18 with the non-locating flurry library in it... it would seem to me (and I'm not a lawyer) that the new language applies to OS4 but who knows. I sure hope Flurry gets some clarification soon--so we all know what we need to do!
Posted @ Tuesday, June 01, 2010 10:58 PM by Kim
Hi, 
 
any news from Apple if we are allowed to use flurry in applications built with SDK 4.0? 
 
Since Steve said at D8 (http://www.engadget.com/2010/06/01/steve-jobs-live-from-d8/) that Flurry pissed Apple off, what does it mean for us Developers? Will we still be able to use Flurry? 
 
Please, any clearification or information would be nice. 
 
Stefan
Posted @ Wednesday, June 02, 2010 9:14 AM by Stefan
I am also now very interested in an update too, after having just watched Jobs at D8: 
http://www.9to5mac.com/jobs_at_d_video #7 
 
He gives Flurry (specifically) a bit of a roasting. 
 
Brett
Posted @ Wednesday, June 02, 2010 9:35 AM by Brett
Any updates on using CoreLocation in apps that only use CoreLocation for analytic/advertising purposes? Since Apple uses CoreLocation to place ads for iAd doesn't the notion of a level playing field apply to all app developers wanting to use CoreLocation for analytic/ad placement purposes? From Apple's site (http://advertising.apple.com/); 
 
"Standard targeting options on the iAd Network include:  
 
Demographics 
Application preferences 
Music passions 
Movie genre interests 
Television genre interests 
Location " 
 
Any comments/advice on using CoreLocation for analytic/advertising purposes only? 
 
Danton 
Posted @ Wednesday, July 21, 2010 8:02 AM by Danton Chin
Comments have been closed for this article.