If you delete a certificate, the server will simply offer you another. No big deal. You only get a conflict when you get a certificate that is current and does not match the one you already have.
Bob On Jan 31, 2014, at 14:32 , Dave Kilroy <[email protected]> wrote: > Keychain files are kept in 'dave/Library/Keychains/' (substituting 'dave' for > 'alain' of course) so you could have a look in there and experiment with > creating new keychains from Keychain Access and seeing how they behave. > > But before you do that you could try 'Keychain First Aid' in the 'File' menu > which gives options to 'verify' and/or 'repair'. I think I tried this but it > didn't help but maybe you will have more luck... > > The other thing is to check that 'Hide expired certificates' is not checked > in the 'View' menu - actually thinking about it, this was probably my > problem a year ago and I should have fixed it in 5 minutes :) > > And I certainly did make copies of keychains before I messed with them! > > Be careful with certificates, spend some time exploring Keychain Access and > don't do anything without making sure you can reverse out of trouble. > > > > > ----- > "Some are born coders, some achieve coding, and some have coding thrust upon > them." - William Shakespeare & Hugh Senior > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/iOS-codesigning-tp4675372p4675382.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
