The Unofficial Apple Weblog (TUAW)

Reports of an odd bug affecting downloaded files in Snow Leopard have been circulating Apple's discussion boards recently. As reported by TidBITS, the issue appears to be affecting all computers running Snow Leopard.

While different users have reported varying symptoms and differing circumstances, it essentially boils down to this: if you download a group of files, and then attempt to open the entire group of files at once (rather than opening each file individually), chances are either some or all of the selected files will not open.

My initial response to this was that it could possibly be one of those "it's not a bug, it's a feature" ordeals. We have already seen some indications that Apple is working on enhanced security and virus protection in Snow Leopard, so it stands to reason that the operating system may be simply trying to prevent what it thinks is malicious activity by imposing restrictions on what you can and can't do with a newly downloaded file.

Of course, that's just my theory, but I'm apparently not the only one who has explored that possibility -- a reader on the Mac OS X Hints forum discovered some hard evidence supporting that theory. In OS X, newly downloaded files are flagged with a "quarantine" attribute, which remains until the file is opened. If this attribute is set when the file is launched, and the file is an application, you would receive the typical "This application was downloaded from the Internet" confirmation before the application is allowed to continue launching. This is nothing new in Snow Leopard, but it would seem that the additional protections and scanning that were added to Snow Leopard most likely prevent opening multiple files so that each file can be individually checked before it is launched.

Whether or not this is a serious bug or a minor inconvenience depends entirely on your workflow. Personally, I find that I don't often open multiple files from Finder, as most of the applications I use have the ability to select multiple files from their Open dialog. I can easily see where this might pose significant problems, however. For example, if you do a lot of work with graphics, you might download a several photos from a client, highlight them and open them with a custom tool that automatically resizes and processes for you. With this bug in play, that task would become much more difficult if you had to open each file individually.

So what about you? Is this bug bugging you, or is it a non-issue? If you are affected, feel free to chime in with your experiences on the discussion boards, and be sure to let us know in the comments!

If you've been waiting patiently for the Dropbox app [iTunes link] to hit the App Store, your wait is over. The app has arrived, and brings with it the simplicity that Dropbox users have come to know and love.

Since Dropbox itself is a free service, it's a pleasant surprise to see a simple, easy method for creating a new Dropbox account right off the bat if you don't happen to already have one. The app just asks for a name, e-mail address and password, prompts you to accept the terms of service, and creates the account. During my testing, I did encounter a problem where I would receive a nondescript "Account creation failed (null). Please try again." message, which I'm guessing may be due to high load on their servers. Still, this is not an encouraging encounter for new users.

Once logged in, everything worked pretty smoothly. On first login, You are presented with a brief welcome document that highlights some of the features of the app. Backing out of the document will take you to your Dropbox, which quickly lists any of the files and folders you may have in there. The app features built-in document preview for several types of files, including PDFs, text documents, spreadsheets, pictures and videos. You can also tag files as a favorite by tapping the star at the bottom of the file viewer, which adds the item to the favorites panel and caches a copy locally on the device so that it's immediately available.

An unexpected feature is the ability to take pictures, video, or use existing media and upload them directly to the Dropbox. This could definitely be handy if you need to take a quick video and have it available on another machine without having to plug in your phone and wait for it to sync. Also unexpected, but incredibly welcome, is the massive amount of documentation that is available from inside the app's settings panel. In addition to giving you general details about your account, the settings panel offers a link to watch a video about how Dropbox works, take a tour of the features, or browse their complete online help library, without having to leave the app. As many apps fall short in this area, it's refreshing to see such detailed documention available, let alone right from the app.

A couple of side notes: As I mentioned above, the new user signup does not appear to work properly sometimes. I'm guessing this will be fixed in short order, though. You can log out of your Dropbox account by tapping the Unlink iPhone from Dropbox button on the settings panel, but beware that you will loose any favorites you have stored (the app does warn you of this). And finally, when you do logout of your account, the app just disappears from the screen, as if it crashed, although you are successfully logged out. In my eyes, these are minor issues (well, aside from the signup problem), and will likely be addressed with future updates, but still good to watch out for.

All in all, this is a very well done, simple app that connects you with an already great (and free) service. It's available now in the App Store for free.

Since the birth of the App Store, Apple has oft stated "there is an app for just about everything." Now, it seems they have come up with a great way to prove their claim.

Apple has added an "Apps for Everything" section to their website, complete with a wide range of selections from Apps for Cooks, to Apps for Managing Money, to Apps for Moms and Dads. Each section is then broken down into different tasks or activities that are associated with the group, and highlighting a particular app for that item, complete with screenshots and a link to the App Store.

Based on recent trends, including our own "5 Apps" series, it's easy to see that breaking down the massive list of apps available in the App Store and grouping them by different occupations or activities is a great way to bring otherwise hard-to-find apps to the spotlight. It's good to see that Apple has come up with a nice, clean way to do this on their own website, and I'm sure it will serve as a great resource to users who are looking for the perfect app.

[via LoopInsight]

Users of Tweetie, the popular Twitter client for both Mac and iPhone, have reason to be excited: a new version of the iPhone app, Tweetie 2 (aptly codenamed "Bigbird"), is confirmed to be on the way.

In a preview of the new version, Scott Kleinberg of ChicagoNow detailed his experiences with beta builds of the upcoming release. From the screenshots provided, it's clear that several interface improvements have been made, including a quick menu that provides easy access to several new features while posting a tweet. Other improvements include the ability to send video tweets, persistent session handling that restores the app to its previous state, conversation threading, draft management, and geotagging.

While Scott's review suggests that the changes and improvements make Tweetie 2 feel like a whole new app, Tweetie developer Loren Brichter indicates that it really is -- it's a complete rewrite from the original app. In addition to the major features, the new version also boasts integration with several 3rd party services, and a host of configuration options, from new gesture options to custom Twitter API settings.

Of course, not everyone will be happy with the update. There is already a stir among beta testers over the app's use of pinstripe backgrounds on the profile and single tweet views. Also, there is the issue of cost: Tweetie 2 will set you back $2.99, as it is being offered as a new app instead of a free upgrade to existing users. When it comes to upgrades, most desktop applications follow a pattern where minor updates (such as upgrading from version 1.0 to 1.1 or 1.1.2 -- often refered to as "point releases") are provided free of charge, and major updates (from version 1.0 to 2.0) usually require the user to purchase the new version of the software.

With iPhone apps, however, Apple does not provide a system to allow developers to do this. Developers can release upgrades and bug fixes as free updates to their applications, but if they invest a lot of time into a major update to their app, they have to submit it as a new, different version of the application rather than an upgrade to the old version, and there is no option to allow users who have perviously purchased the original app to receive a discount on the new version. So users are faced with having to pay full price for the upgrade, which in this case, is another $2.99.

In my opinion, this is not an unreasonable amount to pay for a major upgrade to an already great application, but there are users who feel they shouldn't have to pay for the upgrade. My advice to them? If you can't spare $3 for the amount of time and effort that was put into making a decent, feature-rich upgrade, don't bother using it. Stick with the original Tweetie or find another app that you're willing to pay for.

So, controversy aside, Tweetie 2 looks very promising. The latest beta build that was provided to developers is expected to be the final build, and if things go well, we should see it hit the App Store in the coming weeks. An update to the desktop version of Tweetie is also in the works, and will probably surface after the iPhone app is released.

Update: TUAW reader Ahmed drew our attention to this tweet, indicating that Tweetie 2 has been submitted to Apple! Assuming there are no hold-ups, we can probably expect to see it hit the App Store in a few weeks.

What do you think of the new version? Will you be upgrading when it's released? Let us know in the comments!

Didn't you hate it when you were a kid, and you would complain to an adult about something one of your siblings was doing, just to end up getting yourself in more trouble than they ended up in?

Well, you might say that's exactly what is happening to Palm and the ongoing dispute with Apple over the Pre's ability to sync with iTunes. The company has landed itself in some hot water after drawing the attention of the USB Implementers Forum (USB-IF) by filing a complaint against Apple for violating "the letter and spirit of the USB-IF Membership Agreement," which is "intended to facilitate interoperability between USB devices."

What that's referring to, of course, are Apple's repeated attempts to block the Palm Pre from syncing with iTunes. The whole question of whether or not Apple is in the wrong by doing so is entirely debatable, but the USB-IF seems to be of the opinion that Apple is following the letter of the law:

"In the view of the USB-IF, Palm's allegation (if true) does not establish that Apple is using its Vendor ID (VID) contrary to the USB-IF's policies... Therefore, under present USB-IF policies, the USB-IF does not consider the alleged use, without more, to be 'improper.'"

To summarize, the USB-IF does not believe that Apple is in violation of the agreement, based on the information provided in Palm's complaint. What is interesting with this chain of events is how Palm continues to shoot itself in the foot trying to find a resolution. Rather than work out a deal with Apple or write a custom application to legitimately communicate with iTunes, Palm has chosen the sly path of attempting to trick iTunes into working with the Pre, first by simply identifying the device as an iPod that was made by Palm, to actually using Apple's assigned USB vendor identifiers to completely masquerade as a true Apple iPod.

Perhaps even more startling, however, is that Palm is completely open about the whole process, even going as far as detailing the workaround in the complaint to the USB-IF, saying "Palm will shortly issue an update of its WebOS operating system that uses Apple's Vendor ID number for the sole purpose of restoring the Palm media sync functionality." Although openness is usually a good thing, it seems that Palm may have encountered too much of a good thing: the USB-IF turned the tables, and hinted that Palm itself may be in violation of its own agreement (emphasis added):

I attach for your information the USB-IF's adopted and published policy regarding Vendor Identification Numbers (VIDs). Under the Policy, Palm may only use the single Vendor ID issued to Palm for Palm's usage. Usage of any other company's Vendor ID is specifically precluded. Palm's expressed intent to use Apple's VID appears to violate the attached policy.

Please clarify Palm's intent and respond to this potential violation within seven days.

What's next for Palm? Will the company finally decide to work something out with Apple? Will Palm start embedding USB chips out of refurbished iPhones so that it isn't technically misreporting the device's identity? Only time will tell, and in the meantime, at least we can look back and say "Palm, we told you so."

If you use Gmail, you have something to be excited about today, because you can finally have new email messages pushed directly to your iPhone when they arrive.

For many users, however, their first response is "it's about time!" and others have even gone as far as saying "it's finally here, no thanks to Apple." This new feature, unveiled this morning by Google, has even been called a "workaround" to Apple's alleged refusal to support push email, but in reality this isn't the case.

Push: What is it, and how does it work?

To understand why push services have not been available before, let's first discuss what exactly push is. When a client (be it a mail program, Twitter client, or web browser) needs to notify a user when new content or information is available, it has to periodically connect to the server and check for changes.

This is the way email clients have worked for years: the client checks with the server at a defined interval (usually every 5-15 minutes), downloads any new messages, and notifies the user that new mail has arrived. Many other services, such as RSS feeds, Twitter, Facebook, and even the Gmail website work the same way; they just check the server more often, which gives the appearance of real-time notifications.

Other services, such as instant messaging clients, maintain a constant, active connection to the server at all times. When new information is available for the client, the server sends, or "pushes" the information directly to the client as soon as it is available. In corporate environments, mail services such as Microsoft Exchange have paved the way for push email, by having the mail client (usually Outlook, Entourage, or other clients that support Exchange) maintain an active connection to the mail server, which allows the server to notify the client immediately when new mail arrives.

Read on to find out how Gmail push works, and what you need to know to get it set up on your phone.

Read more →

Well, it looks like they were telling the truth, for once. Last weekend, a friend of mine just happened to forget that my iPhone couldn't receive MMS messages, and sent me a picture he had taken. So needless to say, I was surprised when I saw the MMS notification, complete with picture, show up on my phone.

I was fully prepared to hop on to TUAW and write up a post, letting everyone know that MMS was turned on a full three weeks ahead of schedule. To be on the safe side, I decided to check with others to see if MMS was working for them. Unfortunately, everyone I asked said MMS was still not working on their phones.

Here at TUAW, we have received several tips over the past few months from individuals who have indicated MMS had suddenly started working for them. Many of these were from people who had also installed an updated carrier settings profile to their phones, which has produced mixed results across the board, ranging from MMS actually working to accidentally removing Visual Voicemail and even the basic ability to make phone calls. Even with these profiles installed, however, most people were still unable to use MMS due to settings on their AT&T account which prevent iPhones from sending media messages and filter incoming messages through their web-based "Multimedia Messaging" platform.

For the record, I was running the iPhone 3.0 software, and I had previously modified my carrier settings, although that hadn't really made much of a difference until now. I had been lucky, in that I had found a profile that did not break anything, and had even temporarily enabled tethering on my phone, which I successfully used for about five minutes to try it out (although when I later tried to use the tethering during a recent power outage, the option mysteriously disappeared from the settings panel after I turned it on). So I had to draw the conclusion that my newfound ability to send and receive MMS messages was probably related to the carrier settings I had previously tinkered with, and I was doubtful that it would last.

Now here we are a week later, and MMS is still working for me. But what's even better: reports are flowing in from around the country that MMS has started working in different markets. There are still quite a number of people out there that don't have it yet, but it looks like AT&T is actually serious about meeting the September 25th deadline. Yeah, it's definitely not "later this summer" as promised, but at least we are finally seeing some progress instead of just vapor dates and promises.

For those who are wondering where MMS has landed, HowardForums has a thread running with many people reporting which locations are up and running. Also, it's worth mentioning that the majority of users who have reported MMS as working have the "AT&T 5.0" carrier profile installed, which is included as part of the iPhone 3.1 update. So be sure to update if you haven't already!

Thanks to everyone who has sent tips in regarding MMS in their area.

Yes folks, it looks like the online Apple Store is currently down. Given that it is 10:00 PM on a Saturday night over in Cupertino, I'd say chances are pretty good that it could just be some simple maintenance, but you never know.

We'll keep an eye out for any changes and post an update if anything exciting happens!

Apple has released version 3.3 of its remote administration tool, Apple Remote Desktop (ARD). The update is available both via Software Update, and from the Apple website.

According to the release notes, the update comes with a number of improvements, including the long-desired ability to send function keys and system shortcuts (Force Quit, cmd-Tab for application switching, cmd-shift-Q to log out) to the remote Mac; previously those commands would execute on the administrator's machine, which could cause undesired behavior. Also included are support for wide-area Bonjour connections and improved performance when using a shared screen.

If you're just starting out with ARD, be sure to check out some of the great tutorials Apple has posted online. From getting set up, to providing remote assistance to users, to automating routine tasks; as Apple might say, "there's a tutorial for that."

Thanks to TUAW reader Jim for giving us the heads up!

Earlier today, I posted about the ability to find previously deleted emails using the Spotlight search on the iPhone, adding to the already intense swarm of news surrounding this issue. My findings were that, by ensuring your trash folder was emptied and refreshed, the problem appeared to be solved.

However, many of you responded indicating that this did not work for you, and that you were still seeing cached messages. Then Cult of Mac posted an update to their original piece, suggesting that the problem was more specific to POP accounts. Although I had tested both POP and IMAP accounts with similar results, I decided to investigate further.

First, to clarify: The problem here is *not* with Spotlight caching the contents of your email, as many have suggested. Spotlight simply indexes the available content on your phone, and logs a pointer to it. When you tap a search result, it opens the associated application and tells that app to view the content. In this case, it sees an email message and asks Mail.app to open it, which it does, because Mail.app still has the message content stored locally. Secondly, this appears to be specific to POP accounts. On IMAP or Exchange accounts, deleted email messages do appear in Spotlight results until the trash folder is emptied, as described in my earlier post.

I created a fresh account and configured it for POP access, then downloaded the mail. Searching spotlight, I could see the message I was looking for. I then went back to the message and deleted it, and that's where the fun starts. I conducted this same test multiple times, and found that sometimes, the message would now show up in Spotlight twice, one result opened the message, intact, with the Inbox listed as the folder to return to; the other displaying a message in the trash folder, but with an error displaying the body of the message. Other times, I would only see one result, pointed directly to the trash.

Read more →