Just got this, can't make heads or tails from it? Simply updated the app with iPhone 5 support and some new plugins. --------------------- Non-public API usage: Apps are not permitted to access the UDID and must not use the uniqueIdentifier method of UIDevice. Please update your apps and servers to associate users with the Vendor or Advertising identifiers introduced in iOS 6. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. If you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's nine-digit Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged, to [email protected]. For further information, visit the Technical Support Information page. -------------------------- Anyone ever get this? Cheers, David

Yes, i did receive this message today after adding YouTube Playlist plugin, Chartboost and Flurry to my app, I remove Flurry and still get the same message. Will work on other test tomorrow morning and post the result.

Just got it again with another app update, what the heck? David

I found this out: http://www.buzztouch.com/forum/thread.php?fid=06DB0BCB0394857 A year ago it was the Twitter/Facebook plugins. But I've submitted multiple apps with these (the newest ones in the market that were free) and they worked fine. Wondering if its the same issue. Cheers, David

BT Push or Scringo must use a UUID. As of May 1, UUID usage is not allowed. Jake

Oh crap... is my Scringo doing that? I wonder if it's appirater, I just added that to both new projects that were rejected. I betcha it's that. Let me try uploading without appirater, and try scrigno afterwards if same issue, and will get back to you guys. David

Possibly Scringo has updated their API by now. Check out their website, maybe the one with the BT downloads is outdated? Jake

Possibly.. will check. Confirmed: It's not appirater, same rejection without it in the app. Knocking on Scringo's door next. David

Fun fact. I can't test Scringo, removing the framework brings errors galore due to it's integration. Let me take scringos's latest framework and try that. David

Scringo is not the problem. Socialize is not the problem. I downloaded a clean source code again and apple is no longer yelling at me. SUPER weird.

The UUID battle continues. Firstly though, removing the Scringo package is super easy (if it matters). 1) remove the Scringo folder from the BT_core folder. In Xcode, remove from project. 2) remove two references to the #import <Scringo/ScringoAgent.h> This is in two places int he project. At the top of the .m file in app delegate and at the top of the BT_viewController.m file. Remove these two references, remove the folder, scringo is gone. BUT, you'll also need to remove the "call" to Scringo in your app's delegate. Line 591 or so... [ScringoAgent startSession:@"YOUR-SCRINGO-APP-ID" locationManager:nil]; Remove that. Ok, UUID stuff. All sorts of SDK's used to use the previously allowed method to get a devices unique id. BT core hasn't done this in over a year. We removed it as soon as it was no longer allowed. We're using a different, and recommended way to get a unique string for each device. I'll bet anything one of your SDK's was doing something "old" and not allowed anymore.

so we can't add scringo until there is a fix at their sdk?

@Georgios: I'm not saying that, I'm just saying that all sorts of SDK's exist (in the wild) that continue to use the older, not allowed anymore methods to get a device's unique Id. I would highly doubt that Scringo does this. I'll see if I can find out but I dont' think it's Scringo doing it.

Ok David I see...I have no doubt that you'll copy out with this...thanks for your support! :)

@David.. as always you figured it out. I BELIEVE the issue was that I was using a older Socialize version (which p.s. you guys should also totally integrate!). I updated my framework to 2.8.3 and submitted both apps with no problems. I was using 2.7.2 before. That was the only change I made and apple let my app go into wait for review instead of insta-reject. Good to know that Apple changed the rules, I had no idea. Thanks a ton. This week has been full of weird errors and problems that I just can't seem to understand/solve without you. LOL. Hopefully the last one for a long time! Cheers, David.

Hello !, I did receive the same message (automatic rejection for Non-public API usage) and my app does not contain the Socialize Framework. I remove Scringo as stated before, and commented // all #import and startSession statement and still got Invalid Binary message... Will work on other test tomorrow morning and post the result. Anyone ever getting approve without problem ?? Thanks.

ABC Scringo is not the problem in this case. Did you add anything else? Like Socialize? David

Hello ! My app does not contain the Socialize Framework. I do have Invisible Facebook / Twitter plugin with the Social framework and the Revmob and Chartboost Framework. This app was approved 10 days ago with all those plugins and framework, I add the Flurry framework a got he 'invalid Binary...' So far i have remove Flurry and Scringo with no success. Still a mystery to me. Best regards Gilles

Scringo should be OK to use, it might be flurry that's doing it. To fix: Download NEW SOURCE code. Just fix the app the way you like it and do not add flurry. Continue to use socialize, that is OK. Now submit, see if it gets to "waiting for review". If it does, REJECT BINARY, and then add flurry, and re-submit. If you get the same email error back, you know it's flurry. You then have 3 options: 1: don't use flurry. 2: find out if there is a newer version of flurry framework. 3: contact flurry support and tell them about the issue. Keep me updated! Cheers, David

Hi David, Thanks you for your help, I did remove Flurry with no result. I thinks my problem is the source code. I have download the SOURCE code from Buzztouch on April 3rd, I spend many hour to modify it, if I download again, the new files will erase all my work, which mean I will have to download NEW SOURCE code and redo my work. "Did you MODIFY the BuzzTouch source code regarding the UDID after April 3rd 2013 ??" Best regards. Gilles

Yes gilles, if you keep old project transferring custom changes should not take too long, this is the only way I know to step by step find out which SDK is causing the problem (by process of elimination). :( David

I had the same problem. I ended up updating all my sdks (socialize, chartboost, revmob, flurry) and the problem resolved. Regarding previous comments about process of elimination, that logic is faulty. In my case there were several sdks that contained the taboo UDID code. I swapped them out one at a time, and resubmitted each time, and until I replaced the last guilty sdk, the problem was present. But that does not mean that all but the last sdk were innocent. And it is really "interesting" to see companies like chartboost literally wait until the day the requirement is imposed before they release their fix, and then on top of that they had bugs on their backend that prevented things from going smoothly. (That last sentence out of context could be really sketchy.)

definitely the SDK´s! For me it was Revmob. Revmob Release note: 5.4.0 (2013/04/05) UDID are not collected anymore

@jason, regarding process of elimination, I had only 3 SDK's and I knew one of them was not the issue, so I guess that was the case for me. But you're right, definitely is the SDK's, and definitely if you have several SDK's process of elimination would not work if more then one is not up-to-date. Sorry - did not think of that. It was my socialize SDK. I had updated it to the latest version and it STILL told me the UDID was accesses - turns out the project was still referencing the old SDK. After I fixed that it went through flawlessly. This is a wakeup call to me to make sure I keep these damn sdk's up-to-date! @LeonG revmob was referenced several times in google for UDID yup :) Cheers, David https://buzztouchmods.com

Hi David, Definitely the SDK´s! For me to, it was an old Revmob SDK. I did up update all my sdks (chartboost, revmob, flurry) Alway keep your SDK "fresh" !! Best regards. Gilles

@MRDavid "It was my socialize SDK. I had updated it to the latest version and it STILL told me the UDID was accesses - turns out the project was still referencing the old SDK. After I fixed that it went through flawlessly." how do you remove the old reference? I've moved to trash the old sdk and put in the new one... what else is there to do?

Uelsimon, just re-download a clean project where there are absolutely no references at all - much easier than digging through tons of settings/code in xcode trying to remove old references. Cheers, David https://buzztouchmods.com

sigh.... i was hoping that wasn't the answer. will have to implement some other sdks too if i go that route. ok thanks