openclaw - 💡(How to fix) Fix [Bug]: 2026.4.5: device commands fail because google plugin crashes with RangeError: Maximum call stack size exceeded [1 participants]

PS C:\Users\Administrator> openclaw devices approve --latest 02:02:58+07:00 [plugins] google failed to load from C:\Users\Administrator\AppData\Roaming\npm\node_modules\openclaw\dist\extensions\google\index.js: RangeError: Maximum call stack size exceeded

TL;DR

• The issue can be potentially resolved by temporarily disabling the google plugin or clearing the plugin/cache state to prevent the RangeError: Maximum call stack size exceeded error.

Guidance

• Try disabling the google plugin to see if the device commands work without it, which can help determine if the issue is plugin-specific.
• Clear the plugin/cache state by deleting the C:\Users\Administrator\AppData\Roaming\npm\node_modules\openclaw\dist\extensions\google directory and then reinstalling the OpenClaw package globally.
• Verify if the issue is specific to the Windows environment or if it occurs on other platforms as well, to determine if it's an OS-specific problem.
• Check if there are any known issues in the OpenClaw version 2026.4.5 related to plugin loading or the google plugin specifically.

Example

No code snippet is provided as it's not directly applicable to the given issue, but the commands to clear the plugin/cache state could be:

rm -r C:\Users\Administrator\AppData\Roaming\npm\node_modules\openclaw\dist\extensions\google
npm install -g openclaw

Notes

The provided information suggests that the issue might be related to the google plugin, but without the full trace or more details about the plugin's functionality, it's difficult to provide a definitive solution. The suggestions provided are based on the information given and are intended to help troubleshoot the issue.

Recommendation

• Apply workaround: Temporarily disable the google plugin or clear the plugin/cache state, as this seems to be the most direct way to address the RangeError: Maximum call stack size exceeded issue without waiting for a potential fix in a future version of OpenClaw.