Users in Turmoil | New NEAR Version Sparks Deployment Errors

A wave of frustration is washing over the NEAR community as developers encounter persistent errors when attempting to deploy smart contracts using the latest version. Many are questioning whether recent updates have introduced insurmountable issues during the deployment phase.

Developers report complications during the upgrade process, with one user stating, "I am basically giving up now" after experiencing the same compilation and deployment errors regardless of whether they use standard or example contracts. This has raised alarms over the integrity of the new updates and whether they support existing code bases adequately. Despite users finding compiling works well, deployment attempts repeatedly trigger the FunctionCall Action errors, leaving many bewildered.

Interestingly, the sentiment in online forums has revealed three prevailing themes: compilation success versus deployment failure, dissatisfaction with update stability, and calls for guidance on resolving errors. One user highlighted this dilemma perfectly, saying, "Rust introduced wasm features not yet supported by nearcore," hinting at underlying technical inconsistencies affecting developers.

"First, I am using the example fungible-token smart contract but running cargo-near using rustup results in a long wall of errors."

Additional commentary underscores a mix of angst and hope within the community, suggesting that clarification from NEAR’s developers is needed. As one frustrated developer noted, the older versions had no such issues which cultivates a desire for swift resolution.

Current Developments and Community Impact

The ongoing discussions in developer forums spotlight a growing urgency for NEAR's development team to address these errors swiftly. Currently, the community awaits responses from key NEAR representatives as users grow restless, resorting to employing older, potentially insecure versions of Rust and the near-sdk.

Key Observations

• 📈 Developers report that compiling functions but failing during deployment remains a pressing issue.

• ⚠️ Several users are reverting to less secure versions of various SDKs to regain functionality.

• 💡 "Cargo-near" has been recommended as a workaround to mitigate deployment issues, yet many remain skeptical.

Overall, as the situation unfolds, NEAR’s user base stands at a crossroads, weighing the need for swift fixes against plunging into older, unreliable versions to get their projects up and running. Time will tell how the development team addresses these glitches, and whether they can regain the community’s trust.