Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

noLoadingState parameter does not work on iOS #136

Open
luisforditch opened this issue Oct 3, 2024 · 2 comments
Open

noLoadingState parameter does not work on iOS #136

luisforditch opened this issue Oct 3, 2024 · 2 comments
Labels
comeback An issue to revisit later

Comments

@luisforditch
Copy link

Hey Guys, First of all, thank you for the amazing package. We're having an issue where the noLoadingState parameter of the LinkTokenConfiguration class, does not work. Meaning, even when the parameter is set to true, it will still load.

Here's how we're using it:

PlaidLink.open( configuration: LinkTokenConfiguration( noLoadingState: true, token: linkToken, ));

And here's the result of opening Plaid Link, it still shows the low opacity loading screen and sends our UI backwards. It's not the experience we want to give our users, and it feels a little too clunky for our liking, it also creates overlap with our internal loading indicator.

Simulator Screenshot - iPhone 15 Pro - 2024-10-03 at 10 04 22

Anyone had any luck fixing this?

@dtroupe-plaid
Copy link
Contributor

Thanks for bringing this up, and we appreciate the kind words about the package! 🙏

Just to clarify, this issue is related to the iOS SDK, not the Flutter SDK itself. We know that the noLoadingState parameter not working as expected can impact your user experience, and we’re actively looking into what needs to be done to fix it.

Right now, I can’t give an exact timeline for when this might be resolved, but it’s definitely on our radar. Once we’ve addressed it, we’ll make sure to update the Flutter SDK with the necessary changes and follow up here with more information (or submit a PR to update the iOS SDK version).

In the meantime, there are a couple of workarounds you might consider:

  • Call create at least 3–5 seconds before you expect the user to open Plaid. This can help preload the session and greatly reduce the chance of users seeing the loading spinner when Plaid is opened. Make sure to still set noLoadingState to true.

  • Alternatively, you can stick with the SDK’s default loading indicators for now, even though I know it’s not ideal.

We’re sorry for the inconvenience and appreciate your understanding as we work through this.

@luisforditch
Copy link
Author

Gotcha. Thanks for the pointers. Didn't know about create. And yes, please keep us posted on where this falls on the priority roadmap and how me and my team can help push this forward.

@jorgefspereira jorgefspereira added the comeback An issue to revisit later label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comeback An issue to revisit later
Projects
None yet
Development

No branches or pull requests

3 participants