This morning I received an email from a user saying that the app stopped working. After one round of back and forth, I realized I shipped the product with a serious (show stopper) bug: I was playing around with adding a comma separator around the time I made change for v 1.2, and I left the code there when it shipped. Now I break pretty much everyone’s nest egg if they run the updated (v 1.2) app.
This little incident again illustrate the thing I mentioned last week: testing
and another topic I would like to talk some time later: source code control.
Luckily, the fix was relatively easy: I comment out the code where I put in “exta comma” for numbers. Because the app persists the number to the file system, I need to do some String manipulation in Objective C (basically remove the extra comma) when reading from the file during app loading. Here is a StackOverflow discussion thread I followed on this topic.
BTW, the user has entered the opportunity to win the $25 Amazon gift card, as I said a bit earlier.
PS: it appears the ratios (saving progress; income ratio) are still correct in those cases, despite the error of dollar amount. Note the ratios are more important in reality, though I can understand the dollar amount are more important in most people’s mind.
PS 2: it’s interesting to see sometimes, when things are broken, it started to get attention. This reminds me a story in which an app got a lot of “ad click” because the useful data feeds were broken, and all the user can see is the Ads.
