youtubeuploader
youtubeuploader copied to clipboard
porjo
video locked to private due to unverified API project
We submitted that the video was uploaded using a third party tool that failed our verification. Because of this, we set limited access for the video.
At which step did you encounter this message? Perhaps this message is not about the program youtubeuploader itself or "My application in Google Cloud Console" program?
youtubeuploader seems to be still working for me, although I've been asking for increased quota (and was eventually granted) which means that I'm already audited. Nevertheless I was able to successfully upload several videos making them unlisted or private (I didn't feel like uploading a public video to notify my subscribers).
I have been using youtubeupload for a month now, everything was fine. For about a week I have been uploading videos to several accounts, as soon as I make the video public, I immediately block it. Tested on Windows 7 and Ubuntu 18.04
I've just uploaded this video using youtubeuploader: https://www.youtube.com/watch?v=g1IXTedsbp0 As for now it's public with no problems (forgive the quality of my gameplay).
The command I've used was:
youtubeuploader -filename League\ of\ Legends\ 2020.07.04\ -\ 10.58.21.04.mp4 -secrets client_secret.json -headlessAuth
I think I'm having this same problem. Used this program for the first time yesterday, and the video gets locked to private shortly after upload due to using an unverified third party service. Here's an image of the notification email from youtube.
Seems related to this recent change, requiring all youtube API projects made after July 28th undergo an audit before allowing normal uploads.
I'm very inexperienced with all this though, so I may well have simply set something up wrong!
I came here to report this as well. I was having no issue using youtubeuploader until last night. I uploaded a video and it was locked to private minutes later, so I deleted it and uploaded another video as a test and the same thing happened.
Here's an image of the notification email from youtube.
This seems to straighten my case that the API key / usage is unverified rather than youtubeuploader itself. I had na audit before (due to asking for increased quota) and I don't have this issue.
This is very sad as going through the audit is rather tedious as the process is designed for applications open to the public which is the dominant case from API usage perspective but a rare case as I imagine for every big and popular app there are dozens or hundreds of "private" use cases.
Thanks for the report, I was unaware of this issue. It does sound like bad news for youtubeuploader - yet another hurdle to overcome.
From Google's announcement:
All videos uploaded via the videos.insert endpoint from unverified API projects created after 28 July 2020 will be restricted to private viewing mode. To lift this restriction, each project must undergo an audit to verify compliance with the Terms of Service.
Creators who use an unverified API client to upload video will receive an email explaining that their video is locked as private, and that they can avoid the restriction by using an official or audited client.
API projects created prior to 28 July 2020 are not currently affected by this change. However, we strongly recommend that all developers complete a compliance audit for their projects to ensure continued access to the YouTube API Services.
Just to confirm, the videos are locked to private (i.e. they can't be manually changed to public after upload) ?
Just to confirm, the videos are locked to private (i.e. they can't be manually changed to public after upload) ?
Can confirm, video is locked to private and can't be changed to public.
I am just looking to upload a few videos a week. Are there any existing, verified API "projects" that I can use or am I stuck getting my own verified for such a small scale use?
I have this problem either. I taught this was my program's error etc. Until we start the confirmation process may I use someone's API (I need just client_secrets.json). We will upload maximum 1-2 video per day.
API's are used to simplify development, but sadly Google/Youtube didn't get that note. Maybe the API should be replaced with Selenium. One project does a similar thing: https://github.com/linouk23/youtube_uploader_selenium But it isn't really practical for automation yet.
Selenium has no relevance to this issue. I further don't think selenium would offer much benefit because web browser interaction is very very minimal. And it would be a dependency on a huge package.
I have the same issue of video made private, with no option to make them public through the web interface. Is there any solutions to this ?
Your API project just needs to be audited. They'll ask for a description of what you're trying to do and eventually they'll approve your usage unless they don't like it. They're not trying to make life difficult, they have to do this because of spam.
They actually do make it difficult. You have to describe what users will use it, how users will use it, how long you will retain user data, how does the interface look for users etc. This is fine if you're making an app which you release for a wider audience and you make use of YouTube API in it. However if this is some server side feature for your own usage (big or small, but no outside users whatsoever, everything in console) then the process makes no sense.
I got approved, however:
- the first time I tried the form was protected by outdated captcha and there was no way to send it (none of the bypasses worked) which says a lot
- once they've switched to a new form it took me 6 months to be approved, however they'll email me occasionally (1-2 times a month) with questions which were always bad (already answered in a form, or they've drawn wrong conclusions) and every time the emails said that I need to respond in 3 days (!) and if not my process will be canceled. That's a long period of time in which you can't miss an email with 3 days deadline
The process is very bad, let's not pretend it's not. Is it needed? Yes, very much so. It doesn't need to be that bad though.
czw., 15 paź 2020 o 11:49 qome [email protected] napisał(a):
Your API project just needs to be audited. They'll ask for a description of what you're trying to do and eventually they'll approve your usage unless they don't like it. They're not trying to make life difficult, they have to do this because of spam.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/porjo/youtubeuploader/issues/86#issuecomment-709053845, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVUEO5CAV5CV7CBN4JRL6LSK3ATXANCNFSM4QJK5GNA .
-- Marcin Wasłowicz
Same experience here. They also don't appear to understand what an executable on a computer is, they only understand web sites, it appears. Takes forever to explain what you want to do (or actually already did in the past). Now that I have access (which took 3 month for me) I now do regular private dummy uploads to keep the status as it is. Because you can lose access it if you don't use the API for 90 days.
I literally told them that this was a server side application and provided my entire source code. They asked me for the same information a second time and I told them to read what I already sent or deny my application. They approved my usage.
They make it very easy.
I need to fill in a whole bunch of OAuth consent screen stuff, with a privacy policy and a description video because it's using "sensitive youtube API" stuff. What did you all put in those fields? It's horrendous and it makes me sad :(
Now that I have access (which took 3 month for me) I now do regular private dummy uploads to keep the status as it is. Because you can lose access it if you don't use the API for 90 days.
Yeah that happened to me and now I’m seriously considering just eating the horrible browser upload workflow instead of this nicely automated one because it’s STILL less hassle than having to go through that stupid audit process.
For everyone interested, this is the batch file I am using to do regular uploads. I just upload a tiny video of a few(?) black frames. It's only 3kB. I set it to visibility private. Edit it to your needs. Also adjust the paths if needed (I can use relative paths). You might want to execute this monthly as a scheduled task.
@"YoutubeUploader\bin\youtubeuploader.exe" -secrets "xxxxxxxx - cred.json" -cache "xxxxxxxx - request.token" -title "dummy video" -description "Dummy video to perform regular uploads. May be deleted." -privacy private -filename "dummy.mp4" -metaJSON meta.json
if errorlevel 1 pause
@wolf128058 Same issue here, I spent like 3 weeks and 15 emails getting my app verified and now after being verified for the youtube scopes everything I upload still instantly gets locked as private for "spam, deceptive practices ..." without any appeal option.
Did you ever figure out a way around that?
@wolf128058 Same issue here, I spent like 3 weeks and 15 emails getting my app verified and now after being verified for the youtube scopes everything I upload still instantly gets locked as private for "spam, deceptive practices ..." without any appeal option.
Did you ever figure out a way around that?
Sorry, but I did not find one.
Same here. I went through the verification process. After a couple of weeks of back-and-forth correspondence they told me that my application didn't have to be verified because it was for use by less than 100 people. They suggested I go through an API audit to have the "locked as private" designation removed. I applied for an audit. After several days of more back-and-forth they informed me that the audit was complete and that no further information was required. They never told me what the result of the audit was and they did not respond to further inquiries. But, my uploads are still "locked as private".
It seems hopeless.
I received an additional response from YouTube API services:
The error you encountered is not YouTube Data API related.
On the other hand, if I try and appeal the "locked as private", I get:
Appealing this violation is not available
@Buadhai I had the same issue where I went through the audit form (which doesn't even have an option for that despite the insert api docs specifically linking to it so I just selected "get more quota") to get rid of the "video locked as private" issue and they replied that they removed that restriction now and I could upload videos in the future without being locked.
Despite that I also couldn't upload videos still and they still got locked so I replied with that problem again to the same thread and a week later when I tried again it worked. I can now finally upload videos without issues. Not sure if it was my reply about it that made them fix it or it just always takes a while.
Thanks @ulysso. I guess I'll wait a bit. When you say "same thread", do you mean that you submitted the same form again?
Same issue here!
The change is documented here: https://developers.google.com/youtube/v3/docs/videos/insert
All videos uploaded via the videos.insert endpoint from unverified API projects created after 28 July 2020 will be restricted to private viewing mode. To lift this restriction, each API project must undergo an audit to verify compliance with the Terms of Service. Please see the API Revision History for more details.
It appears that my effort to have my API usage audited has worked. The video uploaded today is public. No idea if this is a one-off piece of luck or if future videos will also be public. It was a real PITA to go through all that. But, it worked.
Congrats. Now that you have access, make sure you upload regularly. If you don't upload for more than 90 days, you may loose your privileges. I do a dummy upload (empty video) every 2 months or so, just to keep access. I sometimes don't upload any videos for multiple months, and then I need to upload hundreds of them in a couple of days.