The last update fixes two issues, the first I realized there was a problem yesterday and I mentioned it on the g+ page. There were a handful of Application Not Responding reports coming in and after a quick look yesterday, I realized that I committed a programming foul. Typically, anything that's going to take a long time or anytime you're going out of the device to get something (picture, info, etc) you want to put it in a thread. This way the thread can do it's thing and the main part application can continue doing it's thing. I had done this in the past in a number of places (getting the image and weather just to name two). However, I didn't think about doing this for all the new Yahoo! PlaceFinder web service calls that I mentioned in my Round up. Depending on the device, the connection or traffic Yahoo! is receiving the reply from the web service might take too long and the OS displays that lovely "Something took too long" do you want to Force Close, Wait or Report dialog. Most of the time, hitting wait will be good enough. This is one of those things as a programmer that burns me as I know better, but since I don't deal with it often (or not at all for my 9-5 job) I just didn't think about it.
The other thing in this update should hopefully resolve the any future problems that Stu experienced. Those problems frustrated him enough to leave this review. Long story short, I found Stu's email from the purchase order and dropped him a line. It seems (and I'm waiting for confirmation from Stu) that after the purchase of the dock extension is made 1) there's a lag between the purchase and the acknowledgement of the purchase 2) After the acknowledgement is received I'm not forcing a reload of the dock or any of the other stuff that needs to happen. The simple fix for him should have been a Reboot or a Force Close of the app.
I believe that in the time between the purchase and the review, the app wasn't restarted and therefore the extension was never fully 'activated'. The code change was relatively simple and hopefully other people who purchase the extension (and future extensions) will not have the same problems that Stu experienced. My apologies to Stu and any other users who experienced the same kinds of issues.