Airbrake rejects notices where the app-version is a pre-release even when it's later than the "Latest app version"

goodreads's Avatar

goodreads

13 Jan, 2012 04:12 PM

  • For one of our projects, our current "Latest app version" is set to "1.7.2".
  • We are sending notices to that project with '/notice/server-environment/app-version' set to "1.7.3-beta" or "1.7.5-beta" (pre-releases after 1.7.2)

Observed behavior

The server rejects the notices, responding with "422 Unprocessable Entity", body: "<error>Notice for old app version ignored</error>".

Expected behavior

The server should accept these since they are not older than the project's app version, and respond accordingly.

Additional notes

  • The documentation for the app-version field, by stating "This version field uses Semantic Versioning style versioning," implies that pre-release versions are acceptable.
  • The examples for iOS (which really applies to more platforms), do not illustrate what happens when a pre-release "Notifier App Version" is submitted that is greater than (has a higher normal app version) than the "Current App Version"
    • further, with Semantic Versioning 2.0.0, pre-release versions will probably need to be preceeded by a dash (e.g., "2.0.0-beta1" vs "2.0.0beta1")
  1. Support Staff 2 Posted by benarent on 17 Jan, 2012 11:29 PM

    benarent's Avatar

    Hi Goodreads,

    Sorry for the delay. I've pushed this over to our iOS team.

  2. 3 Posted by Ryan on 15 Feb, 2013 07:58 PM

    Ryan's Avatar

    Hello, we are currently revisiting tickets that seem that have been resolved. If you have any further questions let us know. Send an Email to
    [email blocked].

    Thanks,
    Ryan

  3. Ryan closed this discussion on 15 Feb, 2013 07:58 PM.

Comments are currently closed for this discussion. You can start a new one.