checkAvailability error

[bramley-stride]

In the new v2.0.0 of the sdk, every time it starts it throws a checkAvailability error, as per eg the below logcat error:
resultProcessing > Failure >>> java.lang.Error: checkAvailability error

This makes it difficult to check the chat availability before showing the chat.

The following screenshot showing a callstack may help:

In this instance, the API actually returned status available, but for some reason "checkAvailability error" was returned to my callback.

[ALobastov]

The issue indeed exists - if the application register callback BEFORE calling init() the callback will receive CheckAvailability error.

However per source control log, this was introduced on March 04 2021 even before very first release so it always existed. Nothing changed in that area with release 2.0. This means the client application changed (most probably it used to register the callback after calling init() and now it registers callback before).

Please review the application code to make sure it registers the callback after calling API::Init().

We will fix the issue in the next SDK release unless the workaround above does not work for some reason.