Add error handling to common errors on API calls

Issue #17630 new
Leonardo Montiel
staff created an issue

Currently on Bitbucket there exist API calls that return a generic 500 error with the message "Something went wrong". Such errors include authentication failed due to branch permissions or repository I/O issues.

It would be nice to have these messages show up on the UI instead of just showing a generic page with an error code.

Comments (1)

  1. Pieter Dirk Soels

    I received these generic 500 error messages when committing on a branch where I do not have permission to. I also received them when, apparently, Bitbucket imposed a lock on the repository due to another process blocking any modification to the repository.

    As a developer using your API I would like to account for these problems by being able to match on more descriptive status codes and error messages.

  2. Log in to comment