[LG V35 Questions & Answers] cjbarth:
I just got the OTA update from AT&T for my V35 to Android 10. Now, whenever I try to Share from an app and the system Share panel is invoked, the Share panel starts to populate and then crashes and often takes the app with it. The only app that I can Share from now appears to be Firefox, but that doesn't appear to use the system Share but has its own.

Any ideas what could be going on? This is happening for my and my wife's phones (both V35). I contacted AT&T chat support and all they gave me was canned answers and then ended the chat; useless.

UPDATE 1: I found the problem with both phones is GroupMe. On the one phone I was able to get things working again by clearing the cache and data for GroupMe, uninstalling it, reinstalling it, and logging back in. For the other phone, this didn't work. I can Share when GroupMe isn't logged in, but once I log in, the Share crashes while populating. The only difference between the working phone and broken phone is that the working phone has a GroupMe account linked with Microsoft and the non-working phone has its GroupMe account linked with Google. So, it appears that a Google-account-GroupMe + Android 10 + Share is the broken combination. Now I'm really at a loss here.

UPDATE 2: Apparently I'm not the only one: https://www.reddit.com/r/AndroidQue...e_causing_android_system_share_menu_to_crash/

UPDATE 3: While GroupMe logged in with Microsoft was allowing Share to work on my phone for a while, Share has since stopped working while I'm logged into GroupMe. When I delete the data for GroupMe, I can share again. I've emailed GroupMe support about this matter and will report back. I'm currently running the latest version of GroupMe from the Play store: 5.47.4, released May 19, 2020

UPDATE 4: I've chatted with AT&T support a few more times. The first time was with Oliver, and that didn't go very well. I did manage to get a case number though. I was told that update V350AWM20i would be pushed to my phone in the next 24 hours which would fix the issue; I already have V350AWM30c, which is newer. I then spoke with Mike in a second chat session (which I started because Oliver hung up on me) and was told that my case has been escalated and I should at least hear back from AT&T in 24 hours. I'll keep updating this.

For sure GroupMe shouldn't be causing Android to crash, but Android shouldn't crash because of a bad app. IMO, both parties are at fault here.

UPDATE 5: I contacted AT&T today (they didn't contact me as they said they would) and they now say that I'll have a resolution by the 27th. GroupMe hasn't returned my request for support.

UPDATE 6: I contacted AT&T yesterday, the 26th, and they said that an update that would be pushed to my phone to fix the problem. They didn't know the version of the update that would be pushed. The update never came. Today, the 27th, I contacted AT&T again and they said that my case was closed and the the update was pushed. They said they pushed the latest version of Android Pie to my phone. So, here we go again. They decided they would re-open the case and would investigate my issue. For some reason they were under the impression that I opened a support ticket to get an update to Android 10. No one that I spoke with today could even tell me what my issue was, even after they read this post. I was transferred to another support agent where I sat for about an hour before quitting the chat. I only saw "Agent is typing..." and "Agent stopped typing" once, after about 45 minutes, but no actual interaction from the agent.

In other news, GroupMe has started replying to my request for support and apparently they can't open x265-encoded videos of a screen recording I took of the problem that they requested. I've sent them an x264-encoded screen recording to see where this goes.

UPDATE 7: I ended up calling AT&T support (866-344-6217) and spoke with a very helpful person who was able to correctly identify the problem and is escalating it to others, possibly LG, to see if the problem can be addressed. A remote control session was done with my phone where the problem was clearly reproduced. Such was the case even after clearing various cache and data for the app, web view, and system. I was informed that the problem will likely be solved by a hard reset of my phone. Apart from the obvious reason why I don't want to do that, the fact that this affects two of my phones the same indicates that it is an endemic software problem that should be addressed less this roll-out causes more problems for others. Since my phone has such a reliable reproduction and I need to schedule time to reset my phone, I'm holding off on doing this until I hear back about the escalations that AT&T is taking, which I'm expecting today, the 28th based on our conversation.

If anyone knows how to contact LG on this matter, or even AOSP, I'm all ears. It still should never be the case that a logged-in app should be able to crash the Share function in Android.

UPDATE 8: I just (8:49 am CST, May 28th) received a text message from AT&T saying that they were closing my "Urgent Case"; I was never called to inquire if my issue was resolved. Hopefully I'll still get the phone call I was promised later today.

UPDATE 9: I heard back from AT&T and they continue to work the issue. For reference, the model of my device is LM-V350AWM and it is SIM unlocked.

UPDATE 10: Microsoft GroupMe released an update to version 5.47.5 today which resolved the problem on my wife's phone. Thus, there are two solutions to this problem: 1) the comment below about turning off and on "Direct Share", and 2) installing the update for GroupMe. The reason why any installed app could cause the Android system to crash is still beyond me and hopefully is something that AT&T, Google, and LG can work out.