We're excited to share what's new in the latest release powered by GitHub Copilot Edits:
✨ Automatic Clio Update Detection
TIDE now checks for the latest Clio release on nuget.org and notifies you when an update is available — so you’re always in the loop.
🖥️ Terminal UI Improvements
We've enhanced the terminal interface for clearer and more user-friendly system process logs.
🔧 Clio Update Handling Refined
Automatic Clio updates on app restart have been disabled to avoid unexpected errors in certain scenarios.
🆕 Clio was upgraded to 8.0.1.26
TIDE works with the latest Clio version, bringing expanded terminal capabilities and better overall integration.
Update now and enjoy a smoother, smarter dev experience with TIDE 💻
#TIDE #Clio #DevTools #ReleaseUpdate #Creatio #TerminalUpgrade
Do you like this idea?
Hello, could you help me please to install TIDE, see details on https://community.creatio.com/ideas/tide-v129
Thanks
Hello Team,
Thank you for introducing Tide — it's a much-needed step towards streamlining version control processes within the Creatio ecosystem. However, I’d like to share my experience to help improve the setup flow and developer experience:
Installation & Setup Issues
Initially, I faced a blocker while installing Tide. Despite running the correct command (clio install tide), the package wasn’t installing properly. Only after manually updating Clio did things start to work — eventually.
✅ Tool 'clio' was successfully updated from version '6.1.0.35' to '8.0.1.40'
Verified with:clio ver --all [INF] - clio: 8.0.1.40 [INF] - gate: 2.0.0.35 [INF] - dotnet: 8.0.17
The first few install attempts failed with this exception:
System.IO.FileSystem.CopyFile(...) Clio.Common.PackageUtilities.CopyPackageElements(...) ... Deleted temporary directory ...
Eventually, after a few retries, it did succeed — but it's unclear why it failed earlier and then succeeded without any changes.
Package Creation & Git Integration
Following this guide: Add Your Apps to Git using Tide, I attempted to create a new record in the Tide-managed section. The first attempt didn’t reflect in the repo, but a second attempt did — again, without any changes. This inconsistency makes it hard to trust the process.
Furthermore, although I committed changes via Tide four times and once directly via GitHub, only the 2nd and 5th commits appeared reliably. The 1st and 3rd commits are still missing, and the commit timestamps do not align precisely with the action times, making traceability difficult.
Console Terminal / Mini Page UI Bug
Another critical issue is with the CLIO terminal popup UI. When triggered, the mini-page gets stuck indefinitely on:
Initialize action ... Setup connection to server ... Loading ...
There’s no actionable error in the logs or trace of what went wrong, and no way to cancel or restart the process gracefully. This makes it extremely difficult to debug and the only available logger tag is TIDE. Here's a screenshot for reference:
📷 See: CLIO terminal log freeze (attached)
Would appreciate any documentation or support to help resolve these blockers more effectively.
Thank you for your support!