I’m receiving feedback from users having multiple reports of experiencing this issue on latest-release branch (3.2.0.Beta2) on mobile. If we can help in any way to identify the issue, please let us know.
1 like