• 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.pli

    Heres 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


  • Oh well, I completely overlooked that notice. My bad. After deleting the Favorites.plist it launches fine.


  • Oh well, I completely overlooked that notice. My bad. After deleting the Favorites.plist it launches fine.

    ๐Ÿ™‚
    not a problem


  • 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?


  • 5.0i (5.0.0.0.8)

    • fixed a bug with browser selection changing

  • Thank you! That fixed the problem.


  • 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.

    1. 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.
    2. 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.


  • 5.0j (5.0.0.0.9)

    • Chrome/Chromium profile icons
    • fixed browser selection jumping on Removal tab
    • updated font in About panel

    • There's some inconsistency in behavior of the Remove option in Cookies and Databases tabs.

    thanks, i'll fix this. this should now be fixed in 5.0k


  • 5.0k (5.0.0.0.10)

    • made remove button consistent accross all tabs
    • fixed display of nonfav cookies/datbases not on disk (when sub-domain favoriting is enabled)

  • Hi All,

    I installed version 5 only recently, but it's been working fine with me.
    I had a quick question though: I saw that the Purchase Cookie command leads to the possibility of purchasing the app on the App Store (v4) or the website.
    If I go to the Website, it offers to purchase a license without specifying which version.
    Will it generate a license that's compatible with v5 or will it be v4-only?
    Maybe it should be specified somewhere on the WebStoreโ€ฆ

    Corentin


  • I have almost finished adding all the features into Cookie5(through the beta test I realised I needed to add a couple extra things before launch), and will release shortly after. The license generated on my store is only for Cookie4, but ill be giving free upgrades to recent purchasers of Cookie4 to Cookie5.


  • I have almost finished adding all the features into Cookie5(through the beta test I realised I needed to add a couple extra things before launch), and will release shortly after. The license generated on my store is only for Cookie4, but ill be giving free upgrades to recent purchasers of Cookie4 to Cookie5.

    Very good to know! I'll get a V4 license for now then ๐Ÿ™‚

    Corentin


  • Hey guys,

    heres a new beta:
    Cookie v5.0l (5.0.0.0.10)
    Its quite a big update, with many changes:

    • NEW default option grouping all Favorites into one tab. (Cookie4 style layout still available in Preferences as option "Display Favorites on Separate tabs", also Toolbar can be customised exactly to your liking)
    • changed wording of Browser Extensions Preference to make it more clear what it does
    • disabled Remove button when selecting Browser Extensions and "Never remove Browser Extensions" is selected in Preferences
    • reshuffled Preferences, added a warning onto Advanced tab
    • added an option to remove all Sandbox permissions on Advanced Preferences Tab
    • updated Copyright
    • ui tweaks
    • code optimisations
    • UI responsiveness improvements for certain situations
    • added support for Cookie4 file import! with the following *restrictions:
    • *no support for Browser specific favs (all Browser favs are grouped and applied to all Browsers)
    • *no support for import of Browser Extension favorites

    please let me know if you find any bugs, Any new features will be added into Cookie v5.1!
    Im just looking at making sure its stable now.
    ๐Ÿ™‚


  • One minor thing: With "Text Only" toolbar style used, there's no highlighting of the current tab. With "Icon and Text" & "Icon Only" the icon (of the current tab) would be highlighted in blue, but the text is always black. Is it possible to do something about it?


  • One minor thing: With "Text Only" toolbar style used, there's no highlighting of the current tab. With "Icon and Text" & "Icon Only" the icon (of the current tab) would be highlighted in blue, but the text is always black. Is it possible to do something about it?

    Im not sure?
    Ill look into this


  • Also, I'm not sure how is the "Display Favorites on Separate tabs" option supposed to work exactly. When I unselect it, I get only 2 tabs: Removal, Websites; while when selected there are: Removal, Cookies, Databases, Flash, Silverlight. As I understand it, it groups basically everything together, not just favorites, hence the "Display Favorites on Separate tabs" wording seems a little bit confusing and perhaps it should be changed to "Display Entries on Separate tabs" or so.
    Perhaps the whole Favorites section in the General Preferences should be changed this way - as I understand it, it doesn't affect favorites only, but everything (at least I consider as favorites only those entries that are specifically checked as favorites)

    Another one: when the "Display Favorites on Separate tabs" option is not selected, the tracking cookie counts (the 2nd number between parentheses - shown only if there are such cookies found) is shown in red color. But when that option is selected (so the display of all entries is grouped together) there's no red highlighting anymore - it's all in black.
    EDIT: Now I somehow managed to get the opposite - when the display is grouped the number is highlighted in red, when all types of entries are displayed separately it's black. Then when I check (as favorite) some entry that contains tracking cookie, it changes from black to red (e.g. only those that are checked as favorites use red highlighting in the separate view).

    EDIT2: Two more issues:

    1. I had the feeling that when I launched the 5.0l beta for the 1st time, the actual display mode was "separate" but in the preferences window it did show the opposite ("Display Favorites on Separate tabs" unchecked). Thus to change the display mode I had to check that option first (which did nothing) and then uncheck it again. After that it did behave correctly - it reflected the selected option in preferences. I tried to reproduce this by deleting the cookie prefs (rm -f ~/Library/Containers/com.sweetpproductions.Cookie5/Data/Library/Preferences/com.sweetpproductions.Cookie5.plist) and was successful with reproducing it then. I compared the plist files for various scenarios and normally it seems that in the "separate" display mode the "TB Item Identifiers" and "availableTabs" properties list all 5 tabs to be displayed ("TB Item Identifiers" contains few more entries) and also "separateTabs" property is set to true.
      In "grouped" display mode the "TB Item Identifiers" and "availableTabs" properties list only those 2 tabs to be displayed and "separateTabs" property is absent.

    After the very 1st launch (like with com.sweetpproductions.Cookie5.plist deleted) the "TB Item Identifiers" and "availableTabs" properties list all 5 tabs like in "separate" mode, but at the same time the "separateTabs" property is absent like in "grouped" mode.

    To me it seems that managing the display mode via 3 properties ("TB Item Identifiers", "availableTabs", "separateTabs") is unnecessarily complicated (especially when first two of these properties contain almost the same data).

    1. The "Removal" tab is the only one that's always shown regardless of whether the display mode is "separate" or "grouped". Thus when I'm at the "Removal" tab, open preferences and change the display mode, the view should stay at that "Removal" tab. Now the view switches elsewhere ("Cookies" or "Websites" depending on the selected mode) which is a little bit annoying. I understand that something like this is inevitable for other tabs, but with "Removal" this shouldn't happen.