|
Greetings all, I want to update everyone on the status of JetSet Expenses 2.0 and where things are. I was so close to hitting the submit button to Apple as everything was looking great. The bug reports had gone down to zero and I was just looking to test it a bit more before I submit. Then iOS 5 shipped which I knew was close but it happened much quicker than expected. Then Google happened where they updated their security for login and updated the APIs. So now the application was not running properly on iOS 5 and Google was broken. I posted here earlier saying it was Google's problem and I was hoping the issue would go away. In fact in the past that is exactly the resolution--just wait. So I worked on the iOS 5 issues and ended up getting things up and running on iOS 5 (without Google). When the issue with Google did not go away I did the research and found out that hte APIs I am using are outdated and that in fact it was my fault (according to the Google support forums) for not following the development of their APIs closer. They claimed that the API was updated a year ago and that I should have somehow knew this. Anyway--now I am working on getting it integrated. One thing I will say about Google and their code projects is this--they are not for the feint of heart. The documentation is lousy (and out of date!) and worse there are missing files from their latest distribution. I am now working with Google to resolve the issues and rewrite the Google docs connectivity using their updated SDK. If I can make some progress over the next week and get the feature back I will do one more round of testing and then submit. If it continues to the epic battle it has been for the last couple of weeks I will pull the feature and work on it for an update. So that is the status.. it is coming along.. but slowly. If you want to beta test please go ahead and send an email to support. Many thanks for your patience. |
