Your app contains non-public API usage ?? (Validation Fails)

Why is Apple now failing to validate Unity builds?
I built and published the same app Using Unity4.5.4 a couple weeks ago with no issues.

Now after making some code changes, nothing else was change and i'm not using any plugins.
I built the new app version with Unity4.5.5 then build with xCode 6.1 and run Validation on the Archive.
I get the errors below:


NOTE: I'm on OSX 10.10

 

I'm getting the same issue:

http://forum.unity3d.com/threads/su...oaddidfinishnotification.267261/#post-1817265

 

Me too.

Who can help us ?

 

Exactly the same here .. damn !

 

Thanks, downgrading to 6.0.1 worked. Hopefully this gets resolved soon. It would be nice to have a dedicated "is it safe to upgrade" page for these kinds of issues.

 

Downgrading to xCode6.0.1 works, thanks for the workaround.
I don't understand apple and all there artificial limitations, like this one and Mono being forced into AOT ect ect... its ridiculous if you ask me.

 

mono scripts being AOT compiled is a security thing - Apple does not want any script/s downloaded to the device from the internets to be executable and it is right thing to require

this one is because latest Xcode has a bug and sometimes similar issue pops up because between you as a developer and Apple there is another third party so to speak - Unity

 

What difference would that make when I can just download a compiled native lib instead and invoke the native methods? Also this would be irreverent if the app was sandboxed with app permissions like WP8, Android, BB10 ect...
So I disagree as I think they are trying to force people into using battery saving code... which is a artificial limitation. But if i'm wrong, i'd like to know how?

Also on top of the native lib invoke method I could just embed a language script engine that executes code downloaded from a text file. Sandboxing is the only real way to protect a system.

 

you can't

every app on iOS *is* sandboxed

you can't; any app using runtime code generation and invocation wouldn't pass automatic screening / review process


Edit: for the sake of being quasi correct on the internet:

it is very likely possible to obfuscate syscall/s and private API/s calls to hide them and pass the review despite having e.g. downloading and executing / interpreting code at runtime

it was not the original question though - downloading and invoking external code is not *straightforwardly* possible and is in fact prohibited and restricted by the system and the review process

But I think it's better to point out that no sandboxing and security measures can assure any platform to be 100% secure, rather than pretending it is.

 

I confirm, the Downgrading to xCode6.0.1 works !

Thank you.

 

Does the "Unity3D Patch 4.5.5p2" fix this issue?
If not, is there a patch expected to fix this issue? Or is this more on apples end?

 

I had the same error, I submitted again and it succeeded. Had to resubmit a few days later, same error... submitted again, and again it succeeded on the second submission. no idea why.

 

Is this issue fixed yet? I now need to use XCode 6.1.

 

Yes, this is ok now with the last version of XCode.