Wow. This gets weirder and weirder. I CAN build apps with XCode, but not
LiveCode.
On Mon, Jul 15, 2013 at 8:05 AM, Mike Kerner wrote:
> Yeah, tried that. I also deleted all my profiles, certs, etc. and
> re-installed them all, too. No luck yet...
>
>
> On Mon, Jul 15, 2013 at 6:42 AM, Dave
Yeah, tried that. I also deleted all my profiles, certs, etc. and
re-installed them all, too. No luck yet...
On Mon, Jul 15, 2013 at 6:42 AM, Dave Kilroy
wrote:
> Mike,
>
> LiveCode's 'Profile' drop-down in the iOS Standalone Settings Dialog Box
> can sometimes display out of date provisioning
Mike,
LiveCode's 'Profile' drop-down in the iOS Standalone Settings Dialog Box can
sometimes display out of date provisioning profiles.
If you haven't yet fixed your problem it may be worth checking that you have
cleared out old Provisioning Profiles and that LiveCode isn't presenting you
wit
It's so weird that my existing apps, the ones that have zero changes to
them, won't go now, either.
On Fri, Jul 12, 2013 at 12:53 PM, Mark Wieder wrote:
> Dar-
>
> Friday, July 12, 2013, 8:23:47 AM, you wrote:
>
> > All day yesterday I read the subject to be about co-designing
> > rather than co
Dar-
Friday, July 12, 2013, 8:23:47 AM, you wrote:
> All day yesterday I read the subject to be about co-designing
> rather than code-signing, a different interesting topic.
LOL. I have the same problem when I read about resigning.
--
-Mark Wieder
mwie...@ahsoftware.net
At times I have had to delete an app before updating it, especially when there
are provisioning changes.
All day yesterday I read the subject to be about co-designing rather than
code-signing, a different interesting topic.
Dar
On Jul 12, 2013, at 9:11 AM, Mike Kerner wrote:
> thanks, Chris
thanks, Chris, but that didn't fix it, either. It's really weird - even
the wildcard certificate doesn't work for a brand-spaking new stack with
nothing else attached to it.
On Fri, Jul 12, 2013 at 10:34 AM, Chris Sheffield wrote:
> Mike,
>
> Try this if you haven't already.
>
> Launch Xcode an
Mike,
Try this if you haven't already.
Launch Xcode and open the Organizer window. Select "Provisioning Profiles" on
the left, then hit the Refresh button on the lower right. This will sort of
sync everything up between Apple's dev portal and your computer. After that's
done, try building your
Is there some known way to debug this? I haven't seen anything on this
list about it. Creating a new app gives the five-point signing error, now,
too, and it seems that all of my apps have lost their link to their
provisioning profiles.
On Thu, Jul 11, 2013 at 6:55 PM, Randy Hengst wrote:
> M
Mike,
The only time that's happened to me is when I didn't change to the correct
profile when I built the standalone in LC. That was the problem even when I
knew I used the right one.
be well,
randy
-
On Jul 11, 2013, at 5:35 PM, Scott Rossi wrote:
> Not sure if this is your issue, but
Not sure if this is your issue, but FWIW, trying to load/transfer a newly
built app to a device always fails on my system unless I use the
AppResigner tool that was mentioned on the list a ways back.
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On 7/11/13 3:22 PM, "Mike
An app that I have been using and deploying to my team for months is now
failing to build with "codesigning failed with aps-environment
development"
I checked the certs in keychain and in xcode and at apple's developer
portal, and nothing seems to be expired or otherwise out of the ordinary.
So an
12 matches
Mail list logo
