react-plaid-link: Error loading Plaid null appears to be back in v2.2.3

I’m receiving the same Error loading Plaid null that appears to be reported in issue #86 when upgrading to v2.2.3.

It does appear react-script-hook was upgraded to v1.1.0 in v2.2.3, I haven’t dug in to see if that could be causing the issue or not.

If I navigate away and back, everything works and there is no error.

I downgraded to v2.2.1 and it works fine.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 20
Comments: 18 (3 by maintainers)

Most upvoted comments

It’s still an issue on v.3.2.0. Any plans to fix it?

ghost on Jun 23, 2021

I’m seeing this in 3.1.0. For me the issue is highly reproducible when I use multiple “link” buttons on the page. On initial load / page refresh one button usually loads correctly while the other buttons often (but not always) fail. When one fails it remains disabled and there is a stack trace like the below. Sometimes (but not always) they all load correctly.

Error loading Plaid null
console.<computed> @ index.js:1
(anonymous) @ index.umd.js:355
invokePassiveEffectCreate @ react-dom.development.js:23487
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
flushPassiveEffectsImpl @ react-dom.development.js:23574
unstable_runWithPriority @ scheduler.development.js:646
runWithPriority$1 @ react-dom.development.js:11276
flushPassiveEffects @ react-dom.development.js:23447
(anonymous) @ react-dom.development.js:23324
workLoop @ scheduler.development.js:590
flushWork @ scheduler.development.js:545
performWorkUntilDeadline @ scheduler.development.js:157

mpvosseller on Feb 17, 2021

@wnamen Unfortunately, I was not able to find a good solution for this. However, I added <script src="https://cdn.plaid.com/link/v2/stable/link-initialize.js"> into my index.html as one user suggested in the comments at the bottom of #86 and this “fixed” the issue for us by making sure the script was loaded before the hooks get run. Not a permanent solution but it got us up and running until this issue gets resolved.

zsidnam on Sep 8, 2020

Interesting I thought we fixed this in 3.1.0 via #164. I’ll have to take another look at the case where there are multiple link instances being initialized at the same time.

skylarmb on May 18, 2021

Also experiencing this for production users using v3.0.0. We had previously had issues with the link declaring more than once, but that was solved in #109, not sure if that fix unintentionally caused this as well

alexandrasmith00 on Sep 11, 2020

I can confirm as well this is still happening. @ipam73 solution works for now as a workaround. It would be great when this is fixed within the lib.

ghost on Apr 28, 2021

This is happening to me as well. I have a use case where I need multiple link buttons on one page, and get this error every time on page load. I’m on version 3.1.0 using usePlaidLink hook.

Error loading Plaid null

For now, also using the workaround by adding <script src="https://cdn.plaid.com/link/v2/stable/link-initialize.js"> into my index.html

ipam73 on Apr 24, 2021

I am experiencing this as well. It is (somewhat) consistent to reproduce if you have multiple components using the usePlaidLink hook loading at the same time. I have a use case where I want to have one PlaidLink control on the page for the user to link new institutions, and another PlaidLink control on the same page that will open Plaid in update mode for an existing institution link. In this scenario, I can keep refreshing the page, and about 50% - 75% of the time I will encounter this error which prevents one of the two controls from working.

zsidnam on Aug 14, 2020