Whatsapp Crash in Work and User Profiles

jarelllama

unexpired_spoilage Have you tried WhatsApp on a profile with Google Play Store and Google Play Services installed? When I had the same problem as you, the only difference between my setup now and then is the absence of Google Play.

unexpired_spoilage

Oh yeah, I did that as well before the factory reset. Tried both in the work profile and in a separate user profile. Still crashed with the same crash report.

UnknownProperty

Have you tied installing apk file instead from google services? I don't personally use this service at all due to their data collection and privacy violation they pull. I recommend you just use Signal app instead. It works fine on Android 13 without a problem. I did have internet problems with Android 13 lately but got that all fixed.

Edward Snowden recommends it.

unexpired_spoilage

UnknownProperty You mean the Whatsapp APK from the Play Store? I had that one installed initially from the Aurora Store, and it is the one that started with the crashes. Since then, I've tried the Website version... which still crashes. :/
And, I do use Signal! :D It's just that not everyone is on board, so I'm using Whatsapp for specific contacts. Though, I don't have much trust for Whatsapp - hence why I'd like to have it in a separate profile.

MetropleX Ahhhh, alright. Thanks for the explanation! I'm using the latest version listed on the Whatsapp website (at least, the latest version as of a few days ago... I didn't write down the version number when I downloaded it). The website lists the latest version number as 2.22.20.80, so I imagine mine is just a few days behind that one. If it's the case that they're using an outdated interface, then I imagine there's not much I can do on my end? It's odd though, as when I asked this question in the Matrix room, it seemed that others were able to run it just fine in secondary profiles. Could this be device specific? Pixel 4 vs Pixel 5, for example?

MetropleX

My laymans eye leads me to ask how old is the version of Whatsapp that you are using? Calling identity is not authorized relates to the id calling an API, not the phone permission.

com.android.server.devicepolicy.DevicePolicyManagerService.getProfileOwnerAsUser is apparently an outdated and restricted non-SDK interface that was restricted starting with Android12 for apps targeting Android 12 and later. This app may have worked in Android 12 when targeting Android 11 but likely became further restricted in Android13.

Let me know and I will get a more authoritative answer and retract this as required.

Hulk

unexpired_spoilage
Please try downloading WhatsApp from Google Play Store.

Also, we don't recommend using work profiles, please use proper user profiles instead.

unexpired_spoilage

Hulk Ahhh, thanks! So, to clarify, do you recommend installing GSF and Play Services as well? Otherwise, wouldn't running the Google Play version be similar to running the website version or the Aurora store version?

juicer

Hulk Also, we don't recommend using work profiles

Why? No mention of work profiles being worse than user profiles on the website.

MetropleX

unexpired_spoilage the Aurora version IS the Google Play Version, Aurora is just an anonymous front end for accessing Google Play Store.

Even though I separate them out to explain that, ALL Whatsapp sources you mention provide the exact same version as each source can be used to update the other.

unexpired_spoilage

MetropleX That's what I thought, thanks! Then that leads me back to the question, could the crash be an issue with Whatsapp, or is it an issue with the OS/device? I'm under the impression Whatsapp works fine for others who use it in a work or separate user profile.

flamepygmy

unexpired_spoilage did you ever find a solution to this? Just got a Pixel 7 and installed the experimental version. I'm totally aware that it's experimental, but I'm having this exact same issue. I have WhatsApp (latest) on my user profile (not the owner profile), sandboxed Google Play services installed etc.

I've seen some other users posting similar issues on Android 13 (not GrapheneOS) on other Facebook related apps. I suspect this is something that FB/WhatsApp would have to fix.

unexpired_spoilage

flamepygmy I did not, unfortunately. And, yeah, I believe that the verdict was that it's an issue on FB/Whatsapp's side, as you said. I ended up installing WA on my main profile, but denied it contact permissions.

It is curious as to how the issue only seems to affect a minority of users. Must be a pretty specific setup that causes the crash?

Graphenely

unexpired_spoilage I have the same issue on a Pixel 6. I've been trying different options for days trying to get it sorted without success and then I found your thread. Thanks for the info. Can you please let me know how WhatsApp behaves in your owner profile with no GSF? Do you still receive notifications for new messages and phone calls or do you have to open the app manually to see new messages and missed calls?

Graphenely

unexpired_spoilage Nevermind, I gave it a go and it seems to work.

unexpired_spoilage

Graphenely Of course! WhatsApp has been working just fine in the owner profile without GSF. No need to open the app in order to see any new messages/calls. :)

Hulk

juicer

We don't encourage using work profiles because they are not meant for personal usage and have major caveats. Work profiles are for Bring Your Own Device enterprise deployments. Work profiles don't provide the same level of isolation as user profiles and are meant for a specific use case where a company owns a profile on a user's own device and manages it via a device policy manager app.

Hope this clarifies things

Implode8401

I'm having this issue in the main profile, any ideas how fix?