I tried to update to the latest version 529 that was just released and I could not do it. The message I received on the Mosaic app on my iPhone 17 Pro said, “Failed to download Manifest, please contact dCS.” Anybody know what this is about? Thanks.
From Mosaic on your iPhone, when you click on “Check for Update” Mosaic actually instructs your dCS platform to contact the dCS Firmware hosting Server on the Internet.
But before downloading the new firmware, your dCS platform downloads a manifest in order to compare the version held on the dCS Firmware Server against the current firmware on your dCS platform - in case it already has the latest. If the versions are the same, then Mosaic will display “No firmware update”. If the Firmware on the Server is newer, then Mosaic will show the version available for update.
In your case, your dCS has a problem with that first step of downloading the manifest in order to compare firmware versions.
There could a range of reasons why that’s happened - Problems with your Internet. Problems with reaching the dCS Firmware server (they’re actually hosted on CDN caching servers), etc. My suggestion, just to be sure, you should reboot your dCS using the rear power button, and try the update process again.
3 Likes
Jim, you will find the solution here :
It is the same procedure whichever current dCS unit you have except Varese. This was response to a Bartok query but it is the same for Vivaldi, Rossini and, I think, Lina.
1 Like
Thank you so much for your suggestion. It worked!
Thanks for your response. That solution worked.
I too have just experienced this error on my Vivaldi rig. I have tried rebooting both the DAC and Upsampler, but the error persisted. I then rebooted my router, and all was fine. Update proceeded smoothly. Every now and then . . ..
Thats interesting… And you had no Internet access issues just prior to that via that same Router?
The manifest that your Vivaldi Upsampler pulls down from the Firmware Server is tiny, about 4KB, so, it’s more likely to be a Firmware Server address DNS resolution issue that got sorted after the Router reboot 
1 Like
Yeah, zero internet issues prior to the update attempt. Lots of net activity going on immediately before my attempt. So, rebooting the router was just a “what the heck, who knows” thing. And it worked.
1 Like