We want to bring to your attention a critical update regarding the latest version 18.104.22.168.
Important notice: Removal of Global Styles After Saving
We have identified an unforeseen issue that affects global styles.
Action Required: Do Not Update
In light of this issue, we strongly advise all users to refrain from updating to 22.214.171.124 until further notice.
Our development team is actively working on a fix, and we aim to release a patched version as soon as possible.
We understand the inconvenience this may cause, and we sincerely apologise for any disruption to your workflow.
We are committed to resolving this issue promptly and will keep you informed of the progress.
We sincerely apologise for the trouble 126.96.36.199 might have caused on your end.
We have released a fix in 188.8.131.52. This was an unfortunate error with our offloading of API requests that didn’t show up in our final tests.
Special thanks to @sunny and others who reached out to report the issue, much appreciated, you rock!
Enjoy the rest of the week!
I hope this message finds you well. I’m curious about the automated testing process for Cwicly’s new releases. Bugs like this should not slip through, and I wonder if there’s an opportunity to enhance testing with more integrated test cases.
Additionally, I’d like to suggest considering a pre-live release to a small group of testers. It might help identify issues before impacting the wider user base. I understand bugs were manageable when the user base was smaller, but with its growth, they pose more challenges.
While updating after 48 hours is a good practice, I’m wondering if there’s room for improvement. Your insights on this matter would be highly appreciated.
Absolutely agree with @dranzer!