Adding conferencing with ConferenceData.CreateConferenceRequest gives "Invalid conference data"

NOTE: this is mirroring a ticket created on the nodejs side here: https://github.com/googleapis/google-api-nodejs-client/issues/2387

Environment details

• Programming language: C#
• OS: Windows 10
• Language runtime version: .NET Standard 2.0
• Package version: 1.52.0.2375, but I’ve tracked it back to at least 1.51.0.2305

Steps to reproduce

An EventsResource.UpdateRequest with the following code used to work, but no longer does (not sure at which point it changed - maybe with the change from Hangouts to Google Meet?). This seems to work fine in the API explorer, but both I and a user of the JS client (see linked issue above) are reporting issues with the API packages.

public static Event SetConferencing(Event eventToModify, ConferencingType conferencingType)
{
	string conferencingTypeString = null;
	switch (conferencingType)
	{
		case ConferencingType.EventHangout:
			conferencingTypeString = "eventHangout";
			break;
		case ConferencingType.HangoutsMeet:
			conferencingTypeString = "hangoutsMeet";
			break;
	}

	eventToModify.ConferenceData = new ConferenceData
	{
		CreateRequest = new CreateConferenceRequest
		{
			ConferenceSolutionKey = new ConferenceSolutionKey
			{
				Type = conferencingTypeString,
			},
			RequestId = Guid.NewGuid().ToString(),
		}
	};

	return eventToModify;
}

After this I call:

EventsResource.UpdateRequest eventUpdateRequest = service.Events.Update(eventToUpdate, calendarId, eventToUpdate.Id);
eventUpdateRequest.ConferenceDataVersion = 1;
eventUpdateRequest.Execute();

Using conference type “eventHangout” gives the error “Invalid conference type value.” (probably because Google Meet has replaced Hangouts?). Using conference type “hangoutsMeet” gives the error “Invalid conference data.”

Trying this in the API explorer seems to work just fine (event.update endpoint):

[jskeet]

Thanks for the issue - I’ll look into it on Monday.

[derekantrican]

Yeah, that’s totally fair. Thanks for investigating this and I’ll report the “eventHangout” discrepancy via the bug tracker