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 mobile browsers, the plaid link flow opens a second tab where the user authenticates and authorizes plaid to use their bank account. When the OS is low on memory, background tabs may have their state evicted and cause the web app's page to reload when the user finishes the pop-up link flow and reactivates the web app's tab. As a result, the link flow doesn't call the onSuccess callback.
We've tried storing the original link token in local storage, and on page refresh if there's a link token in local storage, we use it when calling usePlaidLink; however, there's still no call to onSuccess in this case.
Is there any mechanism for recovering the user's progress in the pop-up link flow if the web page that called usePlaidLink reloads during the pop-up link flow, so that they don't need to go through the flow again?
The text was updated successfully, but these errors were encountered:
In mobile browsers, the plaid link flow opens a second tab where the user authenticates and authorizes plaid to use their bank account. When the OS is low on memory, background tabs may have their state evicted and cause the web app's page to reload when the user finishes the pop-up link flow and reactivates the web app's tab. As a result, the link flow doesn't call the
onSuccess
callback.We've tried storing the original link token in local storage, and on page refresh if there's a link token in local storage, we use it when calling
usePlaidLink
; however, there's still no call toonSuccess
in this case.Is there any mechanism for recovering the user's progress in the pop-up link flow if the web page that called
usePlaidLink
reloads during the pop-up link flow, so that they don't need to go through the flow again?The text was updated successfully, but these errors were encountered: