Have you compared the yt:recorded element in the XML from http logs with the value of the GDataDateTime response from the recordedDate method?
The presence or absence of the yt:recorded element is up to the YouTube API server; it is only an Objective-C library issue if it is not being translated properly to a GDataDateTime object.
I have just checked in some changes to the top-of-trunk library sources that should improve how date-only (no time) GDataDateTime objects are converted to NSDates. They now are set to noon GMT, so the date should be correct for any time zone.
Since yt:recorded is a date-only element, this may improve the date you see in the video entry, for video entries where that element is returned by the server.
On Fri, Sep 17, 2010 at 5:56 PM, Greg Robbins <grobb...@google.com> wrote: > I have just checked in some changes to the top-of-trunk library sources > that should improve how date-only (no time) GDataDateTime objects are > converted to NSDates. They now are set to noon GMT, so the date should be > correct for any time zone.
> Since yt:recorded is a date-only element, this may improve the date you see > in the video entry, for video entries where that element is returned by the > server.
> -- > You received this message because you are subscribed to the Google Groups > "Google Data APIs Objective-C Client Library Discussion" group. > To post to this group, send email to > gdata-objectivec-client@googlegroups.com. > To unsubscribe from this group, send email to > gdata-objectivec-client+unsubscribe@googlegroups.com<gdata-objectivec-clien t%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/gdata-objectivec-client?hl=en.
> On Fri, Sep 17, 2010 at 5:56 PM, Greg Robbins <grobb...@google.com> wrote:
>> I have just checked in some changes to the top-of-trunk library sources >> that should improve how date-only (no time) GDataDateTime objects are >> converted to NSDates. They now are set to noon GMT, so the date should be >> correct for any time zone.
>> Since yt:recorded is a date-only element, this may improve the date you >> see in the video entry, for video entries where that element is returned by >> the server.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Google Data APIs Objective-C Client Library Discussion" group. >> To post to this group, send email to >> gdata-objectivec-client@googlegroups.com. >> To unsubscribe from this group, send email to >> gdata-objectivec-client+unsubscribe@googlegroups.com<gdata-objectivec-clien t%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/gdata-objectivec-client?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Google Data APIs Objective-C Client Library Discussion" group. > To post to this group, send email to > gdata-objectivec-client@googlegroups.com. > To unsubscribe from this group, send email to > gdata-objectivec-client+unsubscribe@googlegroups.com<gdata-objectivec-clien t%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/gdata-objectivec-client?hl=en.
On Sat, Sep 18, 2010 at 2:16 AM, Greg Robbins <grobb...@google.com> wrote: > This sounds like a Twitter-specific issue; the OAuth client software is not > really involved while the sign-in page is being displayed.
> Can you sign in with any other Twitter client applications that use OAuth?
> -- > You received this message because you are subscribed to the Google Groups > "Google Data APIs Objective-C Client Library Discussion" group. > To post to this group, send email to > gdata-objectivec-client@googlegroups.com. > To unsubscribe from this group, send email to > gdata-objectivec-client+unsubscribe@googlegroups.com<gdata-objectivec-clien t%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/gdata-objectivec-client?hl=en.