CustomActionHandler nor UrlHandler callbacks are getting called in In-App messages

[saintjab]

✍️ Issue Description

We had some custom actions attached to our In-App Messages buttons/images which used to work fine. I am not sure when it stopped getting called but just recently the complex ones are not longer hitting neither our custom IterableUrlHandler nor custom IterableCustomActionHandler callbacks.

📋 Steps to Reproduce

1. Create an In-App Message template with button which has a url using the "Open Web page" action to something like myaction://GOTO_INAPP_BROWSER::https://www.bbc.co.uk/sport/boxing/articles/c1eq4g8w8gyo. I already have set "myaction" as one of the an allowedProtocols when initialising IterableAPI
2. Open the In-App Message from above that has been sent and tap the image/button with the url above
3. Either IterableUrlHandler or IterableCustomActionHandler implementation class should get called

---

I have logs inside both my custom IterableUrlHandler and IterableCustomActionHandler callbacks so should print if any was called. Instead, none get called but the default browser on device get launched with default/blank page showing

What works:
The simple url like myaction://GOTO_INAPP_BROWSER is working but not a complex one like above although it used to work. Aside the potential Iterable version bump, I have not made any changes to Iterable implementation in the app. Also I believe In-App Message used to have "Custom Action" tab for buttons/images like the Push notifications but just not 100% sure there have been changes there.

📦 Iterable SDK version: 3.6.5. Also tried the 3.7.0

📲 Android OS version: All versions we support from Android SDK 28

[franco-zalamena-iterable]

Hi @saintjab, a few clarifications to narrow this down:

Which handler is expected to fire:
For In-App clicks, the SDK only routes to IterableCustomActionHandler when the scheme is action://, itbl://, or iterable://. Any other scheme (including your whitelisted myaction://) goes through IterableUrlHandler. So for this URL, only IterableUrlHandler is expected - IterableCustomActionHandler not firing is by design.

Likely cause of the complex-URL failure:
The SDK code path is identical for both URLs, so the regression is almost certainly at the WebView layer: the double :// in myaction://GOTO_INAPP_BROWSER::https://... gets normalized/percent-encoded (or skipped) by Chromium before reaching shouldOverrideUrlLoading, which is why the browser ends up launching instead.

Recommended URL shape:
Put the target in a query parameter so there's only one ://:
myaction://GOTO_INAPP_BROWSER?target=https%3A%2F%2Fwww.bbc.co.uk%2Fsport%2Fboxing%2Farticles%2Fc1eq4g8w8gyo
Then in your handler: uri.getQueryParameter("target"). This should make IterableUrlHandler fire reliably on 3.6.5 / 3.7.0.

To confirm on our side, could you share:

• A logcat while tapping the failing link (filter on IterableInAppManager / IterableWebViewClient) - we mainly need the exact URL string reaching onUrlClicked.
• Your IterableUrlHandler.handleIterableURL first log line (is it unconditional, or gated on a startsWith check?).
• Android WebView / Chrome version on the device.