Thanks Charlie. I'm investigating this -- It doesn't seem like it
should occur in the method you described (and I've reproduced).
The other case where you would get a similar behavior would be on a
calendar which represents a resource. In this case, the resource
could be configured to auto-accept, and a gd:who similiar to the one
you posted, would be added to the event entry. However, you would see
another gd:who representing the organizer in that case.
Cheers,
-Ryan
On Mar 19, 4:20 pm, "Charlie Wood" <char...@gmail.com> wrote:
One of our users figured out when this is happening, and I've been
able to reliably reproduce it:
* Create an event in your default calendar
* Edit the event so it belongs to a different calendar (in this case
named "Calendar 2")
* Request the event via the API
The event will now have a <gd:who /> element like this:
<gd:who rel="http://schemas.google.com/g/2005#event.organizer"
valueString="Calendar 2"
email="xxxx...@group.calendar.google.com">
<gd:attendeeStatus value=""/>
</gd:who>
Is that the intended behavior?
Thanks,
Charlie
On Mar 19, 3:38 pm, "Charlie Wood" <char...@gmail.com> wrote:
I've seen several cases where an event doesn't have any attendees in
the web UI, but when fetched via the API has a <gd:who /> element like
this:
"Main" happens to be the name of the calendar. Is this expected? If
so, under what conditions? I can't reproduce it.
3 messages in com.googlegroups.google-calendar-help-dataapiRe: Phantom attendee (with the same n...