Safari losing cookies, forgetting logins

I was having the same problem, which was getting really annoying. What I did was to run Keychain First-Aid, delete Growl and delete my 1 webclip from the dashboard. So far things are working perfectly *keeping fingers crossed*. I think the culprit was probably the webclips on the dashboard, but I did all three just in case because I don't like Growl much as of late.

Me too
Frustating
I begun using Firefox for site that you need logins for.

Hello Cupertino, is there anyone out there?

Definitely not a web clipping problem on my end. I do not use web clippings at all and have had this problem since "upgrading" to 10.5.6 on 3 macs (iMac, MacBook Pro, and MacPro).

So Apple is declaring they are unaware of the problem even though it is all over forums. So why would anyone consider buying Apple Care if Apple does not care? I am SO glad I never wasted money on Apple Care since it appears they will not fix anything anyways until the next OS update in 2-3 months. Time for Firefox I suppose. Oh well, at least it will work.

Look, we're all frustrated about this, but you need to do your part too. Report the problem, submit a bug report. Apple does not have the resources to have someone scour over all these message boards looking for issues. And even if they did find a problem, unless the poster put step by step instructions to repeat the issue, or a complete set of his logs, there's no way the support people could even begin fixing it. If you want this problem fixed, then report a bug. Apple will tell you what information they need from your computer to analyze it and it will help them figure this out.

The engineers are NOT sitting on their butts and they are not totally devoting themselves to Snow Leopard and letting everything else slide. They are working to resolve Leopard problems AND get Snow Leopard ready to go. But all of this does take resources and time. Things have to be analyzed to figure out what the problem is. Then once that's done, they have to figure out how to fix it. Then they have to test and test and test to make sure it works, doesn't break anything else, AND doesn't destroy any of your precious data. And there's only about a billion combinations of hardware and software they have to consider, so they do the best they can as fast as they can. If you think you can do a better job, then get a job at Apple as a programmer and show them how brilliant you are by fixing everything in a day.

And if you want to be dumb enough to not "waste money" on Apple Care, I'd say you must be the type of person to cut off your nose to spite your face.

Stop complaining and being part of the problem. Either help by reporting the issue and working with them to resolve it, use your brilliant skills to fix it yourself and post it for all the world to see, or shut up and wait for it to be fixed.

Geez, the gimme gimme gimme attitude of people these days drives me nuts!

Absolutely the same problem here.
Passwords are remebred, but Safari since update to 3.2.1 seems to randomly forget cookies.
I have to login to verious forums and pages several times a day.

Removed webclips from Dashboard - no improvement 😟

Br,
Pawel.

Same problem here, but not on all my Macs! Still they all run the same version of Safari and OSX (10.5.6)

I am pretty sure that the problem regarding loosing "Safaris" ability to autofill in login information is produced by Apples security frameworks. "Mac OS X 10.5" introduced "code signing", which prevents altered applications from e.g. saving/reading existing keychain entries. If you use browser plug-ins the OS's security bells may ring - and you face some strange symptoms.

From Apple Developer Information: +"Code signing is a technology introduced in Mac OS X v10.5 that ensures the integrity of code and allows the system to recognize updated versions of code as the same program as the original. Once you have signed your code, any change in the code that you did not intend—whether introduced accidently or by hackers—can be detected by the system. On the other hand, your signature on an updated version of your program tells the system to treat the new version exactly as it treated the old, so that users are not bothered with obscure dialogs asking them to give permission to the keychain or some other system component to interact with your code. ... Signatures do not alter how your code runs and are ignored by Mac OS X versions prior to Mac OS X v10.5; therefore, there is no reason not to sign your code. ... Because the system will expect all code to be signed, any code that is not signed will not behave in the same manner as the majority of the programs on the user’s system. In particular, the user is likely to be bothered with additional dialog boxes and prompts for unsigned code that they don’t see with signed code, and unsigned code might not work as expected with some system components, such as parental controls."+

To prevent the symptoms you are facing you simply have to re-sign "Safaris" code - even after deleting some browser plug-ins like "Saft", "Glims", etc., which is not necessary, if the plug-in itself is working correctly for you. (Personally I am using the plug-in "Glims" without any probs.) Please note that code re-signing might be necessary after plug-in updates again. Please note as well that many web sites host login forms, that prevent e.g. autofill for passwords for security reasons. You can modify Apples framework "WebKit" to ignore such login form preferences by using a nice AppleScript app, which can be found here: http://magicpubs.com/mac/software/autocomplete/

To sign "Safaris" code just follow this Howto and you will for sure be happy again: http://forums.macnn.com/79/developer-center/355720/how-re-sign-apples-applicatio ns-once/

Hope this helps! 🙂

Message was edited by: Ralph Schreiber

As I never had problem with autofill feature - I have no idea what is causing this, my only problem was Safari losing stored cookies.
Today after some testing with other applications I've discovered that all my problems are gone after I disabled Vienna RSS reader. Although I think this is not purely Vienna's problem - according to other users feedback I think problem is in Safari cookie interface - if other applications use it - cookies simple disappear from time to time.

Br,Pawel.

Message was edited by: Pawel Guraj

It's not due to that RSS reader as I've never even heard of it and I have the problem.

This has to be something to do with 10.5.6 because that is the only thing all of us have in common. I've had to switch to Firefox which pains me, but at least I can use the web again.

Of course it is not directly related to that's RSS reader, but certainly it is some dependency.
This reader uses cookies, and has web browsing interface that is common with Safari.
This all started with upgrade to 10.5.6 and 3.2.1.
My hint is that some kind of interface changed causing other applications to mess up cookie store.
Maybe some Apple developers are reading this - and it might be some hit to finding the problem.

One thing I'm sure - with Vienna disabled - everything is as before upgrades. As soon as I have it
launched Safari starts to loose Cookies.
It might be the same with Dahsboard web-clips, Growl etc.

Message was edited by: Pawel Guraj

If you've read any of the previous posts you'd know that people are running into this problem without growl, without webclips, without fluid, without any of these things. Sometimes the problem goes away for a day, and then it comes back.

I do not use growl, do not use fluid, do not use adium, do not use an rss reader, do not use webclips, or anything else that uses Webkit. Still have the problem.

Yes I've read all previous posts, and as You know, there are also reports that after disabling some applications in some cases problem goes away. That is exactly my case.
You probably know that bug-tracking process involves identifying all circumstances in which problem arouses, not simply saying "It's safari problem" - so I've tried to provide more feedback.
Sorry, it seems that I'm overacting.

Br,
Pawel.

Message was edited by: Pawel Guraj

I've contacted Vienna developers.
They are not using Safari directly, but standard WebKit cookie handling functions. They are aware of the problem, which is very random and depends on web usage. This points that bug exists in WebKit framework or even lower.

Br,Pawel.

I've done everything listed above and I still have the problem.
At first Safari was logging me out almost instantly after logging in.
I disabled the 1Password Safari plugin and now it logs me out after a minute or so.
Extremely annoying.

Edit: I upgraded to 10.5.6 but my Safari is still at 3.2 so obviously it isn't a problem with Safari 3.2.1

Message was edited by: Christopher S.