tag:support.markedapp.com,2011-09-11:/discussions/problems/110241-can-no-longer-open-files-in-icloudMarked: Discussion 2022-02-01T12:01:59Ztag:support.markedapp.com,2011-09-11:Comment/392356952016-02-23T00:57:46Z2016-02-23T00:57:47ZCan no longer open files in iCloud.<div><p>After some further troubleshooting, this might be an iCloud
problem and not one with Marked. I toggled iCloud off/on and
awaiting re-download of files.</p></div>Dave Mactag:support.markedapp.com,2011-09-11:Comment/392356952016-02-23T15:17:05Z2016-02-23T15:17:05ZCan no longer open files in iCloud.<div><p>Definitely sounds like it could be on the iCloud side. Let me
know if it doesn't resolve after syncing.</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/392356952016-02-23T15:45:03Z2016-02-23T15:45:04ZCan no longer open files in iCloud.<div><p>Yep, iCloud was the culprit. I had to restart the computer to
get it working properly.</p>
<p>On that note, do you recommend using iCloud or Dropbox since it
seems the "keep only open on 1 Mac" sync bug might still exist in
nVALT?</p></div>Dave Mactag:support.markedapp.com,2011-09-11:Comment/392356952016-02-23T15:56:15Z2016-02-23T15:56:15ZCan no longer open files in iCloud.<div><p>Glad to hear it.</p>
<p>I haven't had any issues with nvALT in Dropbox on multiple
machines over<br>
the last year. I think the issues were resolved on Dropbox's side.
I<br>
don't use iCloud much. For the record, though, a new incarnation
of<br>
nvALT is in the works, but still planned to be Dropbox-based (or
any<br>
sync system that handles folders).</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/392356952016-05-23T18:56:18Z2022-01-31T20:23:17ZCan no longer open files in iCloud.<div><p>The issue is with iCloud Drive. I get the same "The file “(null)” couldn’t be opened." error with other applications including Byword, Desk, Pages, Numbers, Preview etc. Once the Mac (this occurs on my MacBook Air and iMac) is rebooted the issue resolves itself until the next occurrence.</p>
<p>I am running OS X 10.11.5 but the issue occurred under 10.11.4 and 10.11.3</p></div>khurt