I really would like my questions answered and problems to go away. I would rather build software than hund down system issues like this.
I've been developing against the Google "GDATA" API's for over four years now and to this day I still stress about the stability of these services. When things go wrong my customers get to complain to me and then I have to stress/scamble to figure out what broke this time, find a work around for my customers, and then hope that Google knows about this issue and fixes it. I then need to make sure my workaround does cause problems when the issue is properly fixed. In the end Google returns system errors that software simply cannot respond to and in those cases the end-user is presented with an error and left there wondering what to do. Most users don't know what to do when Google returns a "503 Bad Gateway" error or "(400) Bad Request" and where no addtional data/info is returned with the error. "(500) Internal Server Error" is a great error as well which often does not provide any insight into what is not working. Alain seems to be very responsive so hopefully my issues we get resolved quicky. On May 29, 10:24 am, Robert Owens <[email protected]> wrote: > I wish you good luck in getting Google's attention on this. I am struggling > with Google calendar services that seem to change and stop working with out > any notice. Rather scary if you are attempting to develop professional > product that customers can rely on. > I will be looking forward to seeing what the resolution is here. > > > > On Wed, May 25, 2011 at 8:31 PM, cyberhex <[email protected]> wrote: > > *PROBLME #1: *Starting about one week ago I am getting loads of "Stream is > > not readablle" errors when accessing the Google calendar service from > > customers located all over thw world that use my software to access the > > Google calendar API's. I can only suspect that this issue is a Google > > Calendar Service problem since many of my customers didn't change a thing > > and this issue just popped up out of nowhere. > > > *HELP: *Can someone at Google explain what was changed recently that may > > be causing "Stream is not readable" errors while reading events from the > > Google Calendar service using the Google calendar client .Net libraries > > provided by Google? > > > *PROBLEM #2:*I've had users randomly report the error "The user is not > > allowed to add events to the new calendar" when updating older Google > > calendar events using the Google Calendar GDATA API. This error started > > being reported about 4 weeks ago without any changes to the software by my > > customers. So, again, I can only suspect that _something_ changed with the > > Google calendar service itself to cause this error. This error also only > > occurs for some events in the calendar which further makes this error > > message very misleading > > > The only "solution" I've found to this issue is to instruct the customer to > > wipe out their Google calendar data and repopulate it. Why would the user > > get a message like "The user is not allowed to add events to the new > > calendar" but can a) add events direction from the Google calendar web > > interface and b) after wiping out the entire calendar (which is clearly not > > new since it contains events) is able to update/add events to the calendar? > > > *HELP: *Can someone at Google explain what was changed recently that may > > be causing this error and what is the correct path to correct this? > > > -- > > 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://code.google.com/apis/calendar/community/forum.html- Hide quoted text - > > - Show quoted text - -- 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://code.google.com/apis/calendar/community/forum.html
