Ravi

It is hard to reproduce issue. Need to monitor and investigate further. Most likely suspect is a [null pointer dereference](https://source.android.com/devices/tech/debug/native-crash). Possibly in [parsing](https://stackoverflow.com/questions/54999797/signal-11-sigsegv-code-1-segv-maperr-crash-only-on-some-devices) a Gson [somewhere](https://stackoverflow.com/questions/47836896/signal-11-sigsegv-code-1-segv-maperr-fault-addr-0x7f4485ff1820/47923830#47923830) using Java classes

More details https://sentry.io/organizations/a8c/issues/2462989315/?project=1438088 Suspect seems to be ReaderPostPagerActivity and potentially pager adapter Useful info for debugging https://medium.com/shopback-tech-blog/handle-transactiontoolargeexception-237961bd5ef8

a related issue https://github.com/wordpress-mobile/WordPress-iOS/issues/18988

I'm unable to reproduce this on Pixel 4a - Android 13 - WPAndroid v20.8 Given the issue is not consistent and seems to be device dependent. I'm going to reduce...

The issue seems to have cropped up [after this change](https://github.com/wordpress-mobile/WordPress-Android/pull/15034) This is working alright when tapping on the widget header but not on the content. Mystery needs to be resolved!

I'm not able to reproduce this. I'm going to close this for now. It can always be opened if there are new instances found.

Please see for more details on this issue https://github.com/wordpress-mobile/WordPress-Android/issues/10653

This line `shouldHandleFluxCSitePluginEvent(PluginDetailActivity.java:1163)`, is actually 1169

There's a [new PR for this work ](https://github.com/wordpress-mobile/WordPress-Android/pull/17638)

This opens up in a WebView, not something to fix in the app. See also #10653, and https://github.com/wordpress-mobile/gutenberg-mobile/issues/1387