I have created deployment for App Maker app, with URL https://script.google.com/a/macros/domain.com/s/AKfy..adwq/exec
Also enabled "Allow app to be embedded in any site within an iFrame" option in App Settings.
But when inserting on website:
<iframe src="https://script.google.com/a/macros/domain.com/s/AKfy..adwq/exec"></iframe>
app is not displayed, and this error is in dev console:
Refused to display 'https://www.google.com/a/domain.com/ServiceLogin?passive=1209600&continue=https://script.google.com/a/macros/domain.com/s/AKfy../exec&followup=https://script.google.com/a/macros/domain.com/s/AKfy../exec' in a frame because it set 'X-Frame-Options' to 'deny'.
As I understand, because App Maker app requires GSuite account to run, it redirects to different Google's authorization URL first.
But I don't understand why this URL is banned from displaying in iframe, and how it is possible to embed App Maker app then?
Related
On the high level, I have a PWA with React frontend and .netcore backend. I use service worker for caching and offline ability, in conjunction with workbox plugins for some precaching feature.
The app uses Windows Authentication. Which works fine if it wasn't a PWA app. It also works fine the first time the PWA app launches, I get the username, password login popup.
However from the second time visiting the app, it wouldn't show the login popup, the app fails at pulling data from the backend because it is unauthenticated. One weird behavior is that, if I open Chrome Dev Tools(by F12), then the login popup immediately shows up.
I thought it's caching related and somehow the service worker interfered with the server side authentication workflow. Maybe because the index page is cached by the workbox precache plugins, and it did not cache with the fetch header of 'credentials': 'include'? I tried adding the fetch option to other api routes, which are cached by workbox plugin RegisterRoute. However I didn't find a way to add it to the precacheAndRoute(self.__WB__MANIFEST). Wondering if that's the problem. But I'm also not sure why having Dev Tools open would trigger the popup to display.
Any input is appreciated.
I would like to use Firebase Dynamic Links to open the email verification message in the app by tapping the link sent by email.
In the Dynamic Link created, the package name of the app is given so that the app can start when the link is tapped.
My question is : do I need my app to be in the PlayStore so that the app can be recognized and opened, or can I test the dynamic link app opening even if my app hasn't been published.
You can test dynamic links without having the app published in the stores. It just has to be installed on the device of course.
I've a Wordpress PWA based on https://wordpress.org/plugins/super-progressive-web-apps/ .
The users of the app can scan a NFC-Sticker which open a Deeplink and pass an ID to the App e.g. https://myapp.domain.com/id=1234
Unfortunately sometimes the PWA did not open in the standalone mode, which is defined in the Manifest. To force this, i've integrated a php header redirection which open the PWA in most cases.
Any ideas?
I don't see any option for Web under "receiving dynamic links" in Firebase Dynamic links page.
Without the SDK, there's no way to connect a post-install user with a pre-install click.
I have a desktop app that runs on node.js like a web app, using nw.js. What I'm trying to do is create referral links for users. After someone clicks a referral link, I need to be able to track his referrer. But the problem is that link is only going to take him to the download page, after he downloads and opens up the app for the first time, how can I reach his referrer info? The desktop app has no connection with the website that users download from.
I understand that this can be done with Dynamic Links SDK but can I use that SDK in a web app?(desktop app actually but runs with HTML/node.js)
The post-install deeplinking in Dynamic Links is just for Android and iOS - so there isn't an equivalent for a desktop app.
I have a meteor app running in a node.js machine on nitrous.io and the facebook authentication is not working. I created a new app in facebook, added Website as platform, set the App domain to machinename.usw1.nitrousbox.com and the Website's Site URL to http://machinename.usw1.nitrousbox.com (machinename is made up, but I have my own site there) and then I used the public & secret key to set the fb auth in running meteor app. This is all similar to how I've setup apps before, yet when I try to login to this nitrous.io app using fb, I get this from facebook:
Given URL is not allowed by the Application configuration.: One or more of
the given URLs is not allowed by the App's settings. It must match the
Website URL or Canvas URL, or the domain must be a subdomain of one of the
App's domains.
I've tried all different kinds of settings. Any ideas?
There are two ways to solve this.
Option 1:
Meteor looks for a ROOT_URL environment variable to determine the url the app is running, which is http://localhost:3000/ by default. You can keep the setting as is, but you will need to utilize the following credentials within your facebook app configuration:
site_url: http://localhost:3000/
Option 2:
If you want to utilize your preview URL then you will want to set the site_url to it within your facebook app configuration:
site_url: http://machinename.usw1-2.nitrousbox.com
The next step will be to start up Meteor with the following command:
$ ROOT_URL=http://machinename.usw1-2.nitrousbox.com meteor
Alternatively you can follow the Meteor documentation to change your root URL.