Apple stole my Safari 12 Extensions

[FriedChicken2]

I did a straight restore using CCC from my 2012 iMac to my 2019 iMac. When I booted into my 2019 iMac, everything was the same except my safari extensions (js blocker, µBlock origin, RES) were gone, and cannot be installed again.

WTF apple.

 

[TiggrToo]

I did a straight restore using CCC from my 2012 iMac to my 2019 iMac. When I booted into my 2019 iMac, everything was the same except my safari extensions (js blocker, µBlock origin, RES) were gone, and cannot be installed again.

WTF apple.

You used a third party app to perform a restore and this is somehow Apple's fault?

 

[appltech]

If you're talking about some older macOS version then yeah, could be (when Apple restricted Safari extensions and made them reachable only through App Store) But it was a long while ago

Otherwise, don't know why there should be troubles bringing them back.

 

[FriedChicken2]

You used a third party app to perform a restore and this is somehow Apple's fault?

You don't know what you're talking about.

A restore should bring back everything, but apple nixxed them on purpose and antagonistically because they disabled 3rd part extensions in Safari 12 (arbitrarily, they used to work fine).

 

[TiggrToo]

You don't know what you're talking about.

A restore should bring back everything, but apple nixxed them on purpose and antagonistically because they disabled 3rd part extensions in Safari 12 (arbitrarily, they used to work fine).

You used a third party application. Period.

Insulting me doesn't change that fact.

If you were going from a much older version to Montery then the software you used should be able to handle this. If it didn't and screwed up then that's not Apple's fault.

The issue lies between yourself and CCC.

Not Apple.

 

[Realityck]

I did a straight restore using CCC from my 2012 iMac to my 2019 iMac. When I booted into my 2019 iMac, everything was the same except my safari extensions (js blocker, µBlock origin, RES) were gone, and cannot be installed again.

WTF apple.

Why didn't you use Apple Migration Assistant instead, just use the CCC to be the basis of a snapshot, it would be seen as a usable external volume to run from. Anything not compatible would be placed in a folder as such. You could use this same method to go from running Catalina on your 2012 iMac to Monterey running on your 2019 iMac. Safari extensions aren't always compatible once you start moving between OS's.

Please note as you progress to Big Sur to Monterey, you can no longer make incremental bootable backups. 12.2 supported once once bootable snapshot, but 12.3 broke that method with APFS replication Bless Utility not able to make separate volumes for pre-boot/system/data. It still backs up everything onto one volume for Apple Migration Assistant to work for a restore. see

Monterey - Carbon Copy Cloner - Users Thread

Creating this thread since the MacOS 12 Monterey beta 2 was issued as a PB today. The most up to date version of CCC is 6.0.2 released 6/30 You will now see this when running the Monterey Beta I am not sure of any changes that would really effect this version compared to how it was running...

forums.macrumors.com

 

[44267547]

A restore should bring back everything, but apple nixxed them on purpose and antagonistically because they disabled 3rd part extensions in Safari 12 (arbitrarily, they used to work fine).

Could you explain how Apple ‘antagonistically’ disabled extensions? Antagonistically, meaning; to ‘provoke’. Is that what you’re trying to convey?

 

[johnkree]

First of all, like others pointed out, using a third party app to restoring a backup between computers that are 7 years apart and expecting that everything will work fine is... optimistic? This is not Apple's fault.
Second, Apple reworked the whole Extension system in the new OS. So your extensions aren't compatible to the new system.

 

[Mr_Brightside_@]

You used a third party application. Period.

Insulting me doesn't change that fact.

If you were going from a much older version to Montery then the software you used should be able to handle this. If it didn't and screwed up then that's not Apple's fault.

The issue lies between yourself and CCC.

Not Apple.

Would they have restored properly if Time Machine were used?

 

[TiggrToo]

Would they have restored properly if Time Machine were used?

Dunno - but at least using TM means that you can legitimately blame Apple if it fails.

Using CCC means all bets are off as you're entirely at the mercy of whatever methodology they have chosen - even if it's completely incorrect.

 

[HDFan]

A restore should bring back everything,

Would they have restored properly if Time Machine were used?

Dunno - but at least using TM means that you can legitimately blame Apple if it fails.

If you are talking about applications, not data, none of these are necessarily true if you span OS versions. If your apps are 32 bit and the new OS requires 64 bit, if your app is intel, doesn't run under rosetta, and you are moving to an M1, you can't expect it to work.

 

[MacGizmo]

It's been pointed out several times already, this has nothing to do with using CCC, and the same thing would happen had he used Migration Assistant or TimeMachine – Apple simply disabled Safari extensions a while ago. And they gave plenty of notice that it was going to happen. We can "blame" Apple for changing things, but that's not going to stop it from happening. We can also "blame" the developers who haven't updated their old extensions to work with the new system.

In short: it is what it is.

 

[Mr_Brightside_@]

It's been pointed out several times already, this has nothing to do with using CCC, and the same thing would happen had he used Migration Assistant or TimeMachine – Apple simply disabled Safari extensions a while ago. And they gave plenty of notice that it was going to happen. We can "blame" Apple for changing things, but that's not going to stop it from happening. We can also "blame" the developers who haven't updated their old extensions to work with the new system.

In short: it is what it is.

This is exactly correct. The smug “you used a third party tool, what did you expect” attitude is maddening, particularly about a utility as useful and, arguably, better than Time Machine like CCC.