Livestream Plays but the Product Will Not Open: Troubleshooting WebView Domains and Mini Program Navigation
摘要： If a WebView livestream plays but products will not open, trace the click event, H5 domain, WeChat JS-SDK, Mini Program route and order attribution.
If video plays in a Mini Program WebView but a product will not open, trace the journey one stage at a time: click event, H5 page, WeChat environment, Mini Program route and product detail. A POLYV standard page, a company-owned H5 entry and a Web SDK room expose different levels of event control. Identify the current route before changing domain or navigation settings.
Trace product failures through click event, actual domain, WeChat context, Mini Program route and order attribution.
01 / First: prove that the click event fires
Attach one available test product to a test channel. Record channel ID, product ID, click time and current page URL. On a standard page, verify the current product destination setting. In a custom H5 room, check whether the product event reaches the company’s callback. If the event never fires, inspect channel product configuration and binding. If it fires but nothing opens, move to the WeChat environment.
02 / Second: follow every actual domain
Inspect the initial <web-view> URL, any redirected viewing-page URL and intermediary URL. Compare each with the business domains configured for the company’s AppID. If WeChat JS-SDK is involved, verify its security-domain and signed-URL setup. Do not check only the company home-page domain; an activity subdomain may be the page that actually handles the click. Retest in the target experience build after configuration changes.
03 / Third: validate the destination route
Check that the target product-detail page is registered in the current Mini Program package and that its path, product ID and campaign parameters match the H5 contract. Test both logged-in and logged-out members; a login detour should return to the same product. The back path should lead to the same live event rather than leaving users in nested WebViews. Record input and output parameters at each intermediary page.
04 / Fourth: check playback and order attribution
After product detail opens, verify whether video stops or enters the intended small window. POLYV’s background playback guide describes a native intermediary for WebView live viewing; returning to H5 must exit the background state cleanly. Place a test order and inspect member, product, channel and campaign source in the company’s order service. If navigation works but attribution is missing, inspect parameter passing and server linkage.
05 / Write a reproducible defect report
Include AppID environment, iOS or Android model, WeChat version, channel and product settings, full URL chain, click time, expected and actual routes and a screen recording. Assign the defect to channel configuration, H5 event binding, domain or JS-SDK setup, Mini Program routing or order attribution. After a fix, rerun the entire entry-to-order journey rather than clicking the product button once.
For a longer-term route with fewer H5-to-Mini-Program product transitions, evaluate POLYV’s native viewing-page SDK. An existing uni-app project can host its mp-weixin viewing component through wxcomponents; apps and H5 use their respective solutions from the developer center.
06 / Diagnose by symptom
Start with the same test product and collect evidence in sequence: event, domain, WeChat JS-SDK, Mini Program route and order. A symptom narrows the search; it does not identify a unique cause.
| Symptom | Capture next | Check first |
|---|---|---|
| Product card has no response | Product ID, channel setting, event log | Product not active or callback not bound |
| Click logs exist but WebView stays put | Current URL, redirects, business-domain list | Actual domain differs from configured domain |
| JS-SDK initialization/signature fails | Signed URL, init result, safe domain | Signed URL is stale after navigation |
| Navigation fires but detail does not open | Page path, parameters, login state | Mini Program route or login return |
| Detail opens but order lacks source | Campaign/member IDs and order record | Parameter transfer or server attribution |
After a fix, use new and returning members to complete live entry, product, canceled/completed payment and return. Check small-window audio and campaign source as well.
Frequently Asked Questions
Why does the product open in a mobile browser but fail in the Mini Program? The WebView also depends on WeChat business domains, JS-SDK context and Mini Program routing.
Is opening the product page enough to close the issue? Also verify member identity, order source, return navigation and playback state.
What belongs in the defect report? Include environment, complete URL chain, product and channel settings, device, time and screen recording.
Further Reading
Continue with Embedding a Livestream Room in a WeChat Mini Program WebView: Standard Page, Custom H5 and Web SDK and A WeChat Mini Program Livestream Launch Checklist: Shares, Product Routes, Analytics and Return Paths. For the overall integration choice, see the WeChat Mini Program SDK guide. The Chinese edition covers the same task for local teams.
About POLYV
POLYV standard H5, custom H5 and native rooms have different product-event and navigation responsibilities. Confirm the route first, then align it with the company’s router using the developer center.
