Critical JSON Nesting Malform Issue! about browser-samples HOT 9 CLOSED

So I'm trying to track down this issue in hopes that it'll save you folks the time when you get back:

This line:

!q && 1 == _.qA(n) && n.hasOwnProperty("resource") && (q = "resource");

In this file looks suspicious:

https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.en.Y_wrh8DxACY.O/m=auth2,client/rt=j/sv=1/d=1/ed=1/am=wQ/rs=AGLTcCOrxii_3Shdq8FvYwaX1-pLTZLNeQ/cb=gapi.loaded_0

I couldn't find the string "resource" in any of the other requested files. I went poking around though the methods and properties have pointlessly short single character names.

from browser-samples.

Sorry for the slow reply. Have you had any luck figuring this out? I haven't been able to reproduce the problem, and it seems to be something specific to your production environment. Are you loading the libraries the same way there?

from browser-samples.

Hi Erick,
If you'd like to review a live test environment register at jabcreations.net, post your user name here and I'll upgrade that account to have enough permissions to view the scenario. I'll also have JavaScript console.log before and after my fix so you have a bit more useful scenario to work with. I'll reply with further basic instructions late Wednesday afternoon (Eastern Standard Time).

from browser-samples.

Is this still an issue?

from browser-samples.

Very likely yes. I wrote the code so that it would work even if you guys fixed it. Please register an account at jabcreations.net (just a test domain) and I'll ensure that the code consoles what is going on. I'll upgrade your account once you let me know you've set it up so you have access for testing.

from browser-samples.

I'm personally not comfortable debugging code on your production site. If you can find a way to replicate the problem on the test page or domain I'd be happy to take a look.

from browser-samples.

Eric, the site is not producing anything and is simply a general test domain not used by any clients. Even if the whole domain did go down it wouldn't effect anyone. Additionally I absolutely do not have the time to create a dedicated test case. I've marked this bug as critical and have mentioned that lots of people have been encountering the issue without the insight to compare the JSON output being sent to Google's server. In addition to that I also pointed out the suspect code.

1. Register an account so I can grant it webmaster permissions.
2. Create an appointment request.
3. Go to the Appointments review.
4. Use any Google account you want to have the appointment request also added to a Google Calendar.

Here is the JavaScript that I implemented to work around the bug. For some reason GitHub's editing tools aren't working otherwise I'd format this post properly.

function gca_events_create(id,event)
{
 event = window.atob(event);
 eval('event = '+event);
 event.description = event.description.replace(/\\n/g, '\n');
 var request = gapi.client.calendar.events.insert({'calendarId': 'primary', 'resource': event});

 if (request.Zq.k5.body.resource)
 {
  for (i = 0; i < Object.keys(request.Zq.k5.body.resource).length; i++) {request.Zq.k5.body[Object.keys(request.Zq.k5.body.resource)[i]] = request.Zq.k5.body.resource[Object.keys(request.Zq.k5.body.resource)[i]];}
  delete request.Zq.k5.body.resource;
 }
 request.execute(function(event)
 {
  //gca_status_pre('Event created: ' + event.htmlLink);
  id_('appointments_'+id+'_h3').replaceChild(document.importNode(new DOMParser().parseFromString('<a href="'+event.htmlLink+'" rel="noopener" tabindex="3" target="_blank" xmlns="http://www.w3.org/1999/xhtml">&#10003; '+id_('appointments_'+id+'_h3').tag_('span')[0].textContent+'</a>','application/xml').childNodes[0],true), id_('appointments_'+id+'_h3').tag_('span')[0]);
 });
}

from browser-samples.

Thank you for your effort so far, and I appreciate that you don't have the time to invest in further narrowing down this issue. Unfortunately we have a policy of not debugging developers' code directly, and rely on our users to provide repro cases. At the moment you are the only developer reporting this issue, and the problem could be due to interactions with other libraries loaded in your application, etc. If there is an issue on Google's end it almost certainly is in the JavaScript client library, and it may make sense to work with that team going forward. I'm closing this issue for now.

from browser-samples.

I've posted this bug report here: google/google-api-javascript-client#482

from browser-samples.