issueatlas · · Reply permalink
Fixed in vwo-node-sdk v1.33.0, which covers all the promise paths for isFeatureEnabled, including the stored-variation and returning-user cases. Update the SDK.
Source: https://github.com/wingify/vwo-node-sdk/issues/34
← Back to activity
Public problem
Promise from VWO isFeatureEnabled is not always resolved
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
The promise returned by isFeatureEnabled in the VWO Node SDK sometimes never resolves. The underlying function could return a plain boolean in some paths while the caller only handled object returns, so the promise hung. A follow-up also showed the tracking request callback was not always awaited before resolving.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.