Fatal In-App Popup Exception

[nseidman-play2pay]

✍️ Issue Description

FATAL EXCEPTION: main (Fix with AI)
Process: com.adfone.aditup.staging, PID: 30511
android.util.AndroidRuntimeException: java.lang.reflect.InvocationTargetException
at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:382)
at android.webkit.WebView.getFactory(WebView.java:2599)
at android.webkit.WebView.ensureProviderCreated(WebView.java:2593)
at android.webkit.WebView.setOverScrollMode(WebView.java:2661)
at android.view.View.(View.java:5664)
at android.view.View.(View.java:5843)
at android.view.ViewGroup.(ViewGroup.java:713)
at android.widget.AbsoluteLayout.(AbsoluteLayout.java:59)
at android.webkit.WebView.(WebView.java:426)
at android.webkit.WebView.(WebView.java:368)
at android.webkit.WebView.(WebView.java:350)
at android.webkit.WebView.(WebView.java:337)
at android.webkit.WebView.(WebView.java:327)
at com.iterable.iterableapi.IterableWebView.(IterableWebView.java:15)
at com.iterable.iterableapi.IterableInAppFragmentHTMLNotification.onCreateView(IterableInAppFragmentHTMLNotification.java:203)
at androidx.fragment.app.Fragment.performCreateView(Fragment.java:3119)
at androidx.fragment.app.DialogFragment.performCreateView(DialogFragment.java:770)
at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:577)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:286)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2214)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2115)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:2052)
at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:703)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)

📋 Steps to Reproduce

1. https://app.iterable.com/campaigns/17551245?view=Edit&templateEditor=open
2. Send to device
3. App crashes

---

👤 Iterable orgId: play2pay

📦 Iterable SDK version: 3.6.5, 3.6.6

📲 Android OS version: 13

[franco-zalamena-iterable]

Hi, thanks for the report. We've traced the stack trace and it matches SDK version 3.6.5, where the WebView was created without any error handling. In SDK 3.6.6, we added a safeguard (PR #999) that wraps the WebView creation in a try-catch. The AndroidRuntimeException you're seeing is a subclass of RuntimeException, which our guard now catches - instead of crashing, the in-app message is gracefully dismissed. This crash is caused by the device's WebView provider (Chrome or Android System WebView) being in a bad state (updating, disabled, or corrupted), which is an Android platform issue rather than something the SDK triggers.
Could you confirm whether you're still seeing this crash on 3.6.6? If the crash log was captured while running 3.6.5, upgrading to 3.6.6 should resolve it.

[nseidman-play2pay]

While the try catch is appreciated, we likely won't be able to use the feature in production given the unreliability of Android WebView on many devices. Thank you for the feedback, I will check stability on 3.6.6 later this week and follow up asap with regard to the Github bug report. Best, Noah

…

On Mon, Apr 6, 2026 at 5:02 AM Franco Zalamena ***@***.***> wrote: *franco-zalamena-iterable* left a comment (Iterable/iterable-android-sdk#1013) <#1013 (comment)> Hi, thanks for the report. We've traced the stack trace and it matches SDK version 3.6.5, where the WebView was created without any error handling. In SDK 3.6.6, we added a safeguard (PR #999 <#999>) that wraps the WebView creation in a try-catch. The AndroidRuntimeException you're seeing is a subclass of RuntimeException, which our guard now catches - instead of crashing, the in-app message is gracefully dismissed. This crash is caused by the device's WebView provider (Chrome or Android System WebView) being in a bad state (updating, disabled, or corrupted), which is an Android platform issue rather than something the SDK triggers. Could you confirm whether you're still seeing this crash on 3.6.6? If the crash log was captured while running 3.6.5, upgrading to 3.6.6 should resolve it. — Reply to this email directly, view it on GitHub <#1013 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYGLLGYU4J6KBDBP5SVYY7L4UNXBRAVCNFSM6AAAAACXL3FK2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJRGI4DEMBYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[franco-zalamena-iterable]

Do you have any updates from your side?

[nseidman-play2pay]

Unfortunately my test device still crashes intermittently with a generic webview exception that no longer traces to Iterable sdk code. It would be great to see a non webview implementation that inflates native view components like embedded messages are built to do. I'll close this ticket, as I don't think there's a solution to webview exceptions internal to android sdk components and libraries. Best, Noah

…

On Thu, Apr 16, 2026, 8:04 AM Franco Zalamena ***@***.***> wrote: *franco-zalamena-iterable* left a comment (Iterable/iterable-android-sdk#1013) <#1013 (comment)> Do you have any updates from your side? — Reply to this email directly, view it on GitHub <#1013 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYGLLG5ZIWXNYGPU63Y4JQL4WDD3PAVCNFSM6AAAAACXL3FK2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENJZHEYDGNBRGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>