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
A partner has reported that when viewing the Polaris date picker component in an Android webview, the buttons are missing. The Mobile Shopify app renders embedded apps in a webview, and this is where he observed the behaviour
Expected behavior
Actual behavior
Steps to reproduce the problem
Download any embedded app that uses the polaris date picker. I used this one, but tested on others as well. If you use this app, be sure to pick the standard pricing plan
Open the test store in the Mobile Shopify app for Android, navigate to the apps page, and launch the newly installed app.
For the Theme Scientist app, tap "Theme A/B" testing, then tap the "Start Day" field to bring up the date picker
You should see that the date picker is missing the 3 buttons at the bottom
Specifications
Sorry this is my first issue in this repo, I didn't get the polaris version or react information when I was in contact with the merchant. Please let me know if I should get in contact again and get it, since the issue is replicable in other apps I'll hold off for now.
Are you using the React components? (Y/N):
Polaris version number:
Browser: Android Webview (within Mobile Shopify app)
Device: Google Pixel 3
Operating System: Android 10
The text was updated successfully, but these errors were encountered:
Issue summary
A partner has reported that when viewing the Polaris date picker component in an Android webview, the buttons are missing. The Mobile Shopify app renders embedded apps in a webview, and this is where he observed the behaviour
Expected behavior
Actual behavior
Steps to reproduce the problem
standard
pricing planSpecifications
Sorry this is my first issue in this repo, I didn't get the polaris version or react information when I was in contact with the merchant. Please let me know if I should get in contact again and get it, since the issue is replicable in other apps I'll hold off for now.
The text was updated successfully, but these errors were encountered: