rwuwon/android-webview-troubleshooting.txt

## android-webview-troubleshooting.txt
In short, the workaround that eventually sorted it for me was to create a second profile on my phone (with the same Google Account details) allowed Google Play within that to update WebView properly.

----

Background: I had just bought a refurbished Pixel 6a, a phone that was first released about 9 months ago (https://endoflife.date/pixel) and was in the process of setting it up and bringing the software up to date and found that WebView was the only thing that wouldn't update.

At first, I suspected that it was because the System Updates hadn't caught up (it requires multiple reboots, and will tend to pause after each reboot; so each time you need to go into system Settings and resume the update over there). But I got it up to May 2023 and WebView still didn't update via Google Play, despite also making sure Google Play had the latest updates (which can be done the confusing navigation of Settings > About phone > Android version > Google Play system update).

Still no dice. I also tried several other suggestions such as the ones listed at https://thedroidguy.com/android-system-webview-wont-update-1221798 and even tried disabling Developer Mode again. Nup.

What eventually worked was as outlined in the first line of this gist.

----

Speculation for what might have caused this: I basically upgraded from the original Google Pixel (first released in October 2016, although my unit was a refurbished warranty replacement from October 2018) and during the new phone setup, they ask you to connect both phones with a USB-C cable. Unfortunately, the cable that came with my original Pixel tends to have a dry connection on one end (usually I leave this at the charger end so it doesn't move around much and isn't a problem), so the initial setup might have been interrupted at one point which confused things. Who knows. In future, I might prefer to stick to device "cloning" via WiFi rather than cable because the other 'strange' thing is that the new device starts charging the old ones - which is fine since the new device is charged and has a much newer battery, but still, it feels dirty.
	In short, the workaround that eventually sorted it for me was to create a second profile on my phone (with the same Google Account details) allowed Google Play within that to update WebView properly.

	----

	Background: I had just bought a refurbished Pixel 6a, a phone that was first released about 9 months ago (https://endoflife.date/pixel) and was in the process of setting it up and bringing the software up to date and found that WebView was the only thing that wouldn't update.

	At first, I suspected that it was because the System Updates hadn't caught up (it requires multiple reboots, and will tend to pause after each reboot; so each time you need to go into system Settings and resume the update over there). But I got it up to May 2023 and WebView still didn't update via Google Play, despite also making sure Google Play had the latest updates (which can be done the confusing navigation of Settings > About phone > Android version > Google Play system update).

	Still no dice. I also tried several other suggestions such as the ones listed at https://thedroidguy.com/android-system-webview-wont-update-1221798 and even tried disabling Developer Mode again. Nup.

	What eventually worked was as outlined in the first line of this gist.

	----

	Speculation for what might have caused this: I basically upgraded from the original Google Pixel (first released in October 2016, although my unit was a refurbished warranty replacement from October 2018) and during the new phone setup, they ask you to connect both phones with a USB-C cable. Unfortunately, the cable that came with my original Pixel tends to have a dry connection on one end (usually I leave this at the charger end so it doesn't move around much and isn't a problem), so the initial setup might have been interrupted at one point which confused things. Who knows. In future, I might prefer to stick to device "cloning" via WiFi rather than cable because the other 'strange' thing is that the new device starts charging the old ones - which is fine since the new device is charged and has a much newer battery, but still, it feels dirty.