catalinmiron / react-native-plaid-link Goto Github PK

I'm able to see the Plaid Link view and go into the flow but once I launch a bank's login view and start typing a username, the page immediately exits and shows "AccessDeniedAccess"

Just in case anyone is having this issue or if WebView is not loading correctly, Products takes an array of strings if you are trying to retrieve more than 1 product. I'm not sure if this is new or not but it is not specified in the documentation. Just a heads up! :)

If you select Reset Password after you select your bank the web view thows:

Has anyone figured out how to access the close button (the X in the top right) programmatically within the webview?

I'd like to hook up the Android back button to call this close button. This is to handle the case where the user is on the connected page, after linking their account, but instead of hitting X or Continue, they hit back. As the user has connected their account, the application needs access to the metadata of the successfully linked account. This data is only provided if the user hits X or Continue. If the user closes using the back button, the app never receives this data.

Hi,
I noticed that Plaid Link by default has fade transitions between pages (when you press continue from Home to choose bank). I noticed that this port does not have those transitions.

1. Is this an issue only I'm having?
2. Is there any way for me to fix it?

On README we have an example of the data object we should expect to be returned.
But after connecting successfully, this is the object I get:

{
  action: "plaid_link-undefined::event"
  eventName: "TRANSITION_VIEW"
  metadata: {
    error_code: null
    error_message: null
    error_type: null
    exit_status: null
    institution_id: "ins_4"
    institution_name: "Wells Fargo"
    institution_search_query: null
    link_session_id: MY_LINK_SESSION_ID
    mfa_type: null
    request_id: MY_REQUEST_ID
    timestamp: "2019-11-05T16:43:20.186Z"
    view_name: "CONNECTED"
  }
}

The action plaid_link-undefined::connected never appears. So I'm not able to get some important info such as public_token to move on with the user authentication.

I'm using RN 0.61.2 and this is my component instance:

<PlaidAuthenticator
      onMessage={data => console.log('PLAID MESSAGE', data)}
      publicKey={PLAID_PUBLIC_KEY}
      env={PLAID_ENVIRONMENT}
      product="auth,transactions"
      clientName="Client"
      selectAccount={false}
    />

Has anyone experienced the same issue?

When I close plaid from the x icon it shows only a blank white screen.I have to press for example in my app a tab menu to go to a screen.Isn't there a way to specify what happens when you close plaid ?

Hi,

I'm facing issue as apple will stop accepting submissions of apps that use uiwebview apis in react native. This is due to in react-native-plaid-link used the react-native-webview package. upto version <7.0.1 the react-native-webview used the UIWebView. Now this UIWebView is deprecated and version >=7.0.1 used WKWebView instead UIWebView. But in react-native-plaid-link uses the 5.3.0 version of react-native-webview. Could you please update the react-native-webview version to >=7.0.1

So things have been working great for me but all of a sudden, when trying to use development environment i now get this error and i can't figure out if it's an issue on the API's end or on my end?

When i press continue after completing process , it shows white screen with no data

Now that plaid has release an "oficial" way to use plaid link (https://github.com/plaid/react-native-plaid-link-sdk).

What are the plans for this library? Should we start using the oficial one? I'll keep using this one as long as there is support or at least it is proven that the oficial one is stable.
Thoughts?

Hi @catalinmiron,
I'm using your library and I'm receiving the same data if the user presses either close or continue, after the login is complete.
Is there a way to distinguish those two events?

Thanks for your work!

Hello @catalinmiron ,

In our project we are using react-native-plaid-link and recently we received an email from Plaid saying the following:

As we approach June 30, we wanted to ensure that your Plaid Link implementation is configured to support OAuth. If you're using Plaid Link in a WebView or using our native iOS SDK, some Plaid Link implementation changes are needed to best support the OAuth redirect flow in mobile experiences.

My question is - Is it planned to implement the OAuth redirect flow support and if not - will react-native-plaid-link continue to work if the bank requires OAuth?

response metadata is missing account_id

using the test credentials: user_good / pass_good

Is this due to me using sandbox and the test credentials?

This only happens on Android (not iOS). Does anyone know if there's an immediate fix for this?

Is it possible to integrate password managers in the webview?

It looks like it's possible with the native integration for Plaid Link.

When going through the bank select flow, getting a "Possible Unhandled Promise Rejection: Error: Unable to open URL: plaidlink://connected? ... "

Furthermore, I'm not receiving any data from the onMessage callback -- it keeps giving me

Object {
  "action": "plaid_link-undefined::resize",
  "height": "",
}

Any thoughts on why no data is being returned or logged to my console @catalinmiron ?

Hi,

I am getting "accessDenied" with some long Id after it, on on a blank screen when I try to use Plaid example:

<PlaidAuthenticator onMessage={this.onMessage} publicKey={plaidConfig.publicKey} env={plaidConfig.env} product={plaidConfig.products} clientName="Emma app" />

For a second I can see some other screen with two checkboxes, and message saying something like: "Emma app wants to... ", but I am instantly redirected to "AccessDenied'.

I am testing in sandbox mode.

Not sure if anybody face this problem. I used IPhone XS Max to implement the link flow on development environment. however, the Recaptcha is blocked by window width. I think this is not the problem of this library, but I still want to ask if anybody has solution to deal with this problem. Thanks!

Issue

selectAccount parameter in PlaidAuthentication component is implemented but not documented

Solution

Include selectAccount parameter in the README documentation / example so developers can find out it existence without the need to review the source code

Pull Request: #18

When the WebView loads, it throws the error:

SyntaxError: JSON Parse error: Unexpected identifier "setImmediate$0"
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError
at node_modules/expo-error-recovery/build/ErrorRecovery.fx.js:9:32 in ErrorUtils.setGlobalHandler$argument_0
at [native code]:null in flushedQueue
at [native code]:null in invokeCallbackAndReturnFlushedQueue

It seems like the error is cause because the plaid link page is running window.postMessage with a string containing setImmediate$0 which is then passed to JSON.parse(e.nativeEvent.data), and since it is not valid JSON, it throws the error.

How do I retrieve account and routing numbers? Right, now I am only receiving:
id, name, subtype, and type

I need to retrieve the account and routing numbers

Hi there - great project, thank you!!

Curious if you have any plans to support Link's updated mode?

https://plaid.com/docs/quickstart/#use-link-to-resolve-error

How to recreate:

Click 'Plaid End User Privacy Policy' above Continue button
Click 'Learn more above plaid' under second Continue button

Scroll to bottom and Click 'See what data is being shared'

App will sometimes crash with an Unexpected token s in JSON at position 0.

From Line 86:

this.props.onMessage(JSON.parse(e.nativeEvent.data));

Seems like this is triggering onMessage with invalid data.

After linking a bank or closing the webview it takes a lot of time to return to the view from status state EXIT. What may be the issue ? Also there is a difference on simulator and real phone when testing this.