Failed Connect APIs

Hello @metalinedev

There is validation on the plugin side for manual connection, and there is one scenario where it may fail.

Please check whether your Client ID falls into this category – for example if it starts with B (there are some cases like this, although they are rare). As a developer you should be able to verify this:

// Client ID: exactly 80 chars, word chars + hyphen only
if ( 1 !== preg_match( '/^[\w-]{80}$/', $client_id ) ) {
    throw new RuntimeException( 'Invalid client ID provided.' );
}

// Client Secret: exactly 80 chars, word chars + hyphen only
if ( 1 !== preg_match( '/^[\w-]{80}$/', $client_secret ) ) {
    throw new RuntimeException( 'Invalid client secret provided.' );
}

In short, the front-end form validation for manual connection expects the Client ID format to match specific rules (Start with A, 80 chars / format validation). If the credentials pass this validation, then the only remaining explanation would normally be incorrect credentials.

We have an open issue for this, and it will be fixed in the next plugin update, as currently, the regex is too strict.

That said, this still does not explain why the automatic connection also fails, so there may be something else involved there. But let’s start with digging into manual part first.

Kind Regards
Krystian