Repro video in this link:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/916802/

Is there a work around for opening these apps? Can they be opened another way?

The same app can be opened from Playstore when searched for.

I see in logs crash loop and container is not started. that is why all icons are default and do not react.

tracked in b/120051351 

https://crash.corp.google.com/browse?q=EXISTS+%28SELECT+1+FROM+UNNEST%28CrashedStackTrace.StackFrame%29+WHERE+FunctionName%3D%27org.chromium.arc.applauncher.AppLauncherService.getAuthService%27%29#samplereports

3K+ crashes per day.

Is this specific to eve and nocturne only?

Adding changmar@, elijahtaylor@, khmel@ to comment.

Bumping this to ReleaseBlock-Beta as there is a work around for this for the users. Please let me know if we should truly block Dev for it.

Thanks

For any platform. majority is from reks_cheets, relm_cheets, kefka_cheets

eve + nocturne 0.34% + 0.03%

Few updates.
This problem is side problem that appears after ArcAppLauncher crash/restart due the different reason.
M71 is much stable than previous builds due stabilization work we did in general and initial phase of refactoring for auth layer.
M72+ has problems but we have time to address.

Besides the problems I found before I got one, that might be directly casuing the crash loop.

12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: [1220/162815.785584:FATAL:jni_android.cc(251)] java.lang.OutOfMemoryError: OOM allocating scaled Bitmap with dimensions 60480 x 60480
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.ImageDecoder.nDecodeBitmap(Native Method)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.ImageDecoder.decodeBitmapInternal(ImageDecoder.java:1607)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.ImageDecoder.decodeDrawableImpl(ImageDecoder.java:1687)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.ImageDecoder.decodeDrawable(ImageDecoder.java:1645)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.ResourcesImpl.decodeImageDrawable(ResourcesImpl.java:766)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.ResourcesImpl.loadDrawableForCookie(ResourcesImpl.java:839)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.ResourcesImpl.loadDrawable(ResourcesImpl.java:631)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.Resources.loadDrawable(Resources.java:902)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.TypedArray.getDrawableForDensity(TypedArray.java:955)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.AdaptiveIconDrawable.updateLayerFromTypedArray(AdaptiveIconDrawable.java:517)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.AdaptiveIconDrawable.inflateLayers(AdaptiveIconDrawable.java:481)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.AdaptiveIconDrawable.inflate(AdaptiveIconDrawable.java:230)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.DrawableInflater.inflateFromXmlForDensity(DrawableInflater.java:142)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.Drawable.createFromXmlInnerForDensity(Drawable.java:1332)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.graphics.drawable.Drawable.createFromXmlForDensity(Drawable.java:1291)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.ResourcesImpl.loadDrawableForCookie(ResourcesImpl.java:833)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.ResourcesImpl.loadDrawable(ResourcesImpl.java:631)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at android.content.res.Resources.getDrawableForDensity(Resources.java:893)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.arc.util.IconUtil.getIconData(IconUtil.java:94)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.arc.util.IconUtil.getIconDataAsPng(IconUtil.java:258)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.arc.util.IconUtil.getIconDataAsPng(IconUtil.java:208)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.arc.applauncher.AppLauncherService.requestAppIcon(AppLauncherService.java:1356)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.arc.mojom.AppInstance_Internal$Stub.acceptWithResponder(AppInstance_Internal.java:1113)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.RouterImpl.handleIncomingMessage(RouterImpl.java:225)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.RouterImpl.access$000(RouterImpl.java:21)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.RouterImpl$HandleIncomingMessageThunk.accept(RouterImpl.java:33)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.Connector.readAndDispatchMessage(Connector.java:215)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.Connector.readOutstandingMessages(Connector.java:172)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.Connector.onWatcherResult(Connector.java:152)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.Connector.access$100(Connector.java:25)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.bindings.Connector$WatcherCallback.onResult(Connector.java:142)
12-20 16:28:15.793  1000 22723 22739 F mojoprocesssupport: 	at org.chromium.mojo.system.impl.WatcherImpl.onHandleReady(WatcherImpl.java:53)

Situation is strange. First of all it never appeared on ToT branch.
And it only exists on M72 branch.
First time problem appeared on:
11316.6.0	72.0.3626.8	5164505
Last known good:
11316.5.0	72.0.3626.5	5162747

verified 11316.41.0

[Auto-generated comment by a script] We noticed that this issue is targeted for M-72; it appears the fix may have landed after branch point, meaning a merge might be required. The owner of this bug should confirm if a merge is required here. If so, add Merge-Request-72 label and indicate which commits/CLs are to be merged. Otherwise, remove Merge-TBD label. Thanks.

Verified on chrome OS 11316.66.0, 72.0.3626.49