Meteor Rejects Addon 1211 Work May 2026

A corrupted cache is a leading cause of “rejects work” errors.

# Stop any running Meteor instance
meteor reset
# This clears your project's .meteor/local folder

Then delete the global Meteor package cache (if safe): meteor rejects addon 1211 work

rm -rf ~/.meteor/package-metadata
# On Windows: rmdir /s %USERPROFILE%\.meteor\package-metadata

Before diving into fixes, let’s break down the keyword phrase into its components: A corrupted cache is a leading cause of

Put together, the error suggests that the Meteor build system or runtime has refused to execute a task initiated by Addon ID 1211. This is not a standard Meteor error message; it is often a composite log output from a CI/CD pipeline, a custom script, or an obscure native module conflict. Then delete the global Meteor package cache (if

To understand the error, let’s break it down:

Combined, "meteor rejects addon 1211 work" means: While attempting to compile or link a Cordova addon (plugin), the Meteor build system rejected the process because a background task (possibly Gradle’s build daemon) returned a non-zero exit code (1211).