Error while uploading content for Google Assistant Actions - google-sheets

While trying to upload the content via Google Sheets URL I am getting the following error:
Authentication failure. Parameter: popup_blocked_by_browser
How can I fix this?

Removing blank rows with notes from the sheet resolved the problem.

I turned off pop-up blocking and it worked.
To turn off pop-up blocker, follow these instructions:
Click the Customize and control Google Chrome menu (the three
horizontal bars in the upper right corner)
Select Settings.
Click the Show advanced settings... at the bottom.
Under Privacy, click the Content Settings button.
To disable the pop-up blocker check the Allow all sites to show
pop-ups box.
To enable pop-ups on specific sites, check Do not allow any site to
show pop-ups (recommended) and click Exceptions and enter the
URL(s).
This helped me to resolve this issue

Related

Why Won't Firefox Add-on Browser-Action Pop-Up Close?

I'm working on a Browser extension/add-on. We have it working in Chrome, so I'm trying to get it working in Firefox.
I've only gotten my extension to load in Firefox Developer Edition 49.0a2 (2016-07-25) (I'm not sure why it doesn't work normally, but have asked elsewhere).
My add-on uses a browser_action to add a button to the toolbar and open a pop-up, which opens fine, but once it's open, it seems impossible to close without quitting Firefox entirely.
In fact, it's so pernicious, the pop-up then appears over other applications!
Is this just a current bug in Firefox, or is there a way for me to fix this?
You might have accidentally clicked the "only close the popup on ESC" button in the firefox debugger, which keeps a popup open until you press Escape. Source: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Debugging#Debugging_popups
IF your browser extension popups (and right-click context menus, bookmark menu etc.) persist and refuse to go away unless you press Esc AND you have the ’Browser Toolbox’ window open—then you have probably left the ‘Disable Popup Auto-Hide’ option enabled. (This setting is only in effect when the Browser Toolbox window is open.)
To disable this setting, go to the Browser Toolbox window (the window title is ‘Developer Tools – Debugging’), then, in the upper right-hand corner, press open the three-dots menu, and uncheck ‘Disable Popup Auto-Hide’. (If checked you get sticky popups/context menus. If unchecked the popup/context menu will close if you click outside it).
Browser Toolbox
NOTE: If your browser menu does not have a ‘More tools > Browser Toolbox’ option, then the Browser Toolbox is disabled, and cannot be causing the sticky popup behavior.
The Browser Toolbox window can be opened through the browser main menu (the little hamburger icon, rightmost in the URL bar of the browser) ‘More tools > Browser Toolbox’ (or Ctrl-Shift-Alt-I).
The Browser Toolbox is disabled by default, so, for the above paragraph to work must first be enabled. To do this click on main menu icon, then ‘More Tools > Web Developer Tools’ (Ctrl-Shift-I), then, in the Developer Tools frame (or window) click the three dots menu icon (top right) and select ‘Settings’.
In the settings, scroll down to the bottom right (under the ‘Advanced settings’) and check the last two options:
[✔️] Enable browser chrome and add-on debugging toolboxes
[✔️] Enable remote debugging
Your browser menu should now contain the ‘More tools > Browser Toolbox’ option. (From the MDN Web Docs ‘Enabling the Browser Toolbox’.)
This answer (just like #Lakinator’s answer) is based off of information found on Mozilla's official site.

iOS 9 Universal links Forward button breaks deep linking forever until I erase phone settings

Before anyone marks this question as a duplicate please read the extra section at the bottom that sites differences between this question and other similar questions out there
I'm utilizing Universal Links for my deep linking needs. Two example use cases are:
1.) Safari/Chrome Browser on iPhone with my app installed: When click on a link on my web site on their iPhone I'm deep linking them into my app if installed on their phone.
2.) With my app installed, running my app but using an in-app-UIWebView. My app also has an in-app UIWebView, when you tap a button it deep links them somewhere in the application.
After you deep link into the app, there are two buttons in the navigation bar. A Back button (top left) and a Forward button (top right).
My problem
If the user presses the forward button (top right) it forwards them to my web page and then will forever break my deep linking so that any time in the future when the user clicks on that link to deep link it always goes to my web page instead of deep linking into the app (which was the original intention). How can I prevent this? My concern here is that my app has close buttons in the top right corner and if the user is trying to hit hte close button they could accidentally hit the forward button and forever break deep linking. I've tried clearing my browsers caches, I've tried deleting and re-installing my app. But nothing will "fix" deep linking after it's been permanently disabled by the forward button. The only way I can get it working again is by doing a complete device reset and Erasing all Content and Settings.
Here is an image of the back and forward buttons after deep linking into the application.
Difference between my question and similar questions on SO:
Similar SO question But here they are saying that the user can long-press on the "universal link" and and action sheet pops up asking you to "open in ". I've tried this for above case 1.) and my app isn't showing up in the options. See attached screenshot below. And this doesn't work at all for above case 2.). How do you get a Universal link to work with an iOS WebViewController? Do I have to use the SafariViewController? I don't want to use SafariViewController in my app for this case because I don't want to have that top navigation bar that SafariViewController has.
You're absolutely right: the forward button is horrible UI/UX. It's one of the big flaws with Universal Links identified in this blog post. There is no way to disable the forward button, and once it's triggered, you're screwed.
The easiest way to re-enable Universal Linking behavior after it is turned off is to long-press on the link. But that doesn't work if your link is being disabled by the system based on some other criteria (more details below). Your best bet at getting a clean shot is to paste the Universal Link URL into the stock Notes app and try long-pressing it from there.
To answer a few of your other questions:
Universal Links do work within UIWebView (per Apple's docs). A SafariViewController is not necessary.
Universal Links are disabled at the system level in certain situations. There's a list here, but this the main one that comes to mind as potentially applicable in this situation:
Universal Links will not work with a user driven element click on the same domain. Example: if there is a Universal Link on google.com pointing to a different Universal Link on google.com, it will not open the app.
Your second example image is from Chrome. Universal Links should work (conditionally) in Chrome, but is the link pointing at the same domain as the page you've already loaded? If so, that's why you aren't seeing the Open in [app] option.
You cannot disable the button to open the website, but you can create a path in the other direction: Use a smart banner on the website, and when users tap "Open" (or the localized equivalent), they will be taken back to your app, and this will also reset the default to opening universal links in your app instead of Safari.

How can I reset iOS 9 Universal Linking settings?

While testing universal links on my iOS 9 app, I accidentally tapped "mywebsite.com >" (top right corner). This made the app navigate to the website again. Now I can't seem to make universal linking work again. Seems like iOS has remembered my preference that I would like to see links opened in Safari as opposed to my app.
Has anyone run into this? Is there a way to reset this?
You can long-press on a universal link and it will give you an action sheet with an "Open in 'AppName'" option. Once you select that option it will default to opening the links in your app again.
You need pull down in opened page in safari from email, etc to see button "Open" (this button is system in safari). If tap "open" after
I accidentally tapped "mywebsite.com >"
universal link will work again under the old scheme.The result of this action preserves.
example
#dan is right, long-pressing the hyperlink will give you the option to open with your app again through universal link.
If you have an Apple Smart Banner in place, you can also click on its 'Open' hyperlink to active universal links on your app again.
For a Branch.io deep link the long tap (at least in GMail) does not work and also you can't pull down from safari, it brings you to the App Store immediately.
Instead, copy the link to Notes and then do the long press.
More info here: https://blog.branch.io/3-steps-to-troubleshoot-ios-9-and-ios-10-universal-links/

The infamous "sticky" :hover on iPad - how does Google fix it?

I have unfortunately stumbled on the issue where, on iPad, a pop-up menu summoned by way of :hover does not disappear from the screen when the user touches an empty area of the page.
The problem is the same described here:
Hover Behavior on Desktop vs iPad
The menu is part of a template I bought, namely:
http://html.realia.byaviators.com/
But... wait a minute... it WORKS on the template's home page? And only on that page -- it doesn't work on any other page of that same template.
I was able to track the behavior down to the point where I found that the reason why it works is the following: initializing a Google map makes the menu behave properly. Just the simplest of maps, with the default options.
Now my question to the experts is: what is that Google does in the map initialization code in order to fix the :hover behavior?
Thank you very much in advance for your help!
Well, can't tell what is that Google does, however the solution is documented in mobile Safari developer's reference.
For a click event to be generated on an area of the document, there must be a click handler attached. For example, clicking on a div will generate a click event only if an onclick="void(0)" handle is presente:
Clicking here triggers event in mobile Safari

How do I remove an attachment on a Jira ticket?

The permission "Delete all Attachments" is granted to the group "jira-users". I am member of "jira-users". Though, I do not see a way to remove an attatchment (a screenshot actually).
I am by no means a JIRA expert, but on our instance (v4.2.4-b591#591), there is a drop down arrow next to the "+" icon to add an attachment. In that drop down, there is a "Manage Attachments" option. You should be able to figure it out from there...
As of October, 2015, it's changed a little and I thought I would post a new answer since this is the first Google result!
According to a forum post, the only way to remove attachments is to open the issue in the "Issue" view and not the "Projects" view, click on the issue, scroll down to the attachments, and then hit the trashcan icon when scrolling over the image.
Source: Jira Forum
It's not directly possible in the greenhopper detail view. You first have to open the issue in the normal JIRA issue detail view through clicking on the issue key in the greenhopper detail view. In the normal JIRA view you should see a trash can icon if you hover over an attachment. If not, you should check your permissions

Resources