Uncaught Error: Braintree API Client Misconfigured: clientToken required.

Hi there!

I know this can be so frustrating when it seems like everything is exactly the same as on the previous server, but it’s not working! It’s hard to know what’s happening here because we can’t see exactly what is happening, but maybeour troubleshooting suggestions here will help.

I know this is obvious, but something is different about the client token on the new server than the old server. Let’s target that first.

? Check that you are not using production API credentials in the sandbox or vice-versa.
? Check that your Merchant ID, Public Key, and Private Key are correct, & that you’re connected to the right Braintree environment.
? Double-check that your connection settings are correct
? Ensure your shop currency matches the currency of your Braintree account.

I hope that helps at least a little. Let us know if you make any progress.

Hi @kristinaplauche,

So we have followed your instructions and everything looks fine. I have investigated this issue by reading method by method through the plugin’s code and found out that suprisingly the token is being generated! The problem is that in ClientTokenGateway::_doGenerate()method there is a weird response returned from POST request. “Weird” means that there is an array returned with an empty string as a key, and an array with token as a value. To make it more clear, here is the actual and expected behaviour:

Actual response:

var_dump($response);

//prints:

array(1) {
 [""] => array(1) {
    ["value"] => "ver_long_token_string"
 }
}

Expected response:

var_dump($response);

//prints:

array(1) {
 ["clientToken"] => array(1) {
    ["value"] => "ver_long_token_string"
 }
}

So I came up with a quick workaround and did something like this:

if ( ! array_key_exists("clientToken", $response) && array_key_exists("", $response)) {

   $temptoken = $response[""];
   $response = array(
     "clientToken" => $temptoken
   );

}

I just check if the response is (IMO) invalid but contains the token and if it does, I append it to the response. After I did it, I found that there is exactly the same story with transaction response in TransactionGateway::_doCreate()method so I applied the same workaround here too. After that, we were able to make payments via BrainTree.

So I wonder why is it happening? I hope information I provided you will help somehow. IF there is something more I could do to help you identify the issue, just ask ??

• This reply was modified 7 years, 3 months ago by dawidadach.
• This reply was modified 7 years, 3 months ago by dawidadach.

Hi @dawidadach!

The problem is that in ClientTokenGateway::_doGenerate()method there is a weird response returned from POST request. “Weird” means that there is an array returned with an empty string as a key, and an array with token as a value.

Have you tried switching to a default theme and disabling all plugins except for WooCommerce and Braintree? Then testing to see if the weird response is still returned? If not, can you please try that and let me know the results?

If that weird response still returns when the site is in that “vanilla” state of a default theme and only those 2 plugins active, then we’ll know we don’t need to look at the other plugins or theme as possibly causing the problem here.

Thanks!

Hello @kristinaplauche,

So we have investigated this issue even more. And this is what we have discovered:

Both clientToken and transaction were returned correctly from the API. I checked it deep in the Http::_doRequest() method. The problem was that after the response was returned in XML format, the Xml::buildArrayFromXml($response['body']) method which calls this one Xml\Parser::arrayFromXml($xml) was encountering an issue with DOMDocument. To be more specific, the problem was in this line:

$root = $document->documentElement->nodeName;

$root was NULL, because $document->documentElement was undefined. And why it was undefined? I found the answer here: https://github.com/braincrafted/bootstrap-bundle/issues/461.
TL;DR the problem was in the php.ini file. We have been loading dom.so extension in this file which was causing all the issues. After we’ve commented out this line:

extension=dom.so

everything was working fine.

So if someone will encounter the same issue then the solution is to remove the mentioned line from php.ini file and restart your server. I hope it will help someone.

Thanks for the support, topic closed.

• This reply was modified 7 years, 3 months ago by skaczmarek03.
• This reply was modified 7 years, 3 months ago by skaczmarek03.