@user2015926 No, I have not found a solution yet. However, it's on our issue list and it's actually coming back up soon so I'll be actively trying to figure it out again this week. I will post back here if I find a solution.

They've got a docs.unity3d.com/ScriptReference/UIElements.ListView.html now.

Check out that platform-independence. Gotta wonder why they called it "Unity" sometimes.

Ok, I got it working, I changed android:name in the application element from com.companyname.glass.screen.UnityPlayerActivity to com.unity3d.player.UnityPlayerActivity. But I'm not going to attempt to post a self-answer because I have no idea why I had to do that or if that was the "proper" solution. Will accept any reasonable explanation of this. (I arrived at this conclusion by comparing the manifests from the APKs both with and without my custom manifest; I do not understand why Unity filled in an incorrect application class name with "Export" vs "Build and Run").

Re: Your edit: I deleted my custom manifest, changed it in Player Settings, re-exported the manifest, verified that it contained the new package name, then copied it back to my project and tried again. So yeah I can confirm I used a custom manifest with a matching package name after changing it.