Offset of July uncovers yet another issue in Google’s Photos service. Aaargh! The problem rears its ugly head when you try uploading videos, irrespective of the way used. While some users say their upload gets stuck in video processing, others say they can’t access their just uploaded videos (clicking/tapping video produces a gray screen with a message).
It’s worth mentioning that those who complain of inability to access uploaded videos say Photos clearly notified earlier that the video(s) were “successfully uploaded.”
The issue is being largely reported with .mp4 files, but a few of those affected say they are having problems while uploading other type of videos as well (such as .mov). Interestingly, multiple users have confirmed that the problem occurs when their Google Photos Backup & sync setting is on High Quality.
There have even been some stray reports of uploads getting completed, but after a long long wait, and that too for not all videos.
A few of those facing access issues (after Photos says upload is successful) note that sharing the video over email, or importing it while in YouTube lets them play it normally. This strongly suggests the Google Photos upload process was successful, just that the service itself is having issues while playing/accessing it.
For what its worth, the exact errors that users get (while uploading or after uploading) are: “Still processing. Your video will be ready soon” on app and “Your video will be ready soon” or “An error occured, please try again later” on desktop.
With the escalating number of reported use-cases, an expert on the official Photos forum said (August 5)
“I’ve noticed a lot of reports about this lately, I’m going to gather some more info so that I can escalate this to the Google Photos team”
And looks the issue as indeed been escalated, as a recent tweet by Google Photos revealed that the problem is already known and they are working on fixing it.
https://twitter.com/googlephotos/status/894968945836511234
Meanwhile, a few of the affected users have also provided some workarounds (just in case you want to try):