https://assets.adobe.com/cloud-documents
It's a great feature in theory. Unfortunately, it's giving me a lot of guff when I want to work on my file again. In this case, it's the design for my small business launch. I mean, sure, I can redo it. I have a desktop version that's about an hour behind the Cloud documents version in terms of work but man, incredibly irritating. I don't like having to wrestle my files away from friggin robots.
I'm attaching a visual as well as a txt dump of the Photoshop version and system specs etc.

Repro Steps:

Scenario A.
1. Open Creative Cloud.
2. Select Cloud Documents.
3. Attempt to open file.
4. Observe error message.

Scenario B.
1. From CC interface, open Photshop.
2. Attempt to open document from welcome screen.
3. Observe error message.
3b. (Optional) Scream in rage.

Scenario C.
1. Open Photoshop.
2. Open file -> Cloud documents (little box under the file selector).
3. Observe error.
3b. See Scenario B.

If there is an "idea" to be had here, it is this: Fix Cloud Documents. That would be a really good Idea. I'm a goddam Thought Leader over here. Look at the big brain on Matt!

Potentially Useful Info:

I can open the files from before and after this one file's creation.
- I suspect that the issue is related to the file size. I saw something about files over 4mb causing issues? The neighboring files are much smaller in size.
- It could be something went wrong on that specific date? It appears to be the only cloud save from that day.

I will most likely have already re-done my work by the time this is answered although I am curious to learn the cause, when one is determined.

Thanks,
-m-

My friend will work on edititing my photos from her computer, and I will be unable to access her saves from my own computer. They will show up in the online folder, Creative cloud app is running, and will say it's up to date. But I won't be able to access any of the files created elsewhere, unless I visit the folder on the web, create a new folder for each file, and move a single file to an individual folder on the web. After, and only after doing that, will the photos show up on my desktop. Restarting the Creative Cloud app has no effect.

I'll also save files, and they will not be there in the folder! Really fun when I do a batch process on about 3 hours worth of edits, and it's all gone because the save portion of the batch process did not work. So no batch processing for me.

The save problem is also solved by creating a new folder for each file save. Sometimes saving will actually work, so I always check after saving a file to be sure it's there. And if it doesn't show up in the file, I can get it to actually save by creating a special folder to put the file in. One folder, one file. Or it could not work. It can happen if I save the file to a folder on my computer, or if I save the file in the creative cloud.

So, I'm getting creative with my folder names. So far, we have the following names:

Photoshop is a piece of shit
Adobe hates me
How many I hate adobe folders do I need
1 adobe
2 is
3 an
4 absolute
5 piece
6 of
7 horse
8 shit

Okay, not particularly creative, but hey, it's still rather early in the game.

Seriously. I'm paying 10 bucks a month for this aggravation?

Mac High Sierra 10.13.6
Photoshop CC 20.0.4
Creative Cloud 4.8.2.476

Seems to just spit out the last cached version without checking if it was invalidated.

Repro steps:
- Have PSD file freshly synced to Creative Cloud.
- Open the Creative Cloud iOS app
- Do a "Quick Export" of the PSD, Save to Images. Don't close the app.
- Make some visible change to the file in Photoshop, on Windows 10. Sync.
- Notice that the Preview has updated as expected in the app.
- Do another Quick Export, Save to Images.
- Notice that it returns immediately, giving the last export given instead of a new export reflecting the change you just made.

Expected Result: Second export has expected changes.

Actual Result: Second export is the same as first export, no time taken.

Using latest Creative Cloud iOS and desktop apps, Windows 10 v1903, latest Photoshop. iOS v 13.2.2, iPhone 6s.

EDIT: Turns out the Quick Export wouldn't update even after shutting down and re-opening the app. I had to sign out and back in, and that allowed it to update. Also, it's worth mentioning that every time I Quick Export, it hangs partway through, and I have to stop it and re-export, then it finishes immediately. Really strange behavior all around...

On both assets.adobe.com and the Creative Cloud iOS app, the stroke effect appears to be expanding the lines by X pixels in thumbnail space, rather than in file space as intended. I.e., the lines in the preview are way too thick and inconsistent with the image as shown in or generated by Photoshop. The problem is worse in the app than on the website.

By "stroke effect", I mean in Photoshop, when you right-click a layer (in my case a group of layers), click "Blending Options...", then check "Stroke" and set the size to some value (in my case, 5 pixels.)

Example file: https://adobe.ly/2KF3yWt (the top-level layer "Line Art" has the affected stroke effect.)

So I was working on this file last night, closed Photoshop, then shut down my PC (we'll say PC #1). Next day, I hop on PC #2 and the file had synced some changes, but not the latest changes. (PC #1 possibly shutdown mid-sync?) Specifically, the diamond-shaped paths in the file were not present on PC #2 when viewed in Photoshop. I check the iOS Creative Cloud app, file has no preview, says "Preview not Available", no option to quick export either. It was working for this file the day before. Check assets.adobe.com (henceforth "web"), preview still not available, shows file type as "Octet", extension ".psd" is shown in the file name rather than being hidden like the other files. So I look at the file on PC #1, and the changes I had made last night were still present when opened with Photoshop. Because I'm guessing the file type wasn't detected, I remove the file extension by renaming it in explorer. The file syncs, then... disappears! Not present on web either. Panicking, I hit Ctrl-Z and the file pre-rename comes back. I copy it out of the directory, check it, it's fine. File is back in web, still no preview, type Octet. (EDIT: I just checked Recycle Bin and there's a copy of the file in there, deleted around the time this bug was happening. I don't recall doing that, as I was using Shift+Delete after this occurred, so it may be from the original disappearance.)

As an experiment, I delete the file in the CC dir and sync, now gone from web. Then, outside the CC dir, I once again rename to remove the extension, then copy in the file, and sync. It shows up on web as Octet, no preview. I rename it to ".psd" in directory, sync, and still Octet and no preview on web. I delete the file, sync, now gone from web. Then, outside the CC dir, I add ".psd" back by rename, then copy it in. It syncs, and success! On web, the file is now of type PSD and the preview is showing as expected.

To be completely clear, I expected:
1) The cloud to correctly detect/maintain the file type initially.
2) The cloud to detect the file type on rename, which it did not.
3) Creative Cloud to not delete my file both locally and on cloud without warning - this is obviously a severe problem. I'm lucky to have been able to recover the file.

If there are logs, they'll be on the account associated with this email. Both PCs are on Windows 10 v1903, latest Creative Cloud (5.0.0.354), latest Photoshop (21.0.1). The file affected was "Sojourners/NaomiFrontView4.psd": https://adobe.ly/2KF3yWt I haven't modified this file since before the bug and I'll just work on a differently named copy going forward.

My anti-virus (Trend Micro) was enabled, but logs show that it took no action throughout all of this.

File is about 50 MB, whereas SSD has about 33 GB of space left.