Actually all I have is the edit URL in this case. Long story.  Can he  
tell me the cause and I can modify the retrieved event anyway? Or  
generate a delete query by hand and just call nsurlconnection manually.

-- CEO WebIS
Sent from my phone

On Feb 25, 2009, at 5:26 PM, Trevor Johns <[email protected]> wrote:

>
> On 2/25/09, Trevor Johns <[email protected]> wrote:
>> On Wed, Feb 25, 2009 at 1:08 PM, AK <[email protected]> wrote:
>>>
>>> No, it does not happen on 100% of my delete requests. I've only been
>>> able to reproduce it twice. I am using 1.6.0 of the client. I  
>>> checked
>>> and I am not using setShouldUseMethodOverrideHeader at all.
>>
>>
>> That's interesting. In this particular instance, are you able to have
>> your user reproduce it, or was it completely a one-time occurrence?
>>
>> If you're able to reproduce it at all, it might be useful to obtain  
>> an
>> HTTP transcript so we can figure out what's going on here.
>>
>
> I spoke to Greg Robbins, the principal author of the Objective-C
> client library, about this. He wasn't able to reproduce this either,
> but he thinks he located the problem anyway. He's working on a fix for
> a future release of the client.
>
> Meanwhile, he suggested that you avoid re-fetching a complete entry
> like you're doing in retrieveDeletedCompleteEntryForEntry:. If you
> already have an entry instance, which you should since you're getting
> the self link from somewhere, then you can just directly call
> deleteCalendarEventEntry: on that original instance. Hopefully that
> will make the error go away.
>
> Let me know if this helps.
>
> -- 
> Trevor Johns
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to