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
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
micahalcorn opened this issue
Jan 9, 2020
· 5 comments
Labels
bugSomething isn't working as intendedduplicateThis issue or pull request already existsmobileP1Large amount of significant user impact, a meaningful feature is brokenui/ux
Many users are reporting that the webview never loads after native onboarding. It is a white screen with an endless spinner. All of the reports that I have seen involve Android devices, but there's a slim chance that this is only due to the fact that the vast majority of our usage is coming from Android. The IP addresses that I have tried to match in Sentry reveal no errors at all. @tomlinton theorized that this could be caused by #2344. I've confirmed that many of the users are on Android 6, but at least a couple of people claim to be on Android 7.
@tomlinton how confident are we about that? I couldn't prove that it was happening on 7️⃣ but received more than one report indicating that it might be happening there too. Would it affect both?
Yea the Android version isn't the important bit, it's the version of WebView that shipped with those Android releases. I can't find a list of the versions anywhere but I'm confident it is the same thing.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't working as intendedduplicateThis issue or pull request already existsmobileP1Large amount of significant user impact, a meaningful feature is brokenui/ux
Many users are reporting that the webview never loads after native onboarding. It is a white screen with an endless spinner. All of the reports that I have seen involve Android devices, but there's a slim chance that this is only due to the fact that the vast majority of our usage is coming from Android. The IP addresses that I have tried to match in Sentry reveal no errors at all. @tomlinton theorized that this could be caused by #2344. I've confirmed that many of the users are on Android 6, but at least a couple of people claim to be on Android 7.
⚪️
At Origin, we use ZenHub to manage our engineering tasks and product development. Download their browser extension and check out our open workspace at github.com/originprotocol/origin#zenhub.
The text was updated successfully, but these errors were encountered: