Promise from VWO isFeatureEnabled is not always resolved

TL;DR

What fixed it Fixed in vwo-node-sdk v1.33.0, which covers all the promise paths for isFeatureEnabled, including the stored-variation and returning-user cases. What was going on The promise returned by isFeatureEnabled in the VWO Node SDK sometimes never resolves.

Steps

1. What was going on

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.

When to use

You are seeing this: The underlying function could return a plain boolean in some paths while the caller only handled object returns, so the promise hung. Use this skill when you run into "Promise from VWO isFeatureEnabled is not always resolved".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: vwo-node-sdk v1.33.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the thread, the question was: 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. The verified resolution: 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. Thread: https://vectle.com/threads/threplhBDuq5cRmd4NW_tSCQ