Not sure this really works. To get the "dynamic-codesigning" entitlement in the Provisioning Profile -- that has to come from Apple in the Dev Provisioning portal. Your entitlements file settings in your project must match the entitlements set in the Provisioning Profile.
Thus, for this to work (in non-JB phones), the signed PP in the Dev Portal must have this entitlement set -- which is of course all up to Apple. On Thu, Nov 29, 2012 at 11:09 AM, Shazron <shaz...@gmail.com> wrote: > Having trouble with entitlements, don't know what's going on yet: > [image: Inline image 1] > > > On Thu, Nov 29, 2012 at 10:14 AM, Shazron <shaz...@gmail.com> wrote: > >> We should definitely put this in the wiki if testing shows that it works >> -- I'll give it a spin with some benchmarks >> >> >> On Thu, Nov 29, 2012 at 9:19 AM, Dave Johnson >> <dave.c.john...@gmail.com>wrote: >> >>> It would be cool to try an app with and without nitro and see how much >>> of a difference it makes. >>> >>> On Thu, Nov 29, 2012 at 3:02 AM, Brian LeRoux <b...@brian.io> wrote: >>> > Whatcha think, add to the docs or just put a note in the wiki? >>> > >>> > On Thu, Nov 29, 2012 at 10:42 AM, Shazron <shaz...@gmail.com> wrote: >>> >> Awesome -- Apple might disapprove for App Store apps but doesn't mean >>> an >>> >> enterprise developer can't enable it for enterprise distributed apps >>> >> >>> >> >>> >> On Thu, Nov 29, 2012 at 2:32 AM, Brian LeRoux <b...@brian.io> wrote: >>> >> >>> >>> of course just because we can doesn't mean we should >>> >>> >>> >>> >>> >>> >>> http://www.littlereddoor.co.uk/ios/how-to-enable-the-nitro-javascript-engine-in-ios-applications-directly-through-xcode/ >>> >>> >>> >> >> >
