According to the Unity docs (they use Mono, too) http://forum.unity3d.com/threads/54355-_NSGetEnviron-App-Rejected-Version-3-0
"_NSGetEnviron is used by the Mono runtime to provide an implementation of the .NET core API method: Environment.GetEnvironmentVariable()." "In order for us to solve this problem we simply removed any calls to _NSGetEnviron and exc_server. Update Unity iPhone 1.5.1 was sent out to developers days ago. Most of them have already resubmitted their Apps to the AppStore with the functions removed. Unity iPhone 1.5.1 will go live this week." --posted November 2009 I would venture a guess that you built your app with something earlier than unity 1.5.1. Is this the case? If so, perhaps you should rebuild with Unity 1.7 and resubmit. ---------- which version of Xamarin.iOS are you using, 'cos that post is nearly 3 years old? I assume you are calling Environment.GetEnvironmentVariable somewhere? MAybe it's been fixed in a newer version of Xam.iOS? Sebastien (or Rolf) is the right person to fix it tho, as far as I know. N On 2 May 2013 11:15, Kosta Mihajlov <[email protected]> wrote: > Except for the native bindings, the only external library we are using it > Newtonsoft.json(portable) > Our shared code is in a form of a portable libraries. is there a chance for > Newtonsoft.json to be the problematic one? > Thanks, > Costa > > Thanks, > Costa > > On May 1, 2013, at 2:03 PM, Sebastien Pouliot <[email protected]> wrote: > > On Wed, May 1, 2013 at 5:24 AM, Kosta Mihajlov <[email protected]> wrote: >> >> >> Hi All, >> We have an issue with publishing our IOS app/s on the store >> we are using the Application Builder to submit the ipa/s. >> the result returned is : >> The App references non-public symbols in >> Payload/MediawirePrintStandMobilePresentationMonoTouch.app/PrintStand: >> _NDGetEnviron > > This is not a symbol that comes from Xamarin.iOS. It likley comes from a > static library you're linking your application against. > >> >> I made a few searches and it seemed to me that if i set the solution to >> Link SDK Assemblies(currently we don't link anything) it will work: > > > Link SDK is the default and there are several reasons for this. I'll give > you a link to my Evolve talk as soon as it's published. > >> >> This popped up another bug: >> 2. Due to the fact that we are using: >> --compiler:clang++ additional arguments >> the build fails when Link SDK Assemblies only or Link All >> assemblies is set. > > That's surprising. Managed linking happens before native compilation. Can > you file a bug report[1] with the details ? including the version of > Xamarin.iOS you're using and the exact error you get while building. > > Sebastien > > [1] http://bugzilla.xamarin.com >> >> 1. If we you have solution how to fix #1 without using linking .we can >> wait for item no #2. >> >> Thanks, >> Costa >> >> >> >> _______________________________________________ >> MonoTouch mailing list >> [email protected] >> http://lists.ximian.com/mailman/listinfo/monotouch >> > > > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > -- Nic Wise t. +44 7788 592 806 | @fastchicken b. http://www.fastchicken.co.nz/ _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
