data-collector.min.js doesn't loaded about braintree-web-drop-in

[jplukarski]

@wirthandras , thanks for writing in.

It looks like there is a version mismatch here. Version 1.38.0 of the Drop-In should be using version 3.94.0 of the data-collector, which matches the version in the screenshot, but then you point to a data-collector version of 3.96.1. Which version of the drop-in are you actually using, and how are you loading the data-collector? In the drop-in, the correct way to load the data-collector is to pass in dataCollector: true in your dropin.create() method, as outlined in our documentation. Are you loading it separately with a script tag?

Also, can you share the reason it doesn't load? Is there any sort of error message to go along with that screenshot?

Finally, you are correct that we do not officially support Facebook Browser. This is because the Braintree SDK is not tested or developed with the Facebook browser, so we cannot guarantee it's performance. You can certainly continue to use the SDK within the Facebook browser, but you may run into issues. If you do run into specific issues with the Facebook browser, let us know and we will do our best to resolve that issue.

[wirthandras]

@jplukarski we updated the related package to "braintree-web-drop-in": "^1.42.0", that will be go production probably in next week, and yes we are using the option dataCollector: true which you mentioned. As I mentioned we were used the version 1.38.0 before the update. We are not added anything related to a separated script loading magic like a script tag.

The reason is unclear, we saw only a "failed" message in our monitoring tool. Could be a network problem.

We saw the problem only affected a limited number of users (<10) with various browsers.

[jplukarski]

@wirthandras thanks for the clarification. Without reason for the failures we would not be able to triage this issue to see if there is a bug in the SDK. I agree it's likely network or browser-related issues on the buyer's end.

We're going to close this issue out for now. If you continue to experience this issue or if you see it start happening more frequently you can reach out to our support team with timestamps, SDK version, and, if possible, steps to reproduce.

Thanks