I’m sitting here, typing away at this article in Firefox. I currently have Mail, iChat, and Twitterriffic open. They are all connected to the internet. Oh, there’s a new batch of tweets! And a new mail message! And in comes a new chat with a link to a funny video. Let’s check it out! Up pops Safari, tries to load the page, chokes, and dies with a pathetic message that it can’t find the server. Did I mention I was writing this in Firefox? Because I am. This is the story of how Safari 4 completely screwed over Webkit on my Mac.
I downloaded Safari 4 at about 3:45 today. I downloaded it using Safari 3. I installed Safari 4, and restarted. Eager to try out Safari 4, I opened it… and got the message you see at the top of this article. Okay, I thought, maybe there’s a little network communication issue. I quit Safari and re-open, to see the same message displayed again. Alrighty, I think, let’s turn off Airport and restart it. Still that same message. I reinstall Safari 4. Still. The. Same. Message.
Now angry at Safari 4, I quit, and whip out the uninstaller. After a restart, I fire up Safari 3, which the installer has restored, ready to start ranting on the ordeal. Guess what greets me? That’s right. The same message. Switching to Firefox now, which is connected just fine and dandy, I offhandedly check NetNewsWire for new RSS. Hey! NetNewsWire isn’t connecting! Fan-freakin-tastic. Safari 4 has caused a system-wide block between WebKit and the internet. Safari, NetNewsWire, Webkit nightlies, Stainless (a Google Chrome-like browser), Software Update, and more have all ceased to be able to communicate with the outside world.
I’m sure these results aren’t typical, but the fact that this could happen in a public beta is more than annoying to me. Does anyone have any similar stories? (And maybe a solution?) Sound off in the comments below.
I haven't had that problem. Well, I wouldn't know, since when ever I try to open Safari 4, it says it closed unexpectedly. I've tried installing about eight times now, and I'm back to 3.2…
Disappointed that there are errors like this in the public testing stages, but hey, it's still in beta I guess.
I think that you take your own risk with BETAs. BETA programs exist to resolves exactly the problems you are talking about. I mean before I could even install Safari 4 it forced me to update the most recent security update which I had been putting off. Apple wants to iron out these issues so that different combinations of 3rd Party Software do not have the interaction issues. In an effort to lessen the footprint of apps, they pull from common code bases. They can only fix the issue if the problem is reproducible. If they made the release closed to the dev community, there would continue to be this feeling that Apple is too secretive and doesn't let their kids out of the box. To believe that the problem is with Apple automatically because that is the last thing you have done, simply not the most effective method. Any number of third party software pieces could be at fault for a bad code base. Safari has hooks throughout the OS so there are compatibility issues. Who is at fault is a question for coders? BETAs exist to support the development community not the consumer. If the consumer gets involved that is your own business. Reading the EULA, such claims are equally made as a caution to users.
Yes, Betas are unfinished. But this is a public beta. There have been many developer only betas released to test these critical issues. By releasing a public beta, a company should be sure that any bugs that could arise won't affect system wide components.
By the way, after 45 minutes with a great AppleCare rep, we figured out that the Safari 4 installer had inadvertently enabled web proxies. After unchecking this in the advanced tab of AirPort preferences, everything was working fine.
I have no problems thus far (knock on wood). I was even able to get 1Password working too by following a set of instructions from crunchgear.com.
I hope things get better for you Adam, and I hope things stay good for me.
Did I just jinx myself?
It's working fine for me.
However, I am rather miffed that my favourite Safari plug-in Inquisitor does not operate any more. I have even tried to re-install it to no avail. Either a new version will have to be made or maybe Apple have stopped access to the search bar for plugins altogether now.
Don't quote me on this, but I'm pretty sure Inquistor (as well as most plug ins) has never been supported. I know for a fact that 1Password is basically a hack, and Apple has never supported it, so blaming them for it "breaking" isn't really possible.
I'm not saying I blame Apple at all. I fully understand it was never supported. I am just disappointed it isn't working anymore. I hope an update will remedy this.
I had the same issue as described in the article. I went into the Network settings and reapplied them… after a few minutes… everything started to work again…
Whenever I have installed Beta software in the past it has come with the warning not to install on production machines as it may cause problems. I've not installed Safari 4 as much as I am looking forward to it, as I don't want to experience any issues so will wait until the final release.
I thought the purpose of Betas was for developers to check their plugins/websites etc. in the new software as well as giving feedback on the application as not everybody has access to other pre-release versions.
@ Barry Ward from Birmingham, UK
Re: Inquisitor
You don't need it anymore. That functionality is now built into Safari 4.
So far the only problem I've had is when usgin MS Messenger 7.2 in the Mac.
Since I installed Safari 4 (both in the iMac and MacBook) the messenger doesn't let me write several messages without having to click again in the text area.
I wrote something, click enter.. it sends the message and I start writing again and it doesn't write anything.. I get frustrated as soon as I notice (it happens a lot because my habit is strong), and I click inside the text area to write everything all over again.
It's a really annoying problem.. I haven't try uninstalling so far, I'll do it and let you know if anything interesting happens.
Cheers
Well I also like it, and I'll like it even more when it's finished…
I've had just one problem so far.. I hope they fix everything soon.
@Oxchris
Of course that installing betas always comes with a risk, but if the purpose of betas was developer testing, Apple wouldn't post a link in the front page for everyone to follow.
In cases like the Safari 4 download, this beta is for everyone who, knowing the possible consequences, would like to see the app in action, and I'm pretty sure that Apple uses us as testers to discover general "minor" errors of the application.
What better test field that "out there".. there's no company in the world which can afford test labs with millions of different computers, configurations and environments.