Cookie 5 beta
-
Also not sure about the other browsers, it's very interesting nobody else seems to have this problem. Firefox is a standard release version, Opera is very old (V 12.16), but I do care more about Firefox.
could you try this version, it has some debugging logging enabled:
Cookie5.0gbmaybe it will give me some hints as to whats going on.
all you need to do is open it up, click on the Cookies tab, and select Firefox, then Opera. Then if you could open up Applications/Utilities/Console.app and do a search for Cookie then email me the output. (you can omit the cookies if the log output shows them..... which judging by your situation, it most likely won't anyway).
[/quote]The pasted console-content is on its way via the e-mail-form on your forum user-profile…
-
The pasted console-content is on its way via the e-mail-form on your forum user-profile…
cool, got it.
could you please try the same with this version:
Cookie5gbIt seems that there may be an error reading sqlite files on your computer?
Log is on its way, so Cookie doesn't seem to have the necessary permissions, do you need any additional information I can provide?
-
Log is on its way, so Cookie doesn't seem to have the necessary permissions, do you need any additional information I can provide?
Got it thanks.
Permissions seem ok, but I use a third-party library for reading SQLite files and it seems to fail on your computer?
Ill take a look at rewriting my SQLite code today, and send another build maybe tonight.
thanks for your help.
I'll send you a license to your email address now. -
Log is on its way, so Cookie doesn't seem to have the necessary permissions, do you need any additional information I can provide?
Can you try this version, Ive replaced the SQLite framework:
Cookie5.0gc (alpha)you don't need to check Console.app, al you need to do is see if Firefox/Opera cookies are shown on Cookie "Cookies" tab.
thanks in advance!
-
Hi. Upgraded from 5.0b to Cookie 5.0g via auto update and it doesn't seem it removes cookies anymore. On settings a label reads that the trial expired. I can change settings, but "Removal Options" are grayed out. Also "Remove Non-Favourites" and "Remove Tracking Cookies" are grayed out as well.
Cookies 5 doesn't take my Cookies 4 license.
Thanks.
-
Same here, Cookie 5.0 does not remove any cookies anymore. I assume it is because my trial period expired. It also took my quite a while to find out that the trial period was expired, it is only displayed in the settings of the main windows at not at the preference window in the license tab where I would expect it.
I also think it is confusing to have settings and preferences. Either put all setting to the main window or move them all to the preference window. I would prefer the latter because settings do not fit into the scheme of the tab bar that contains various website storage methods: Cookies, Databases, Flash, Silverlight. "Settings" is not just another storage method. Additionally, one usually does not change these options very often.
Also, Cookie always preselects Firefox in the Cookies/Databases/... tab (but not in Settings tab) even though I have it deactivated and use Safari (have only the two browsers). Can Cookie please select the first activated Browser when clicking on one of the storage method tabs of the main window?
Even worse, whenever I check or uncheck a cookie for Safari, the application instantly jumps to Firefox and asks "Would you like to give Cookies access to Firefox Cookie data?". Super annoying.
The Cookie icon in the global menubar is still hanging some pixels too low compared to other icons which looks odd especially compared to other circle icons.
-
Hi. Upgraded from 5.0b to Cookie 5.0g via auto update and it doesn't seem it removes cookies anymore. On settings a label reads that the trial expired. I can change settings, but "Removal Options" are grayed out. Also "Remove Non-Favourites" and "Remove Tracking Cookies" are grayed out as well.
Cookies 5 doesn't take my Cookies 4 license.
Thanks.
Have the same problem as Klaus. v. 5 expired. I mailed you about it, Russel.
And thanks again for one of my favourite utilities.
-
A quick update.
I have fixed all the known bugs. And are currently implementing cookie4 style favourites. This will be the default, with the current cookie5 style favourites enabled in advanced prefs. The reason for the change is that I think cookie4 style favourites are maybe easier to grasp for new cookie users. I have this implemented and working well for cookies, I just need to roll the changes over to databases/flash and silverlight before I release the next beta. -
and here it is
v5.0h (5.0.0.0.7)
You will need to delete your favourites file after installing beta 5.0h, as Cookie will most likely crash when it attempts to relaunch
the favourites file is located here:
~/Library/Containers/com.sweetpproductions.Cookie5/Data/Library/Application Support/Cookie5/Favorites.pliHeres whats changed:
- New default option to use Cookie4 style favorites (Cookie5 style Favs can be re-enabled in Advanced Preferences using the "Enable sub-domain Favoriting")
- New toolbar icons
- New licensing window
- Moved "Run Setup" and "Reset All Warnings buttons to Preferences window
- Changed Preferences reorganised
- fixed Safari Timer setting
- fixed Silverlight display
- fixed an issue with Opera favorites
- fixed Chrome/Chromium/Opera cookie contents now correctly displayed as being encrypted
- improved code optimisation
-
Hello, beta 5.0h crashes for me right upon launch (the GUI doesn't even appear):
Dec 23 15:04:09 Petrs-MacBook-Air Cookie[30067]: An uncaught exception was raised Dec 23 15:04:09 Petrs-MacBook-Air Cookie[30067]: *** -[NSDictionary initWithDictionary:copyItems:]: dictionary argument is not an NSDictionary Dec 23 15:04:09 Petrs-MacBook-Air Cookie[30067]: ( 0 CoreFoundation 0x00007fff8ccf6ae2 __exceptionPreprocess + 178 1 libobjc.A.dylib 0x00007fff915d173c objc_exception_throw + 48 2 CoreFoundation 0x00007fff8cc08d18 -[NSDictionary initWithDictionary:copyItems:] + 904 3 Cookie 0x000000010c32d358 Cookie + 140120 4 Cookie 0x000000010c32bb59 Cookie + 133977 5 libobjc.A.dylib 0x00007fff915c7390 _class_initialize + 706 6 libobjc.A.dylib 0x00007fff915c6c90 lookUpImpOrForward + 183 7 libobjc.A.dylib 0x00007fff915c0591 objc_msgSend + 209 8 AppKit 0x00007fff868ba1bd -[NSCustomObject nibInstantiate] + 91 9 AppKit 0x00007fff8686d5a7 -[NSIBObjectData instantiateObject:] + 309 10 AppKit 0x00007fff8686cbe8 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 428 11 AppKit 0x00007fff8684bb51 loadNib + 384 12 AppKit 0x00007fff8684b077 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300 13 AppKit 0x00007fff8684ae40 -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201 14 AppKit 0x00007fff8684ac0c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344 15 AppKit 0x00007fff8684525a NSApplicationMain + 466 16 libdyld.dylib 0x00007fff91df35ad start + 1 ) Dec 23 15:04:09 Petrs-MacBook-Air Cookie[30067]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSDictionary initWithDictionary:copyItems:]: dictionary argument is not an NSDictionary' *** First throw call stack: ( 0 CoreFoundation 0x00007fff8ccf6ae2 __exceptionPreprocess + 178 1 libobjc.A.dylib 0x00007fff915d173c objc_exception_throw + 48 2 CoreFoundation 0x00007fff8cc08d18 -[NSDictionary initWithDictionary:copyItems:] + 904 3 Cookie 0x000000010c32d358 Cookie + 140120 4 Cookie 0x000000010c32bb59 Cookie + 133977 5 libobjc.A.dylib 0x00007fff915c7390 _class_initialize + 706 6 libobjc.A.dylib 0x00007fff915c6c90 lookUpImpOrForward + 183 7 libobjc.A.dylib 0x00007fff915c0591 objc_msgSend + 209 8 AppKit 0x00007fff868ba1bd -[NSCustomObject nibInstantiate] + 91 9 AppKit 0x00007fff8686d5a7 -[NSIBObjectData instantiateObject:] + 309 10 AppKit 0x00007fff8686cbe8 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 428 11 AppKit 0x00007fff8684bb51 loadNib + 384 12 AppKit 0x00007fff8684b077 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300 13 AppKit 0x00007fff8684ae40 -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201 14 AppKit 0x00007fff8684ac0c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344 15 AppKit 0x00007fff8684525a NSApplicationMain + 466 16 libdyld.dylib 0x00007fff91df35ad start + 1 ) Dec 23 15:04:09 Petrs-MacBook-Air com.apple.xpc.launchd[1] (com.sweetpproductions.Cookie5.176352[30067]): Service exited due to signal: Abort trap: 6[/code] After rolling back to the previous beta (5.0g) it launches fine. Running OS X 10.11.3 beta 1 (15D9c)``` -
You will need to delete your favourites file after installing beta 5.0h, as Cookie will most likely crash when it attempts to relaunch
the favourites file is located here:
~/Library/Containers/com.sweetpproductions.Cookie5/Data/Library/Application Support/Cookie5/Favorites.plist -
The issues I mentioned in [url=https://sweetpproductions.com/support/showthread.php?tid=329&pid=961#pid961]my previous post[/url] are unchanged. I made a video that visualizes the problem that Cookie jumps to Firefox instead of staying at the Safari page: https://youtu.be/Dxg0MLy2hsY
My license is still expired, is there any way you could send me a valid Cookie 5 license please?
-
I've done some tests and it looks pretty good now, just some notes regarding user experience:
-
As I've already written previously, some simplified view of of entries with just 1 cookie/database that would directly reveal that single entry might be useful.
-
In the Databases tab, the ability to display various types of entries separately or actually select which ones to display (Browser Extension, Browser Extension Database, Local Storage, IndexedDB, ...) may be useful as well. For example I don't want browser extension related entries to show up there at all for most of the time. Now I can at least treat them as favorites so they can be easily skipped during removal, however they still show up in the list which is unnecessary. The ability to select what exactly I want to show up there would be better.
-
There's some inconsistency in behavior of the Remove option in Cookies and Databases tabs.
- Cookies: check website entry (as favorite) so it's both checked and selected at the same time, press Remove (at the bottom), the entry grays out (which seems like the data was actually removed) but it still shows up there and is still checked, then after unchecking it disappears.
- Databases: check website entry (as favorite) so it's both checked and selected at the same time, press Remove and nothing happens.
The question is whether the Remove option should remove the entry that's both selected and checked (as favorite) at the same time. In any case, the behavior should be identical everywhere.
-
