openclaw - 💡(How to fix) Fix Bug: Feishu plugin fails with 'Cannot destructure property tenant_access_token' [1 comments, 2 participants]

Feishu plugin fails to initialize with error: this.logger.error(e); // BUG: catches error but does NOT re-throw When the HTTP POST fails, the .catch() only logs the error but does not re-throw, so the function returns undefined. The code then tries to destructure tenant_access_token from undefined, causing the error. The real HTTP error is silently swallowed and hidden.

• Expected: If token API fails, an error should be thrown with the actual cause
• Actual: Error is caught and swallowed, then a confusing destructuring error appears

TL;DR

The Feishu plugin initialization error is likely due to a bug in the @larksuiteoapi/node-sdk where an HTTP POST error is caught but not re-thrown, causing a destructuring error.

Guidance

• The issue is caused by the getCustomTenantAccessToken() method in the @larksuiteoapi/node-sdk not re-throwing the error when the HTTP POST fails, resulting in undefined being returned and causing a destructuring error.
• To verify the issue, check the logs for any errors related to the HTTP POST request to https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal.
• The bug can be mitigated by patching the SDK code to re-throw the error in the catch block, or by waiting for an upstream SDK fix and updating the bundled SDK version.
• Check the OpenClaw version and Feishu SDK version to ensure they are compatible and up-to-date.

Example

const { tenant_access_token, expire } = yield this.httpInstance
    .post(`${this.domain}/open-apis/auth/v3/tenant_access_token/internal`, {
        app_id: this.appId,
        app_secret: this.appSecret,
    })
    .catch((e) => {
        this.logger.error(e);
        throw e; // re-throw the error
    });

Notes

The issue is specific to the @larksuiteoapi/node-sdk version 1.60.0 bundled with OpenClaw 2026.4.1, and may not affect other versions or platforms.

Recommendation

Apply workaround by patching the SDK code to re-throw the error in the catch block, as an upstream SDK fix may take time to be released and updating the bundled SDK version may not be feasible in the short term.