A: Meteor wraps Cordova and adds its own build hooks, hot code push, and dependency management. Some hooks clash with native addon initialization. Conclusion The error "meteor rejects addon 1211 work" is a frustrating but solvable problem. It usually signals a deep compatibility issue between a specific Cordova plugin, the Gradle build system, and Meteor's build pipeline. By systematically clearing caches, increasing memory limits, updating SDK components, and isolating the offending plugin, you can resolve the error and restore your mobile build process.
Introduction If you are a mobile developer working with the Meteor.js framework and Cordova , you may have encountered a cryptic and frustrating error message during the build process: "meteor rejects addon 1211 work" .
meteor rebuild The "1211 work" error often hides an out-of-memory condition. Set higher limits:
Cordova plugin: cordova-plugin-firebase@5.0.0 Running command: /path/to/gradle assembleRelease Process 1211 exited with code 1 Error: meteor rejects addon 1211 work Make note of which plugin triggers the failure. Remove suspected plugins one by one:
sdkmanager "build-tools;30.0.3" "platforms;android-30" If the addon is non-essential, remove it entirely:
meteor update meteor update --cordova-platforms But test after each update in a staging environment. Use htop or Activity Monitor to watch CPU/memory during builds. If a Gradle daemon (process ID 1211 or similar) spikes, you may need to reduce parallel builds:
meteor create new-project --cordova cd new-project cp -r ../old-project/client . cp -r ../old-project/server . cp -r ../old-project/imports . Then re-add Cordova platforms and plugins one by one, testing after each addition. Once resolved, adopt these practices to avoid recurrence: Lock Plugin Versions Do not use @latest in production. Specify exact versions in package.json and mobile-config.js :
