Sponsor-offer webview overlay opens with no content on certain offers after tapping "Claim"

[qazwsx521943]

Summary

On the sponsor-offer bottom sheet, tapping "Claim" on certain offers opens the webview overlay with no content — it shows a broken-image placeholder ("?") or "This offer is no longer available". Other offers render their content in the overlay correctly, so it appears to be specific to certain offers rather than the overlay mechanism itself.

Observed on SDK v1.4.55.

Steps to Reproduce

1. As a non-subscriber with sponsor offers enabled, open a subscription paywall and trigger the offer flow (tap the paywall CTA, then cancel the App Store purchase sheet).
2. Observe the sponsor-offer bottom sheet.
3. Scroll to one of these offers: "Paramount+" (Movies, shows & sports), "Agency Skincare", "Saily eSIM", "Nord VPN".
4. Tap "Claim" on that offer.

Actual: The webview overlay opens with no content — broken-image placeholder ("?") or "This offer is no longer available". Other offers display content correctly in the same overlay.

Expected: The webview overlay should display the sponsor-offer content for all offers.

Screenshot

[ryan-encorekit]

Thanks for flagging this, and for the detailed screenshots and recordings. They genuinely help us trace these.

We take the claim experience seriously, so we looked into each offer you shared. Based on our telemetry, these failures trace upstream to our partner networks rather than the SDK. In development the no-content screen shows up frequently because these affiliate networks enforce resilience measures like rate limiting, and we have also seen empty content for traffic on a VPN, which they can flag.

On our side, we have validated each of the offers you shared and confirmed they return content, we monitor offer health, and we can disable a specific offer or network when one misbehaves. We are also improving our detection so we catch a destination that loads but returns an error page.

To help us confirm, could you retry those offers without a VPN on a fresh development session, before running many claims in a row? If anything still fails, send it over and we will dig in.

For an end user in production, on a fresh IP and typically interacting with a single offer, the link redirects and the content renders, so we do not expect this to reach your users. We want it solid in your testing too, so let's keep this open and keep iterating.

Thanks again.