Happened again on update to 8.1.0.17797 (97258331).
Happened again on update to 8.1.0.17893 (559d3f4d).
Happened again on update to 8.1.0.17967 (3dbad729).
Happened again on update to 8.1.1.10852 (bfeb41d4).
Happened again on update to 8.1.2.18120 (443b1c50).
Happened again on update to 8.1.2.18135 (cd28855c).
Happened again on update to 8.2.0.18187 (82fb7232).
Happened again on update to 8.2.0.18280 (9bcaf5ef).
It gets worseā¦ not only did it happen again on 8.2.0.18361 (which I could only verify by looking at the version in the Play Store and also in the Plex web app settings under āAuthorized Devicesā), but this version and the previous one crash almost immediately on startup. No amount of force stopping, clearing cache, or restarting the device make any difference. With the previous version at least, I noticed that how long before it crashed was variable, so it seems that some process/method thatās invoked shortly after others have completed seems to be the culprit. (With that previous version, 8.2.0.18280, I think that when I first updated to it, I was at least able to use the app enough to get to the device name settings before it crashed.)
For reference, 8.1.2.18135 needed to have its app cache data cleared to work correctly on the Pixel 4 XL.
The latest version, 8.2.0.18361, works just fine on both Pixel XL and Pixel Slate (and never required any cache clearing etc).
CC @jesusmc
Same problem with 8.2.0.18431 (with PMS 1.19.4.2902): device renaming and crashing. Luckily, I was able to rename back to āPixel 4 XLā on one of the first runs of 8.2.0.18431 before it crashed, but subsequent runs crash almost immediately (with the same variability I mentioned in a previous comment).
About to update PMS to 1.19.4.2935ā¦I wonder whether that will make a difference (though it seems doubtful to me).
No help on update of PMS (no surprise), and Android app 8.2.0.18481 also crashes on launch (even faster than previous versions). Plex Web confirms that the Pixel 4 XL was renamed to āIntel Apollo Lake Chromebookā again.
Sigh.
And again on update to 8.2.0.18495, both the crashing and renaming. Miraculously, I managed to rename it back to āPixel 4 XLā by being speedy before one of the crashes.
Same crashing and renaming on 8.2.0.18507 and 8.2.0.18572.
Perhaps relevant is that the background sync process seems to run just fine (no random crashes), and Plex Web reports that content syncs successfully to the device.
So Iām guessing that thereās something with the launching of the UI that triggers some fault.
And on 8.2.0.18603.
Okay, looks like 8.2.0.18617 (37ffc22e) doesnāt crash on startup anymore! Huzzah!
The device was already named āIntel Apollo Lake Chromebookā from a previous app update (that I couldnāt update before it would crash), so Iāll report whether my changing it back to āPixel 4 XLā this time sticksā¦
8.2.1.18636 (1cc6ce64) reset the name to āIntel Apollo Lake Chromebookā.
Props for sticking with this after MONTHS of no responses from Plex. Kinda wish I had a Pixel 4XL so I could add an āIām seeing this tooā comment, but alas, Iām not seeing this issue on my Pixel 2XL.
To be fair, @jesusmc did comment on March 18:
The team has identified the issue (a tricky one) and will work on it soon!
At this point, I think my continuing to post with every app version update is just gratuitous, but I donāt want the thread to automatically close, and I want to be able to mark a particular version as a solution, when the problem is fixed.
As a product manager myself, Iām imagining that itās not a very high priority, given how few people itās affecting. But Iām keen on sticking with it.
(It doesnāt happen on my Pixel Slate, Pixel XL, Pixel 2 XL, or Pixel 3 XL, eitherā¦and yes, Iām one of those enthusiasts who collects the highest-end Pixel devices every year and then doesnāt get rid of them!)
It is still impacting me, too. So, keep it up! 
My problem is that response was back in March. Weāre now nearing the end of June. Now Iām not a product manager, but I work in customer-facing IT for a large corporation and if I went three months without updating my users/customers, Iād be out of the job, no matter where that particular issue is in the priority stack. I dunno, I just keep noticing these issues/suggestions that apparently fall into this āsuch a low priority they donāt need a responseā category and itās frustrating to see.
