It's the nature of certificates. You can have a certificate last a long time
but you cannot create a non-expiring cert to my knowledge. Also, keep in mind
that as time progresses, encryption algorithms become dated. Malware forces the
modification and sometimes the abandoning of what seemed once
On 30 Apr 2018, at 4:07, Mark Smith via use-livecode wrote:
Hi Bill, reading your message I thought for a second it was something
I had
written myself. You stole the words out of my mouth. Always
challenging,
never seems repeatable the same way twice.
May I second this? Getting things set up
Mark,
I think we can complain about Apple, but they are going to do what they want.
My hope is to make it more clear where we get hung up so hopefully they
(whoever writes the docs) can write them in a way that answers the questions we
face. I think it’s a big challenge, but it’s the world we l
Hi Bill, reading your message I thought for a second it was something I had
written myself. You stole the words out of my mouth. Always challenging,
never seems repeatable the same way twice. Eventually i figure it out but
there are so many steps (and missteps) that I never feel like i have
critica
Randy
Thaks for that info. You are correct that I load them from the ide. I notice
that with lc9 I can load directly from the Developer menu. Nice. Maybe I didn’t
notice it for older versions.
I’ll get that into my notes.
Bill
William Prothero
http://ed.earthednet.org
> On Apr 29, 2018, at
Bill,
Sounds like you’re loading your apps to your iPhone and iPad via the Xcode
Devices and Simulators window… apps loaded in that way will cease to work when
your provisioning profile expires. As far as I know (and have experienced),
that is the “normal” way it works.
However, those same app
I write a couple of apps for myself, that run on Apple iPhone and iPad. I have
to buy certificates from the Apple Developer site. They stop working after a
year. However, some of the apps I get on the Apple store haven’t been updated
for more than a year, yet they still work. I wonder if it has
Sorry Mark, I’ve just switched countries and I haven’t got all the info to
hand, but I think the length of validation depends on the certifcate(s) one
buys - you can get them for different lengths of time. From memory, mine are
three-year certificates, but you can get shorter and longer ones.
H
graham, do your apps expire and need resigning after a year?
--
Sent from:
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, uns
In response to messages on both lists, this is an explanation of the way I’ve
successfully code-signed apps for Mac using the simplest possible methods. I’m
talking about desktop apps made in LC to run on Mac OSX - I am currently using
LC9.0. This seems to work for me (of course YMMV). There are
10 matches
Mail list logo
