iOS - ignore/drop errors from specific (old) versions of the app
Hi guys,
I realize you just closed Jason Terhorst's thread on this (iOS: Option to ignore errors from older versions of my app), but I'd like to reiterate how important this feature is for iOS apps. The release/deployment model is very different when updating an app in the App Store since you cannot force people to upgrade, which is effectively what you're doing when you release a new version of a website. It's not uncommon for users of an application to be 2-3 releases behind, in our experience.
A simple "ignore errors if version <= x.y.z" filter would really help clean things up (or if it's easier to implement, "ignore errors if version is in set "). Count these dropped requests against the API limits if you'd like -- you still get paid and your servers will do a lot less work.
Great product, btw. We've used it on the web for a long time, and now mobile.
Adrian ---- -- -
Showing the most recent page of comments. View the first page
Comments are currently closed for this discussion. You can start a new one.
32 Posted by hunterhillegas on 28 May, 2011 09:42 PM
Or alternatively, an option to block all notifications missing the key? That would effectively silence old errors.
33 Posted by Jared Egan on 29 May, 2011 10:13 PM
Hey, I agree this a must-have feature for an iOS crash notifier. From my point of view, it seems like it should be possible to block out of date crash reports as well.
But if you need to release, you probably shouldn't be waiting on Thoughtbot to update one of their products. If you can host a json file on a webserver somewhere, you can code something that allows you to remotely configure your app to run or not run the Hoptoad code. You can also use this implementation to decide if you want to force them to upgrade when your latest version is available. Better to get this code in early.
34 Posted by Andrew on 04 Jun, 2011 07:34 AM
I've been impressed with Hoptoad so far, but this lack of version filtering (and the seeming unwillingness to provide it with data that already exists) is just one of the buckets of cold water about giving me a reason to pay for this service.
It really seems there's been very little thought or effort put into supporting iOS in the months since it became supported. Heck, I can't even filter by development environment from the main project page and that's a pretty basic requirement.
My advice would be decide whether you really want to provide an iOS service, or spend the resources elsewhere.
35 Posted by mwhuss on 04 Jun, 2011 11:42 AM
To filter by environment you need to make sure the environmentName is set
appropriately. Then in on the project page you will see letters directly to
the left of the errors. Click on any of those to filter by environment. More
information on the environments can be found here:
https://github.com/guicocoa/hoptoad-ios
[HTNotifier startNotifierWithAPIKey:<# api key #>
environmentName:<# environment #>];
Version filtering is almost complete. If you would like to use it now you
need to use the development branch of the notifier:
https://github.com/guicocoa/hoptoad-ios/tree/development
You can set your latest app version under the Hoptoad project settings.
On Sat, Jun 4, 2011 at 3:35 AM, Andrew <
[email blocked]> wrote:
36 Posted by calebdavenport on 06 Jun, 2011 01:46 PM
the new notifier version that supports app version filtering is now live on github. For more information on how this works check out http://help.hoptoadapp.com/kb/ios/app-versions
calebdavenport closed this discussion on 06 Jun, 2011 01:46 PM.