Stuck on loading screen at 45-46% (with solution for Android)

After freshly installing MInecraft and signing in with xbox live the game could not be loaded a second time as it gets stuck on the loading screen at 46%

The only way to get it working again was re-installing at which point you could sign into xbox live and play once but the next time you loaded the app it would stop at 46% again.

We connected the phone to a pc and had a look at adb logcat. After restarting the app several quick times in succession we noticed the following message was coming up quite consitentley

 

cat ~/s20logcat2 | grep -i webview
06-29 13:51:34.755 14682 15672 W lacrima : Failed to get webview version
06-29 13:51:34.755 14682 15672 W lacrima : android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
06-29 13:51:43.150 15624 16074 W lacrima : Failed to get webview version
06-29 13:51:43.150 15624 16074 W lacrima : android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
06-29 13:51:47.171 15875 16453 W lacrima : Failed to get webview version
06-29 13:51:47.171 15875 16453 W lacrima : android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
06-29 13:51:50.711 16249 16616 W lacrima : Failed to get webview version
06-29 13:51:50.711 16249 16616 W lacrima : android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
06-29 13:51:53.408 16574 16754 W lacrima : Failed to get webview version
06-29 13:51:53.408 16574 16754 W lacrima : android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview

So suspecting webview we cleared the data for the webview app and the issue still happened.

But when we then tried uninstalling the updates to the webview app (reverting it to factory version) Minecraft started loading.

Altough this could point to an issue with the latest webview version itself it is still very much  a bug on your end that causes your Minecraft app to hang instead of dealing with the invalid state gracefully. Perhaps may point to an incompatibility with the latest version that needs fixing your end.

Also, A quick google search shows others are getting stuck at 46% too not just us.

Full logcat available on request