Apps crashing in Android 12

galaxy-A52 · ‎29-08-2022

App crashing only in Samsung devices after the android 12 updates. This is happening with Samsung devices only ( in other company devices it is working fine ). We are capturing logs while the app crashing.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

08-29 18:06:59.824 4801-4801/? A/DEBUG: Build fingerprint: 'samsung/a52qub/a52q:12/SP1A.210812.016/A525MUBS4BVE1:user/release-keys'

08-29 18:06:59.824 4801-4801/? A/DEBUG: Revision: '8'

08-29 18:06:59.824 4801-4801/? A/DEBUG: ABI: 'arm'

08-29 18:06:59.824 4801-4801/? A/DEBUG: Processor: '7'

08-29 18:06:59.824 4801-4801/? A/DEBUG: Timestamp: 2022-08-29 18:06:59.425646342+0530

08-29 18:06:59.824 4801-4801/? A/DEBUG: Process uptime: 4s

08-29 18:06:59.824 4801-4801/? A/DEBUG: Cmdline: com.xxxxxx.xxxxxbat

08-29 18:06:59.824 4801-4801/? A/DEBUG: pid: 4632, tid: 4758, name: Chrome_InProcRe >>> com.xxxxx.xxxxbat <<<

08-29 18:06:59.824 4801-4801/? A/DEBUG: uid: 10318

08-29 18:06:59.824 4801-4801/? A/DEBUG: signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xc3a71ba4

08-29 18:06:59.824 4801-4801/? A/DEBUG: r0 00000000 r1 bd053d50 r2 00000002 r3 00000000

08-29 18:06:59.824 4801-4801/? A/DEBUG: r4 bd0b0538 r5 00000000 r6 00000000 r7 00000000

08-29 18:06:59.824 4801-4801/? A/DEBUG: r8 00000000 r9 bd430430 r10 00000000 r11 bc37b9f8

08-29 18:06:59.824 4801-4801/? A/DEBUG: ip c4e49ac0 sp bd4301f8 lr c44164c3 pc c3a71ba4

08-29 18:06:59.824 4801-4801/? A/DEBUG: backtrace:

08-29 18:06:59.824 4801-4801/? A/DEBUG: #00 pc 010b1ba4 /data/app/~~9_-g-fPTMkwA3mcQ8bYcHg==/com.xxxxx.xxxxbat-vyH4Y9ShdtUMToa7dofzKg==/lib/arm/libxwalkcore.so (BuildId: fcaef3d1c86e8047c3ad9245008b8c54afb476b2)

08-29 18:06:59.853 683-683/? E/tombstoned: Tombstone written to: tombstone_20

08-29 18:06:59.938 1018-1018/? E/ClientCache: failed to get buffer, invalid process token

08-29 18:06:59.938 1018-1018/? E/ClientCache: failed to get buffer, invalid process token

08-29 18:06:59.939 1018-1018/? E/ClientCache: failed to get buffer, invalid process token

08-29 18:06:59.939 1018-1018/? E/BpTransactionCompletedListener: Failed to transact (-32)

08-29 18:06:59.940 1018-1018/? E/BpTransactionCompletedListener: Failed to transact (-32)

08-29 18:06:59.941 2653-2653/? E/libprocessgroup: set_timerslack_ns write failed: Operation not permitted

08-29 18:06:59.944 2089-19759/? E/TaskStackListenerAbstract: onTaskSnapshotChanged called by Binder.getCallingPid() 0 android.app.ITaskStackListener$Stub.onTransact:585 android.os.Binder.execTransactInternal:1220 android.os.Binder.execTransact:1179 <bottom of call stack>

08-29 18:06:59.945 3448-7616/? E/TaskStackListenerAbstract: onTaskSnapshotChanged called by Binder.getCallingPid() 0 android.app.ITaskStackListener$Stub.onTransact:585 android.os.Binder.execTransactInternal:1220 android.os.Binder.execTransact:1179 <bottom of call stack>

08-29 18:06:59.945 2089-855/? E/TaskStackListenerAbstract: onTaskSnapshotChanged called by Binder.getCallingPid() 0 android.app.ITaskStackListener$Stub.onTransact:585 android.os.Binder.execTransactInternal:1220 android.os.Binder.execTransact:1179 <bottom of call stack>

08-29 18:06:59.950 1018-1018/? E/BpTransactionCompletedListener: Failed to transact (-32)

08-29 18:06:59.968 3438-3438/? E/DMASA[D]: [DropBoxReceiverManager]enqueueFCwork: ProcessErrorStateInfo is null

08-29 18:07:00.004 2653-2653/? E/libprocessgroup: set_timerslack_ns write failed: Operation not permitted

PaulC59 · ‎29-08-2022

I've had frequent app crashes on my S22 Ultra mainly Microsoft office apps. The main issue for office apps crashing is no network so I think the unstable network connections both WiFi and mobile network are the main cause

Neo001 · ‎29-08-2022

Via Samsung Members app, contact Support and report the error.

Andy3 · ‎29-08-2022

Factory reset. Looks like token is corrupt.. looks like some code or files are corrupt and still trying to use previous codes

JAMES4578 · ‎29-08-2022

Hi @galaxy-A52 Have you tried clearing the cache partition to see if that makes a difference. Follow these steps:

1. Turn off the device.
2. Connect To Computer or plug in USB-C Headphones , Press and hold the Volume Up key and then press and hold the Power key .
3. When the Android logo displays, release all three keys.
4. An 'Installing system update' message will show for 30 - 60 seconds before the Android system recovery menu options appear.
5. Press the Volume down key several times to highlight wipe cache partition.
6. Press Power key to select.
7. Press the Volume down key to highlight yes, them and press the Power key to select.
8. When the wipe cache partition is complete, Reboot system now is highlighted.
9. Press the Power key to restart the device.

You may need to send an error report though for advice. a factory Reset would be the last resort but would need to ensure Data is backed up beforehand.

I do not work for Samsung or make Samsung Products but provide independent advice and valuable contributions.

galaxy-A52 · ‎30-08-2022

Hi Team,

I have tried but it is not working.

jlola · ‎22-09-2022

I had the same issues and had tried all strategies previously mentioned, and it ended up being related to the "Android System WebView" app for me. I first realized that it had pending updates in the playstore that I updated, then I:

1. Go to settings > apps> Android System WebView

2. I cleared the cache and data in the storage section, then force closed it, disabled, then re-enabled it then rebooted my phone

This fixed the issue for me after months of being unable to figure out what was going on. I'm not 100% sure whether it was just the updates needed, or if cleared cached/stored data of the app and rebooting it, or the combination of the two, but I figured I'd just explicitly mention my steps. The end result was no more crashing! Hope it's the same issue with you