safari 5.1 ate my Disconnect extension

The same "error" occured for me, and I haven't found any other reference to it online.

It seems unlikely that Apple would pick on that specific extension, when there are plenty of adblockers and other related extensions still operating. Has this ever happened with other extensions?

While it's true that Apple are quite "Strict" with the content they allow to be used, I can't see why they would care about one specific Safari extension

I'd be very grateful if you could post any reply you get, or any solutions. I've also made a few enquireies and I'll post what I find.

Hey there, I'm the developer of Disconnect. Thanks guys for pointing me here.

It'd be awesome if somebody from Apple could give me a hand. I spent most the night troubleshooting to little avail and thousands of people are^H^H^H were using the extension(s). :-(

Here's all I've been able to come up with so far:

* Besides Disconnect, my other Safari extension, Like+1, is also

uninstallable and getting automatically uninstalled

* The problems happen in Safari 5.0.2 and up

* The extensions haven't changed in weeks

* My developer account seems to be in good standing, i.e., isn't

blacklisted or the like

Well byoogle, it's a true pleasure to meet you. Your extension has helped me keep FaceBook corralled in it's own little corner of the net and not following me like a personal injury lawyer after a workplace accident.

Please let me know if I can help get the extension working again, although my knowledge of programming is non-existent.

Besides Disconnect, my other Safari extension, Like+1, is also uninstallable and getting automatically uninstalled

This makes me feel better, because it suggests that it isn't an isolated incident.

Has there been any word from Apple?

I haven't heard anything from Apple, but like I said, my developer account doesn't seem to be banned. I guess they could've blacklisted my extensions individually, but I think there's more likely some conflict between Safari 5.0.2+ and my common code.

It really ***** that, unlike you guys, most of the thousands of users who've installed over the last few months already have or are going to get the extension automatically uninstalled and probably won't even know what happened because the error message is meaningless.

Um, sorry for using such a foul word: http://j.mp/nw5sey. :-P

I'm able to install it manually on 5.0.5 on Leopard. Is your developer certificate expired?

Thanks for the extra info.

Some sort of expiration was my first guess and the first thing I checked because I registered with Apple almost exactly a year ago. But I made a test extension that's installable, so the problem is elsewhere.

Since I posted, we managed to isolate the issue to a large chunk of code. If Safari's error messaging and handling was any better, we could easily have a fix by now and no broken users.

(I hope I didn't say any bad words this time!)

Have there been any changes?

I’m sorry a fix took so long, guys, but the extension is finally fixed. You’ll need to reinstall from:

http://disconnect.me/

If you’re interested, the problem was our developer certificate somehow got remotely reset. The reset invalidated the certificate you installed with. In other words, Apple’s developer platform is a mess.

I've said it before, and I'll say it again: THANKYOU for all the hard work.

It seems to be working now. No more FaceBook following me around like a puppy.