Breaking change in 1.1.15. AuthenticationException is now a checked exception, it was un-checked previously

Hi,

You introduced a breaking change in v1.1.15.

By making AuthenticationException inherit from Exception you are effectively requiring the developers to check for this Exception. If they didn’t, then their code breaks when they try to update to v1.1.15

Look at AuthenticationException class in this compare view.

Or just this image highlighting the change.

This should not be a revision number update. Since this breaks existing code, this should be added to your next major update.

[imakhalova]

Hello, Thank you so much for your feedback. Sorry, that we didn’t set version to 1.2.0 as we probably should have to. You’re right, this is build break change, but if your app wasn’t catching this exceptions before this change, it could easily get runtime exception and your app will crash. So we see a big benefit of notifying user that method can throw an exception. We hope that you’ll find this change useful.

[weijjia]

@Ricalo Yup, it’s our bad to not update the version correctly for causing the confusion. Also thank you @imakhalova for the explanation.