1.4.4 stopped working on 10.12.4

[the3ye]

as in title, not working after newest MacOS update.

[b0gdanw]

Same for me, using cosyTabs 1.4.4 with mySIMBL 0.5.3 (29) on MacOS 10.12.4

[inket]

2 reasons why it's not working:

• Safari now implements Library Validation (like Xcode): as can be seen in the log, Safari by default didn't allow cosyTabs to be loaded but after unsigning [Safari] with unsign, it was loaded correctly.

• cosyTabs needs updating because Safari changed internally (because even though the plugin was loaded correctly, it didn't affect the tabs)

Expect an update soon!

[inket]

Unsigning Safari 10.1 seems to be a no-go because unsigning causes these issues:

• Safari forgets all installed extensions every time you close it
• Safari will also forget other settings
• Touch ID doesn't work
• and probably more that I haven't noticed.

I will try signing it with a self-created certificate later today and report the results. If that's also a no-go, this might be the death of cosyTabs.

[the3ye]

Thank you Apple! no, not really...
I'll keep my fingers crossed, thanks for the effort and good luck!

[Skogmann]

Many thanks for cosyTabs, the valued extension to Safari, and hopefully to the STP as well. Should my donation lift your spirit to bring cosyTabs back to our 'easy living', do forward a PayPal link. Have a nice weekend, Cheers Beff

[inket]

I tried with a self-created certificate but Safari exhibits the same issues… I don't know what to do.

[inket]

I might have found another lead, so please be patient.

[inket]

Yeah… this is dead. To recap what I've tried:

• Safari signed with Apple's certificate:

  • Library Validation prevents cosyTabs (unsigned) from loading: mapped file has no cdhash (unsigned or signature broken?)
  • Library Validation prevents cosyTabs (signed) from loading: mapping process is a platform binary, but mapped file is not (for reference, it says 'cosyTabs' (Team ID: XXXXXXXX, platform: no) for process 'Safari(pid)' (Team ID: none, platform: yes)

• Safari unsigned: cosyTabs loads, Safari works, but it can't read/write any user preferences because the system doesn't allow it to. [because it's lacking Apple's signature/entitlements needed to access data with elevated permissions]

• Safari self-signed: cosyTabs loads, Safari works, but also can't read/write any user preferences^ (console errors about missing entitlements)

• Safari self-signed with the original entitlements: Safari crashes at launch because the kernel rejects the restricted entitlements with a non-Apple signature.

[b0gdanw]

@inket It was fun while it lasted, thank you for all your work.

[the3ye]

why, apple, why?
Thank you @inket for the good days with cosytabs 👍

[the3ye]

With new workaround, patcher made by SafariStrand team seems like CosyTabs is still down, yet other SIMBL plugins work great like SafariStand and WinBuddy. Can it be fixed somehow?

[inket]

@the3ye I didn't know about that patch. It's great that you brought it to my attention.

However, you should know that that's not a permanent solution. The patch just replaces the Safari binary with the one from version 10.0.1 - Once Apple decides to disallow this, nothing is stopping them.

I will look at making cosyTabs work with the current Safari version with this patch. If it's too much work, it might not be worthwhile. 👍

[JayBrown]

Library Validation now also introduced in El Capitan with Safari 11. No cosyTabs, no SafariStand.

[didongke]

Can this problem be solved?

[inket]

@didongke no...