I have code that adds properties to files using Google Drive API and it worked fine for almost a year. Last week it suddenly started throwing errors.
Service.Properties.Insert(New Google.Apis.Drive.v2.Data.Property() With {.Visibility = "PUBLIC", .Key = "Type", .Value = request.Type}, fileResult.Id).Execute()
The error message I get is:
Google.Apis.Requests.RequestError
Property not found: key = Type and visibility = PUBLIC [404]
Errors [
Message[Property not found: key = Type and visibility = PUBLIC] Location[ - ] Reason[notFound] Domain[global]
]
Does anyone know what might cause this? The code hasn’t changed but it stopped working after Google had some service issues.
yup, they just shut down the v2 properties outta nowhere. I switched to v3 pretty early, but a lot of folks ended up stuck. that 404 error is just telling ya the endpoint’s gone. use Files.patch() with appProperties now instead of Properties.Insert.
You’re hitting the deprecated Drive API v2 endpoints. Google’s been gradually shutting down v2 and moving everything to v3. Same thing happened to me last month - my automation scripts started randomly failing.
The Properties resource from v2 got replaced with appProperties and properties fields in v3. You’ll need to update your code to use Drive API v3 and modify files directly instead of the separate Properties.Insert method.
In v3, you set properties when creating or updating files using Files.Update with the appProperties parameter. Check your Google Cloud Console for any deprecation notices. The transition’s messy and some v2 endpoints get disabled without much warning, especially after service disruptions.
Had this exact problem two weeks ago with my file management app. Google killed the Properties API from Drive v2 with basically no warning - seems like they sped up the shutdown after their recent outages. That 404 means the Properties endpoint is just gone now. You’ll need to switch to Drive API v3 and use appProperties instead. Swap out your Properties.Insert call for Files.Update and put the properties in the request body. Main difference is v3 treats properties as file metadata, not separate things. Took me about 200 lines of refactoring, but honestly v3’s cleaner once you figure it out. Don’t forget to update your OAuth scopes too - some v2 scopes won’t work with v3.