Why does SmartContent [mess] up product updates so often?

I have encountered this problem several times now:
Smart Content reports that there is a product update available and all it does it totally [messes] up the product. Lately it's Freja who received an update and now it's like the files are all gone.
I also tried to update "NG Build Your Own Kneeling Poses for Genesis 8 Female" a few times but it just keeps showing up in the update panel (even after reinstallation?!).
Sometimes it seems the only way to "repair" the files is uninstall and reinstall them with one of the other methods.
But why does SmartContent [mess] up product updates so often? I'm even now trying to avoid product updates...
Post edited by Richard Haseltine on
Comments
It can happen to non-updates too. I have tickets in about several, including Freja 8 - it does seem to be a Daz-side issue.
I tried to re-install Freja via SmartContent but all files are 0 kb placeholders. I'm now using DazCentral to solve the issue.
According to what has been written here at the forum, I get the impression that "Smart" Content (=DAZ Connect) downloads files that are encrypted and decrypts them during the process and that doesn't seem to be working that good -> Botched installation.
Also DAZ has been having problems with the servers since the store update, which has made the files unavailable in whole or in part and at least with thumbnails and metadata, DAZ Connect has still went on with the "update" -> Botched installation.
Sounds plausible to me - albeit not a satisfying result for the customers.
I see that the new update for Freja now includes an 8.1 version. Unfortunately the meta data now appears in "lost and found" -_-
Smart Content <> Daz Connect. Smart Content shows categorised content filtered by its install state and, optionally, compatibility. Daz Connect can be used through the Content Library>Products or through the Install pane.
There are two potential bad outcomes for Connect - files present but not decrypting, or files not in fact isntalling, in which case the product seems empty (going to the folder location may show 0 byte .part files).
There were issues, not related to the store update, with the CDN being used. Those alrgely seem resolved, and when they weren't they seemed to affect DIM/Central too.