iOS standalone - what to do about code signing failures?

[Scott Rossi]

FWIW, one tool that *might* help with app signing (haven't read all the
details of your situation) is AppResigner:
http://www.gorbster.net/blog/archives/273


In my situation with recent OS and LiveCode updates, I haven't been able
copy over development versions of apps onto devices without getting a code
signing error.  Using the tool is an extra step but allows me to get the
builds transferred properly (not needed for app store distributions).
Instructions are on the page.

Thanks to Ken Ray for the recommendation.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design




On 1/7/13 2:44 PM, "Graham Samuel" <livfoss at mac.com> wrote:

>Don't worry, I wasn't really offended! There's always something new to
>learn. It's a pity that Apple makes it tougher than it needs to be, but
>with the generous help of this list things are (very) gradually becoming
>clearer.
>
>Graham
>
>On 7 Jan 2013, at 19:34, Robert Sneidar wrote:
>
>> Sorry, I didn't mean to marginalize what you do. I really meant that
>>these days security has become an essential part of software
>>development, especially for mobile platforms. The answer for this is
>>security certificates.
>> 
>> Bob
>> 
>> 
>> On Jan 7, 2013, at 2:32 AM, Graham Samuel wrote:
>> 
>>> 2. When you say "now that you are a developer", I bridled a bit, since
>>>I've been a developer for years.
>> 
>
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode
>