This update adds or improves the following:

  • Open Directions for newly entered addresses
  • Improved performance of the search field
  • Added US brands in Food & Drink and Shopping
  • Fixed stability issues (see below)
  • Fixed Portuguese localization

Where To? 3.0.5 is now available for download on the App Store.

Two updates in less than 2 weeks? Are you crazy?

Let me explain. iPhone developers have access to crash reports provided by users via Apple’s backend system iTunes Connect. The number of crash reports shown for Where To? has always been minimal (around 1-3 reports per update). Nevertheless, in our last update we integrated the excellent CrashReporter framework QuincyKit by Andreas Linde & Landon Fuller. Much to our surprise we received quite a lot of reports (around 200 individual crashes for 20 different issues up until now). We compared this to the number of crashes reported by iTunes Connect: Zero.

It was really mind-blowing, especially since the issues found had been in Where To? since ages. Fortunately, we were able to fix the majority of issues and so we didn’t want to wait any longer to rollout these stability fixes. For any developer with a zero-crash-tolerance, I really recommend taking a look at the CrashReporter framework. Don’t be fooled by the small number of crashes shown in iTunes Connect!


  • Fred

    wrote on December 18, 2010 at 1:36pm

    Interesting, that’s why we don’t get any crash reports… 🙂 Might make sense to file a Radar about this, the concept of having built-in crash reporting for all apps without any extra effort and frameworks is still great.

  • Andreas Linde

    wrote on December 18, 2010 at 1:59pm

    @Fred: In an ideal world I would agree. But there are several issues with that.
    1) Apple gets way too many crash reports to provide up to date data. You are currently able to refresh your dataset once a day. The build in frameworks helps to see live data.
    2) Apples aggregated reports only work once the app is released, not while the app is being in development and testing. Letting your testers search those files manually is not very user friendly and in the end you won’t get the data either.
    3) By far most users decline the request if iTunes is allowed to send data to Apple, which contains crash reports. So the devices gather the data you would need, but Apple will not even receive it.
    4) Apple does not provide an interface to work with the crashes, group them, make notes, classify, mark as processed
    5) all the other benefits you can have with a build in reporter I did not mention yet 🙂

    The Apple developers responsible for the crash reporting service iTunes Connect provides know about this framework since several months. There is just not much they can do to improve it.

  • choise

    wrote on December 20, 2010 at 4:44pm

    thanks. the crashreporter framework looks good. implementing it in my next updates 🙂

Comments are closed.

Subscribe to the FutureTap Newsletter

View previous newsletters

We will use your name and email address to provide news and offers about our apps. We will treat your information with respect. By clicking below, you agree that we may process your information in accordance with our privacy policy.