Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick
Related
I have been banging my head against a wall for the last two weeks. I'm trying to set up a contact me web page for my business. Having read all the warnings about mailto, I opted to use phpmailer for this. Similarly, I decided to use XOAUTH2 for sending the mail through gmail. I found several sites, including instructions at the phpmailer github page, that should have walked me through doing this.
Here's where I run into problems. After logging into the Google developer console, creating my project, and enabling the gmail api, all of the sites that I found talk about creating my new client ID. Every single one of them tell me that I will get a simple pop-up where I click that I want to create a web application, fill in a few items, and voila, out will pop my ID. When I did this, however, I was required to complete the consent screen before I could do anything else, and these screens did not match anything that was shown on the web sites I used as a guide. I muddled through as best I could and did finally get a client ID (I think/hope).
Does anyone know of a site or sites that walk a person through this in a way that matches what the development site actually displays? Did Google recently change things and the help sites haven't caught up? Having to guess at some of this is definitely not the way to do things. I'll be testing the results in a couple of days, but won't be surprised if things don't work right. At that point, I'll probably need more help to figure out what went wrong.
Thank you for listening to my rant.
I am having a strange issue that I think might be Chrome related but wanted to post here for thoughts.
I have some users who when trying to log into my node.js application, they press enter or the log in button and it just sits and spins and never times out or anything. When looking at the Network tab when this issue occurred the POST never showed up. I then put some alerts on the button click with javascript and as long as the button was in the tag nothing showed up.
Completely deleting the users' profile (suggestion from Google) made it work...until chrome updated and then it happened again.
Using any other browser, no issues. Chrome Beta, the issue shows up. Chrome Canary, I have had 2 users testing for over a week and they have not seen the issue reappear. Incognito has the issue occur as well.
Google Support asked me to send a HAR file to them. The interesting thing was when I opened up developer tools, went to the network tab and then cleared the screen to start a recording, the issue disappeared for that moment only.
It is working for 80% of my users so I can't see how it could be a coding issue, this is also a login that I created over a year ago and have not touched since.
If anyone has any insights I would love to know what might be causing this.
My Google Chrome Extension (Annotate for Chrome) has successfully received payments.
I have updated the app recently but not the payment flow.
Now when a user initiates a payment the Google modal pops up (that displays the Google payment - from Buy.js) the spinner just runs endlessly and console shows a 401 error.
I double-checked manifest and in-app purchase SKU etc and don't see any differences from previous versions that worked. My check for current license is working fine - which tells me my app is being recognized by the Google Web Store and returning data on specific users license status...
Any thoughts on what could cause this? Many thanks.
(I submitted a ticket to CWS support - nothing yet). Probably something stupid but I don't know how to debug. Or epic fail on Google's part.
The root cause of this issue has been fixed and purchase flows should be working as expected now. Details over here: https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/bxoptYk8--Y/Mh_qJp4gDQAJ
This is a problem with the Chrome Web Store.
I tried to purchase another Extension (https://www.twinword.com/blog/how-to-quickly-monetize-your-chrome-browser/) that uses in-app purchases and saw the exact same problem.
So Google's Web Store purchasing process has been broken for a week+ and no one at Google cares. Maybe they should get out of the payments business and require developers use 3rd party solutions. Utterly disgusting on Google's part. I'd like my 6 hours of troubleshooting back...
I am developing a little extensions called "Tab Bundler", which in short saves all the open tabs in a window into a bundle that can be opened with the click of a button. When a bundle is opened however, no history of how the user got to that url is saved, ie. the user can't click back to see how they got to that url. This is functionality I want to implement. I looked for a while, googling, looking thoroughly through the google chrome extension documentation: http://code.google.com/chrome/extensions/history.html. But I couldn't figure out how to get this information without tracking it myself. Is that the only option I have? Any thoughts would be really appreciated.
Thanks!
Look, many people tried this before. You are not alone in this quest!
At the moment the answer in Google Code was: anybody asked for it when they where developing the History API. Then there's no elegant way to access tabs' history.
Of course, you can hook chrome.tabs.onUpdated to record every page and make your own tab's history...
You could probably hook chrome.tab.onUpdate as well as some state or focus change hook to correlate.
I really want this, please make it!
I really didn't wanted to ask that kind of question in this resource, but I have no choice.
I have tried ask this question to Azure Support on Twitter, but they told me to open support case in azure portal itself. However, if you want to use their direct support, you must pay money.
MSDN forums does not allow me to post screenshots until it verifies my account, so this makes posting there useless.
When I want to add new Virtual machine I press Add button on Virtual Machines tab. Then it opens new tab with loading message and hangs. It says loading and then nothing happens.
I have cleared cache of my browser, opended incognito mode, still this happens.
I have installed another browser, opened portal and Dashboard still hangs at loading tab.
I have tried to open portal on my friends computers, problem still persists.
This is screenshot of this problem:
This is Javascript console:
According to this screenshot, Azure Portals Dashboard has javascript errors.
Why this is happening? Did I encounter some kind of bug?
As David said, it is not directly related to the forum, but there was partial portal outage, according to the https://azure.microsoft.com/en-us/status/. North America users were impacted.
Looks like that issue was mitigated.
If that is the helpful answer, please mark it as a helpful or as the answer. Thanks!