I estimate I am between 2 and 4 days from reaching my next monetary target which I set myself for my apps. To mark this occasion I have decided to do something which Malcolm Barclay talked about at the last iPhone and Smartphone Publishers and Developers meet up. It’s nothing too exciting, just I want to give it a try!

In other news I currently have 5, yes FIVE, apps in review with Apple. I’ve been quite busy over the past couple of weeks as I’ve been between jobs. I’ve released updates to 4 apps (another update to Subnet Calc Pro off the back of comments from users) and 1 completely new app which will be interesting for anyone out there who uses a Zen Internet broadband connection!

I’m continually impressed by Apple’s ability to keep the iPhone platform going so strong. It would be interesting to try doing it full time, but I don’t want to take that risk at the moment as I can’t guarantee I’d have enough money coming in and I actually am very much looking forward to starting my new job on Monday!

UPDATE:
Well I reached it! And I have now almost reached my next target! I also have released the app for Zen broadband customers, it’s called ZeBbUs (Zen Broadband Usage) and it lets you know how much of your Zen broadband plan you have used this month.

I am having a strange issue with UIImagePickerController which is really bugging me. I’ve also found someone else with the same problem so I know it’s not just me!

When using UIImagePickerController, and the imagePickerController:didFinishPickingImage:editingInfo: delegate method gets called, I find that sometimes the returned image is nil, which depending on what you do with the image will cause a crash or at least not do what you expected. It seems to be a memory issue because when you reboot the iPhone and try again, it works and returns the image correctly. Also, I’ve not have the problem on iPhone 3G S which has more RAM, indicating again to a memory issue.

I’m wondering it the new imagePickerController:didFinishPickingMediaWithInfo: delegate method will work – as the other has been deprecated in 3.0 anyway.

But has anyone else had, and fixed, this problem?