Alright then. First post on DEV and it's kind of a cry for help. Can anyone help me pick apart this SO question? It seems that we (and others) have instances where a dependency on Chrome for web views (mostly from 3rd party plugins) cause the app to be killed when Chrome updates. Yet I can find next to nothing about this process or how to potentially mitagate it. Can anyone help?
Updated Post
The Problem
We have various logs indicating that a background update to Chrome is killing our app, which uses webviews. The logs all follow a similar pattern;
3034 3049 I ActivityManager: Force stopping com.android.chrome appid=10115 user=-1: installPackageLI
3034 3049 I ActivityManager: Killing 963:com.google.android.googlequicksearchbox:search/u0a80 (adj 500): stop com.android.chrome,installPackageLI
3034
โฆ
Top comments (0)