Are there any circumstances CloverAuth.authenticate can fail for a live merchant?

We have a merchant who cannot login to our app (K1FV6NJ0G4RJ1). I am 99% sure it is because some exception is thrown when I do this:

CloverAuth.AuthResult authResult = null;
try {
    Account a = CloverAccount.getAccount(context);
    authResult = CloverAuth.authenticate(context, a, true, null, null);
} catch (OperationCanceledException | AuthenticatorException | IOException e) {
    e.printStackTrace();
}

I have a vague recollection of this happening before to another merchant and the device was actually replaced. It is not affecting anyone else. Has anyone seen this, and what could cause it?

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Jeffrey Blattman ♦♦ commented · Jul 22, 2019 at 11:26 PM

This could happen (normally) if the device was offline the first time the app was used. Otherwise it should never occur.

Get logs from the device. That'll include the specific reason it failed. Consider integrating a service like Crashalytics so you'll be able to get the logcat and know how often it is happening.

0 ·

Dan Jeffrey Blattman ♦♦ commented · Jul 26, 2019 at 03:10 PM

Thanks Jeff, yeah we have Crashlytics but because it's just a caught exception I wasn't actually logging it specifically but I will now. Just glad to know whatever is happening is unusual (so maybe not even the issue).

0 ·

question