I'm not a programmer by any means so this could be completely ignorant... but is there a way you could just set the file permissions of the cookies you want to keep to root or something so they couldn't be deleted until you were asked for your admin pass?

This is not specific to Intel Macs. I also noticed my cookies all disappearing soon after my Leopard install (on my PowerBook G4), but didn't make the connection to having just filed a bug. However, I wasn't able to reproduce this in a few attempts. Is it possible that it's a concurrency issue?

(An easy way to find out would be to disable multiple cores on the Intel Mac, or to do some testing on a multiprocessor G5.)

I use a Dual G5 as my main production computer and was not able to reproduce the issue.

This post might be relevant.

http://forum.slicehost.com/comments.php?DiscussionID=929&page=1

Rob: That's also bad, but likely unrelated. This is about deleting all cookies, not just one you're trying to set.

Anyway, would it help if I pointed out that the bug is easily reproduced, except when you're running Safari on an Intel Mac under Rosetta? I always thought that by the time you got out of application-specific code--like down to this "CFNetwork" or whatnot--you were outside of Rosetta's purview and were back into native code.

Chris B. - Rosetta is not like the 68K emulator in OS 9 with its Mixed Mode Manager, it's all or nothing. All the code in a process running under Rosetta is being translated.

In Leopard there's another checkbox - "Open in 32 Bit Mode" - that shows up for 64-bit applications. Only Chess and Xcode (as far as I could tell) of the applications bundled with OS X come in 64-bit versions, and Xcode is set to run in 32-bit mode by default.

I've seen the same problem since I installed Leopard, except (a) I'm on a G5 and (b) I've never filed a bug with Apple. All my cookies seem to disappear every day or two -- I've logged into nytimes.com more times in the past week than in the previous two years. Here's hoping for 10.5.1!

So good of you to immediately assume bad intent and write an inflammatory headline before finding out the actual code that causes the bug. Very responsible.

Never assume that the coders are fallible humans; always assume malice.

Thanks for my morning dose of uncertainty and doubt. (You left out fear. Maybe you should put in a line about how your whole home folder could be deleted. That would complete the whole jumping-to-conclusions theme that FUD is known for.)

It's okay, Tedious. Shh. Macs just work(TM). There are no bugs in OS X. You can go back to bed now.

I get the same thing, my solution was to chflags uchg it for a while and then just start using Firefox for the bug reporter instead.

It only happened on one of my ADC accounts, though.
(radr://5563653)

another one of my comments got deleted.

Banning my IP from posting here will not do ANYTHING to stop me from posting comments.

UNSANITY, YOU ARE A BUNCH COWARDS

Just go and fix your own fucking software, so PAYING CUSTOMERS, can start using it again.

All i see here is alot of shit talking about Apple, but i don't see your little compatibility page updating....

To: hater

Looks like you really memorized that old book, "How to make friends and influence people." WTG!

Not.

@Daniel

No, but i learned 1 thing: If you pay for things, they need to work.

This is a second time we have to hear lame excuses and wait for weeks for an updated "product"

@Hater
If you are an Unsanity product owner than you have probably looked into OSX's system files and on Leopard you can pretty quickly realize that they have made HUGE changes to the very things that Unsanity relies on for its products to work. Compound on that the obvious-ness that Leopard in its current state is in a transitional phase- pushed out the door to meet a release date as the GUI is in the midst of a completely new presentation method and still using a minor amount of the previous data used to do so. Judging from Unsanity's past you arent gonna get left out to pasture and maybe they are just holding off on wasting time until Apple gets caught up to their own schedule.

@hater,
Just how many Unsanity apps have you licensed? I have licensed ALL of them—twice over. You don't see me incessantly whining albeit I miss ALL of them.

We should get a pool together and pay you for your haxies so you will simply get lost. And I do mean indefinitely lost.

@hater,

You paid for a product, and it works. It just doesn't work the way you want it to work: namely under Leopard. But Unsanity didn't sell you something that works under Leopard, they sold you something that works under Tiger. If you can't understand that major OS releases mean major overhauls for mess-with-the-deep-OS-guts software like what Unsanity sells, then that's your problem. You should have taken the time to find out if the programs you're using are certified for Leopard before upgrading. In any case, quit making your problem our problem as well by whinging about it here.

This bug is to do with user permissions on the files, some accounts upgraded from tiger are setting wrong permissions on files, which cause finder to crash if you try to edit them in get info, and this cookie behaviour in my experience. once group id, and all user owned files have been reset to correct permissions things function normally. I would hope that apple will automatically do this with 10.5.1, as it's a wide spread bug.

This issue I am talking about has nothing to do with permissions whatsoever. Especially since the cookie file is deleted and recreated from scratch every time it is saved. And remember, there's only one cookie file.

does the cookie file have a user (unknown) listed in permissions? if not, then ok, it's not that problem.

macghost, no, why would it? I mean, unless you changed your umask (not very likely) then the new file will be created with the defaults permissions.

Why are people suggesting it's related to permissions? The file is written from and read to just fine. But this bug causes an empty array to be written instead of your cookies.

Rosyna, I had the same problem last week. All of a sudden, just noticed that every one of my cookies were deleted. I noticed too late, though, so I'm not sure which site triggered the problem for me.

I'm not an Apple developer, but I did login to ADC to grab a copy of Xcode (some neat tools in there). That's all I can think of, but I do quite a bit of web browsing each day - so it could be a non-Apple site.

I'm using an Intel iMac, one of the mid-August models. I haven't used my PowerBook G4 much, but I don't think it's happened on there.

Hope someone takes your report seriously - if I didn't store everything in my keychain, I'd be kinda stuck right now. I'm not looking forward to logging into everything again.

Here's the stack trace where it writes out the empty plist:

0 libSystem.B.dylib write$UNIX2003
1 CoreFoundation fileWrite
2 CoreFoundation CFWriteStreamWrite
3 CoreFoundation CFPropertyListWriteToStream
4 CFNetwork CFHTTPCookieStorageSync
5 CFNetwork CFHTTPCookieStorageSyncStorageObserver
6 CFNetwork CFHTTPCookieStorageObserverCallback
7 CoreFoundation CFRunLoopRunSpecific
8 CoreFoundation CFRunLoopRunInMode
9 Foundation +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:]
10 Foundation -[NSThread main]
11 Foundation __NSThread__main__

I'm interested that you have the spare time to fool around tracing these bugs while we users still don't have a Leopard-friendly APE Manager, Fruit Menu, etc. Maybe you need to run a reality check on your priorities.

Or perhaps filing bugs in Mac OS X is directly and strongly correlated with writing software on Mac OS X.

I do wish that Unsanity would stop trying to improve the quality of Mac OS X for all users by filing detailed bug reports and would instead get back to working on their own software... if only to shut up their users who seem to have nothing better to do than whinge like children for any reason at all.

Hello!

People, did it ever occur to you that some of these bugs in the operating system are preventing Unsanity from getting their programs to work???

Don't yell at them for finding and reporting bugs in the OS, it's part of getting programs written for a new version of the OS.

Hello!

People, did it ever occur to you that some of these bugs in the operating system are preventing Unsanity from getting their programs to work???

Don't yell at them for finding and reporting bugs in the OS, it's part of getting programs written for a new version of the OS.

I won't express myself as rudely as the other gentleman, but I do agree with him. I am sure that Leopard has very many bugs, and this business of disappearing cookies seems to be one of them. But it is very hard for a layman to imagine how this particular bug might have something to do with the fact that haxies and the/or the APE Manager are broken under Leopard. If there is any possible connection then sure, you're right and I'm wrong, and I'll gladly admit it. If not, as a long-time Haxie purchaser I would like to point out that Unsanity is a business enterprise. Its mission is not, as one contributor put it, to "improve the quality of Mac OS X for all users by filing detailed bug reports," but rather to function as a commercial venture by servicing its customer base and keeping them reasonably happy. If, as I suspect may be the case, its programmer has become interested in one particular Leopard bug and has invested his time in studying it when he could and should have been diagnosing and fixing the current Haxie/APE Manager problem, then, yes, I think he needs to perform a reality check on his priorities since, from the cash customer's point of view, the days keep passing without any end to this problem in sight. If I am wrong about this, then of course I humbly apologize to him.

Would you rather have APE arrive a few hours later or your cookies zapped for good?

Perhaps this was all discovered on a weekend. Note the date and time of this original posting. Do people often devote every waking moment to one task?

Or perhaps this bug was so significant that it prevented any work to be done. Such as this bug, without knowing it's cause, prevented some code from being tested properly due to sites being repeatedly reset to default? Or perhaps in order to write any code, the programmer must first access a site that reads a special cookie in order to get access to the versioning system from a non-main location. As stated, the main production computer is a G5 and this bug cannot be reproduced on a PowerPC mac.

Or perhaps the programmer was doing their due diligence in reporting and tracking down a bug a lot of their developer associates have been hit with?

Personally speaking, I'd rather have APE arrive a few hours (more likely days or even weeks) earlier -- it is the job of Apple programmers to fix that bug, it's the job of Unsanity programmers to get APE up and running so those of us who rely on Haxies in our work can do our own jobs.

I've encountered the same bug. Can you give me the radar-number so I can properly file a dup?

I completely f’ed my box. I’ve got a macbook pro, w/ no native DL DVD-R. My PC, however, has a Dl burner. I moved the .dmg to the PC, and burned it. as .dmg. couldn’t find any PC tools to convert .dmg to .ISO (which is the ultimate goal as I would like a boot-able Leopard Disk.) From the DVD, i restored the dmg to my ***MAIN PARTITION*** ouch!!! :*(

What was I thinking?! I’m not going to get into it. Long story!

How can i recover from restoring Leopard onto my main partition? The Macbook hangs at the apple logo, w/ the status under it in a loop.

Another question, does Apple and their cult like fanboys punish developers who dares to post such embarrassing issues to their blog rather than pimping whatever Apple releases?

I am sure no sane technical user or consumer of Unsanity actually expects/expected Leopard compatible APE right after it was released.

There is no such thing. As far as I see, Unsanity is much more responsible than the company your religion is based on and they never, ever release anything which will cause chaos and unstable user experience.

For that, you should check with some other billion dollar company who spent their 7 months trying to lock iPhone rather than testing their new major version of OS and ensuring minimum backward compatibility.

> it's the job of Unsanity programmers to get APE up and running so those of us who rely on Haxies in our work can do our own jobs.

And it's the job of individual computer users to make sure that the software they require for their jobs runs under a new release of the OS before upgrading to that new release. Just because Apple has shipped 10.5 doesn't mean you must upgrade to it immediately.

If you rely on haxies in your job, you should know NOT to be one of the early adopters of a major OS release. Software inevetibly breaks in such major releases, and you should be prepared to either work around it or live without it till it's fixed. I won't believe you need Leopard to do your work either, as nearly ALL of it's features can be addded to Tiger using 3rd party software.

Rosnya, is there anyway you can post a 'generic' bug report for this issue? That way, if enough people file the bug, it might motivate Apple to get off their arse and fix the problem!

I have experienced EXACTLY the same thing on a C2D Macbook running 10.5 and only just realised that my cookies were being deleted AFTER i was filing bugs!

Less talk, more Shapeshifter.

Would the neglect you've shown ResExcellence count as a bug?

ICBM eated my cookiez.

Much as I enjoy the general Mac OS X debugging posts, it's more fun when you talk about the specific issues you have with making APE and your various haxies work on Mac OS X, seeing as Apple makes it harder and harder to inject code. But thank you for trying to improve everyone's Mac OS X experience.

Less QQ, more pew pew!

Impatient User is impatient.

Keep up the good work Rosnya.

Logitec Control Center 2.4 is out

from changelog:

"Unsanity's Application Enhancer (APE) is no longer installed and needed"

good luck with your software, losers.

Happy Thanksgiving to all!

That's one amazing bug but...I have to agree with some of the other posters here. Could you perhaps post an ETA for at least some of Unsanity's haxies, i.e., an approximate date when they will be available for an open beta? Thanks.

Apple punishes nobody.
It's just an annoying bug you stumbled upon,
a bug that is more relevant to developpers and not to end-users.
Imho not an interesting point to blog about.

Yes, I have reproduced (should read: Apple made my IntelMac reproduce) this error. I thought it had something to do with Safari3 crashing all the time when using the mldonkey html interface, but seems (annoyingly) it does not.

Is this bug specific to Safari only? I use Firefox almost exclusively and have not seen the issue. As far as product update delays go, I'd rather have it later and right than earlier than buggy.

The bug you noted happens on my clean (new drive) Leopard-install G4 pBook, using Safari (no haxies installed, that I can find).
And, yes, please update APEs.

To Haha: I think Logitech switched to a kernel extension to accomplish the thing they do safely with APE.

Good luck to you and all logitech software users in fact.

I will keep buying Logitech for my needs but I won't install their software after they switch to NON SAFE method of doing things.

How would this be for an alternative:
Either . . . a folder action that copies Cookies.plist to some safe folder when it changes, but when the file is changed so that it's below a certain size, it writes the copied, good version to the Cookies folder.
Or heck, a script that copies the cookies file to a safe folder, goes to the bug site so you can report, and then a set time later copies the cookies folder back.

Either could be faster than the Time Machine route.

Just thinkin'.

Plus, I'm hoping that your Leopard compat issues are on the way to being solved. I miss FruitMenu a ton!

The bug I filed on this Oct 1st is still open, Radar #5516729. Just appended a link to this page, in case any one's awake over there. To tell the truth, I haven't really missed Safari that much--Camino's working great..

Thanks for writing about this bug. I upgraded to a new Macbook with Leopard preinstalled... and this bug is driving me nuts!!!

I use the machine at work so I don't have it connected to my RAID box until I get home (so no TimeMachine during the day).

I've resorted to having Stuffit schedule a backup of the cookie file every few hours, that way I can at least revert back to a normal working condition.

I don't care for the other browsers, so Apple really needs to fix this bug.

Thanks again! If you hadn't posted I probably would have lost my mind!

Dudette: get 1Password so you don't ever have to remember a password again -- even without apple's shenanigans cookies Will get corrupted, replaced, overwritten, emptied out -- it's bound to happen sometime. You can even save notes/specifics of your cookies or almost anything including secure notes into 1Password

1Password is a lifesaver and a new must-have for any mac. It works directly integrated with safari and other browsers.

I couldn't do without it ever again. you guys should do some cross promotions!

P.S. forgot:

1Password.com

They have had a perfectly fine earlier version for free going for a while -- don't know how long it will last but this link still seems to be good.
http://agilewebsolutions.com/promo/macgems

and if you sign up at macupdate and click the 2 options to add it to your 'wish' list or whatever it's called and to be notified when it goes on sale, that's a good way to get a great deal to upgrade to the newest version whenever it goes on sale again.

FWIW
happy cheery jingle days

I can tell something after my Leopard installation and endless crashes, issues, amazing things and running software update almost hourly.

Unsanity and their customers should consider themselves LUCKY that old APE created issue on Leopard or simply didn't function.

I have even purchased/used Windows ME in its first release date and to this date, I have never, ever seen such a messy buggy OS along with a cult-like community who would blame EVERYTHING, EVERYONE and YOU but not Apple for these issues.

I can't imagine the bad feedback/press Unsanity would get if something magical happened and Ape 2.0.3 have run on Leopard without problems.

I keep saying "this is a clean install", "machine is checked weekly for issues", "I have these issues while just running mail.app from Apple", those freaks still say "No, you must be doing something wrong! Any third party? Haxies?"

For Unsanity: Your total version tracker download numbers are at some amazing levels, you gotta start IGNORING some no-life, never produced anything successful developers and users.

Care for your customers and nobody else. Merry xmas and happy new year.

IT'S NOT JUST ME!

Man, this cookie thing has been killing me for the past several weeks. It's not just bugreporter that's doing it, because I haven't been there recently. But it's driving me crazy. I lose the file once every few days. Thanks for the tip about it being a per-site issue though, I'll start trying to track it that way and see if I can figure out what site is doing it. I was thinking that maybe multiple webkit instances were trashing the file, or WebHound or some such, but tweaking those didn't seem to make any difference. Have you tried doing a tcpdump while connecting to bugreporter to see if you can figure out the values and perhaps come up with a reproducible case?

As for the folks bitching about the lack of Haxies. Yeah, I miss them too (that's why I came to this blog--to see if there was any news). But I seriously doubt anyone's sitting around at Unsanity and saying "Gee, I don't feel like earning money, so I'm not going to try and get them working again." Come on guys. Keep the comments to things that are relevant.

Still happening in 10.5.2 on my Powermac G5.

This is SO F***ING FRUSTERATING.

Hmm, I report bugs daily on radar and never lose my cookies. Could it be some third party software you have installed? I had so many issues with APE I removed it. Maybe something along those lines?

Try this on a clean system with no third party extensions, or a clean user. Maybe some file is corrupted and its causing this file to get deleted.

Actually, yes I noticed this as well, and switched to Firefox to enter/track my Apple bugs now. However, I think this bug also is triggered by logging onto Apple Developer Connection as well.

The day these were released I installed FM and WS. Immediatly began having repeated Finder and other app crashes when clicking on the Apple menu. I rebuilt permissions, restarted a few times and finally used APE to disable FM. I reported this to Unsanity and offered to send them any log needed. I listed it on VersionTracker and MacUpdate. I see dozens of people agreeing they have problems.

Yet the funny / sad thing is I just got an email from unsanity announcing these betas and claiming "with no reports of significant catastrophy, it's time to roll the betas out to the mailing list." They do live in their own little world...

There are 3 other reports of FM crashing in this blog as well. But dont they read VT and MU feedback?

qb

I've been getting all my cookies deleted on Safari whenever I quit the browser for the last few days. It's been happening ever since I updated Safari. I'm not sure whether I updated anything else at the time -possibly QuickTime?

I'm running 10.4.11 on an intel iMac 5.1.

I sure hope Apple addresses this problem soon, as I am tired of keeping a list of passwords handy to redo every single time I open the browser.

I also use Firefox and the cookies on THAT browser are not being deleted.

I'm in the exact same scenario as Marian but it's my 266 Mac Pro WS with 10.4.11. Firefox is ok for me too. I can't remember my recent updates but there was one from Apple... can't remember the specifics.

Oh, yeah-- I never ever filed a bug with Apple.

WTF! My cookies are all working now. They were cleared out but once I log-in now they're retained. Freaky--I didn't do anything to remedy.

So THIS is how Mac users spend their time computing? Sheesh.