-
Notifications
You must be signed in to change notification settings - Fork 51
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
CONTINUE button is not showing #184
Comments
Thank you for reporting this! Looking into this issue now. I am curious, does this page scroll? |
Tapping on the area where the button should be showing is reacting and continuing. Does not look like it scrolls. 20210805_155807.mp4 |
Do you have night mode on? |
I asked the QA person who has the device. No, night mode is not on. |
Thank you, trying to repro this on our end now but it seems device-specific (have tried Pixel 3, 4, Samsung S21 so far) |
One idea occurred, I wonder if the black button is using |
We have a report of this same issue (real customer in the field) - notice that the Black "X" in the top corner is missing also. We are using Plaid 3.6.0 . Device is Samsung Galaxy S7 (SM-G930V) Is there a specific version of Plaid that made changes to how styles are used? i.e. is there a last known version that doesn't have this and the other visual issues people are reporting? |
Hi, our latest versions 3.6.0+ have the native beta experience which does not have this issue. If you would like to be opted in, please send your client_id to [email protected] |
The problem
Starting the link flow shows the screen detailing to the customer that they are going to use Plaid to link an account.
The black
CONTINUE
button is not showing.Environment
Font and display size configurations
Steps to Reproduce
Running the app on the emulator works nicely, but on the device the black CONTINUE button is not showing
Tapping on the are where the button should be showing, receives the tap and proceeds as if the user tapped on the button.
Expected Result
The button should be showing
The text was updated successfully, but these errors were encountered: