Since development is winding down, we are again in the need of some beta testers. If you are interested, drop an email to clevertangerine. All we ask in return is that you actually commit to beat on the app and, you know, test it.
Space is limited, so we cannot take everyone who offers.
There is light at the end of the tunnel. Looks like we are probably a day or two of work away from being feature complete. Then it is off to testing for a while to bang on the new features. It should finally reach the store sometime next month.
The scope of the release grew a bit as development got underway. There were a number of features that were originally planned for a later release that were pulled forward into this release along with a few feature requests that came in where we though we could sneak it in.
In the coming days, we will kick off a few blog posts on the new features.
So, if you are going to write a review that looks like this:
Twiddling the widget does not work!
We would ask that you instead send your concern to our support email address. That way, you are more likely to get a fix, and we do not have to try to use a line or two in a review to figure out what (if anything) is broken. Sometimes, “bugs” are not really “bugs”, if you catch our drift.
It would be really nice if Apple would let developers respond to the reviews…
In other news, development on the next release is winding down. Should wrap up in the next few weeks depending on how busy the day job remains.
RCLogbook has a few minor issues with iOS 5 that are not serious, but a bit of a pain. This time around, with the day job and all I did not have a lot of time to mess around with the beta builds of iOS 5. Both of these will be fixed in the next release.
The day job has been busy, but there is a lot of progress being made on 3.6. I am hoping to be able to get it wrapped up in time for Christmas, but we will see. There are some changes to the database coming along with other goodies.
Development continues on 3.6.0. This release should be relatively quick. The database modifications and supporting infrastructure changes are wrapping up today, then we will focus on getting the UI wired up to take advantage of the new database records. We will have a little more to say on the changes in upcoming posts.
If all goes well, 3.6 should be in the wild before everyone in the US is eating turkey.
Well, 3.5.2 is now on the App Store according to the App Store elves. That should take care of the last nagging iOS 3 issues (I hope). In the meantime, work has started on the next release. Current plan is to do something fairly quick to cover a few database additions that were punted on for 3.5.
Onward!
Ahh, 3.5.1, we hardly knew ye. It seems that 3.5.1 did not quite get all of the bugs that it should have taken care of. So, we are on to 3.5.2. All of the bugs are issues with iOS 3, so you can skip right over this if you are running iOS 4.
So others can learn from what has, so far, not been one of the smoothest RCLogbook release cycles, here is what happened…
Well, the bug is real. Crap. There is a crashing issue that can show up under iOS 3 when adding new events. The fix is simple, and a 3.5.1 release was just submitted to the App Store.
In the meantime, if you are still using iOS 3 on your device, you should not update RCLogbook until 3.5.1 is available.
According to the email from the Apple elves, the app became available mid-day yesterday. We have one bug report that popped up that we are looking into.
Generally, before you update to a new version it is good practice to download the complete binary database from the current version. That way, you had a copy of your database in the unlikely event things come off the rails.
