# Yanked ic-cdk v0.18 – Investigating Reported Issues **URL:** \ **Category:** Rust\ **Tags:** CDK\ **Created:** [May 13, 2025, 3:10pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908 "2025-05-13T15:10:35Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![lwshang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lwshang/32/3394_2.png) [@lwshang](https://forum.dfinity.org/u/lwshang)\ **Post date:** [May 13, 2025, 3:10pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/1 "2025-05-13T15:10:35Z")
Hi everyone, We’ve yanked ic-cdk **v0.18.0** and **v0.18.1** due to reports of unexpected errors. We’re currently investigating whether these stem from bugs in the release or potential usage misunderstandings and will share updates as soon as possible. For production environments, please continue using **v0.17**. If you’d like to test the new API changes, you can experiment with **v0.18.0-alpha.2** , but we advise against deploying it in production until the issues are resolved. We apologize for the inconvenience and greatly appreciate your patience and feedback. If you encountered errors similar to the reported ones below, please share details in this forum thread. Your input will help us diagnose and fix the problem faster. ```auto Canister violated contract: \"ic0_msg_reply_data_append\" cannot be executed in cleanup mode ``` ```auto Canister violated contract: ic0_msg_reply_data_append: the call is already replied. ``` Thanks, Linwei ---
**Author:** ![Vivienne](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/vivienne/32/29170_2.png) [@Vivienne](https://forum.dfinity.org/u/Vivienne)\ **Post date:** [May 13, 2025, 3:59pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/2 "2025-05-13T15:59:29Z")
---
**Author:** ![lwshang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lwshang/32/3394_2.png) [@lwshang](https://forum.dfinity.org/u/lwshang)\ **Post date:** [May 14, 2025, 7:06pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/3 "2025-05-14T19:06:11Z")
Good news! We’ve completed our investigation. To summarize: - There were no known bugs in the `ic-cdk` v0.18 release itself. - The reported issues stemmed from projects inadvertently using multiple incompatible major versions of `ic-cdk` in their dependency tree. - We’ve released v0.18.2 and backported fixes to all major versions from 0.8 through 0.17. @AdamS posted a complete explanation with all the details [here](https://forum.dfinity.org/t/ic-cdk-v0-18-2-release-important-update-on-version-compatibility/47963). The new versions include improved safeguards that will detect version conflicts at compile time and guide you to solutions. Thank you for your patience while we investigated this issue. If you have any questions, please feel free to ask in the thread linked above. ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [May 15, 2025, 5:09pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/4 "2025-05-15T17:09:51Z")
Linking to the most up-to-date info, as `v0.18.2` has been yanked: [Ic-cdk v0.18.2 Release: Important Update on Version Compatibility](https://forum.dfinity.org/t/ic-cdk-v0-18-2-release-important-update-on-version-compatibility/47963) ---
**Author:** ![zensh](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/zensh/32/15359_2.png) [@zensh](https://forum.dfinity.org/u/zensh)\ **Post date:** [May 17, 2025, 2:39pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/6 "2025-05-17T14:39:17Z")
When will ic-cdk v0.18 be fixed and available for use? Several of my projects have already migrated to ic-cdk v0.18, and it’s impossible to revert back to ic-cdk v0.17 now. @lwshang @AdamS ---
**Author:** ![cyberowl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/cyberowl/32/3635_2.png) [@cyberowl](https://forum.dfinity.org/u/cyberowl)\ **Post date:** [May 18, 2025, 7:25am UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/7 "2025-05-18T07:25:09Z")
Given that we have found a solution to the issue. Do we still need to roll back to `v0.17.2` as proposals `[136671, 136672, 136673, 136675, 136676, 136678]` are attempting to do? ---
**Author:** ![AdamS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/adams/32/5248_2.png) [@AdamS](https://forum.dfinity.org/u/AdamS)\ **Post date:** [May 21, 2025, 8:26pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/8 "2025-05-21T20:26:18Z")
Expect an update soon (\<7 days). We apologize for the inconvenience. ---
**Author:** ![AdamS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/adams/32/5248_2.png) [@AdamS](https://forum.dfinity.org/u/AdamS)\ **Post date:** [May 27, 2025, 2:55pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/9 "2025-05-27T14:55:39Z")
Update: A couple of issues have been discovered in 0.18.2 and we expect to release 0.18.3 soon to address them. These issues cannot be encountered if you had working code in 0.17 that you upgraded, and did not start using new futures-based abstractions like async channels since then. They only relate to the circumstance where you await non-inter-canister-call futures like channels or barriers. ---
**Author:** ![zensh](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/zensh/32/15359_2.png) [@zensh](https://forum.dfinity.org/u/zensh)\ **Post date:** [June 2, 2025, 11:43pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/10 "2025-06-02T23:43:54Z")
I check for new ic-cdk releases every day. 🥹 ---
**Author:** ![AdamS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/adams/32/5248_2.png) [@AdamS](https://forum.dfinity.org/u/AdamS)\ **Post date:** [June 4, 2025, 5:28pm UTC](https://forum.dfinity.org/t/yanked-ic-cdk-v0-18-investigating-reported-issues/47908/11 "2025-06-04T17:28:20Z")
`ic-cdk` 0.18.3 is now released. > [@Ic-cdk 0.18.3 released](https://forum.dfinity.org/t/ic-cdk-0-18-3-released/49637): > > Hi everyone, We’ve released ic-cdk [v0.18.3](https://docs.rs/ic-cdk/0.18.3/ic_cdk/index.html). This release brings the removal of a few edge cases from v0.18.2, as well as support for the new [root\_key API](https://docs.rs/ic-cdk/0.18.3/ic_cdk/api/fn.root_key.html) and mirroring mainnet parameters for Bitcoin regtest. If you are just now updating to 0.18 from 0.17 or before, we have prepared a [migration guide](https://github.com/dfinity/cdk-rs/blob/0.18.3/ic-cdk/V18_GUIDE.md) that we recommend you read. There are changes to the call API, as well as changes to the execution order of code that calls spawn. The [futures module](https://docs.rs/ic-cdk/0.18.3/ic_cdk/futures/index.html) also has new and improved documentation that de…