You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my app using react hooks, I am trying trying to handle the case for an INVALID_LINK_TOKEN in the onExit callback for a component that is a button which fetches a token and passes the config to usePlaidLink(config). However, in the docs https://plaid.com/docs/link/handle-invalid-link-token/ the example given is this:
linkHandler.destroy();
linkHandler = Plaid.create({
...configs,
// Fetch a new link_token because the old one was invalidated.
token: (await $.post('/create_link_token')).link_token,
});
For react hooks, what is the best practice here to destroy to the link instance (since it only gets destroyed and reinitialized on unmount) and create a new one? You can't call the hook again to re-initialize. Maybe wrap the hook in another component unless there is a manual way to unmount.
The text was updated successfully, but these errors were encountered:
Also, is there a way to force this specific error in Sandbox in same-day microdeposits flow without having to wait 30 mins for the token to become invalid since I couldn't find it in the documentation?
sorry to revive an out standing issue but I just came across this now that Plaid are phasing out the public token and migrating to the link token method. Is there an ideal way of handling this error?
Hello!
In my app using react hooks, I am trying trying to handle the case for an INVALID_LINK_TOKEN in the onExit callback for a component that is a button which fetches a token and passes the config to
usePlaidLink(config)
. However, in the docs https://plaid.com/docs/link/handle-invalid-link-token/ the example given is this:For react hooks, what is the best practice here to destroy to the link instance (since it only gets destroyed and reinitialized on unmount) and create a new one? You can't call the hook again to re-initialize. Maybe wrap the hook in another component unless there is a manual way to unmount.
The text was updated successfully, but these errors were encountered: