I am developing using ios obj-c. I am trying to get the access token using google GTMOAuth2 library. I could do the "work with nest" login but the redirect doesn't seem to work.I see nest animation and it keeps spinning. I have set the redirect to "h..p://localhost" on the Nest Developer Client settings.
How do i get the redirect correctly?
Or
How can i get the redirect to my App itself
We've added sample code for iOS over here. To see how we got the access token from the redirect url have a look at NestWebViewAuthController. Let us know if you have any further questions!
Cheers,
Raymond
It sounds like the WebView is timing out trying to load localhost since you like don't have a web server running. On iOS the best practice would be to insert a listener into the WebView that is called when your redirect URL is loaded. See Get notified about a page change in UIWebView
Related
So, I am trying to implement a SharePoint intranet site for an organization. However, there is one application in particular that they would like a link to on the homepage. Unfortunately this application can only be used via the IE tab google chrome extension (I know, dumb) but app devs have yet to add chromium compatibility.
Any way the link looks like this:
chrome-extension:
//hehijbfgiekmjfkfjpbkbammjbdenadd/nhc.htm#url=https://website.com/sub/sub.Hub.aspx
But share point requires a https:// on the beginning of a link.
If you throw that destination into chrome directly it navigates fine, but if you add say https://google.com/ on the front or https://*/ it doesn't work.
Is there a syntax that will allow me to put https:// on the front of this without getting a 404 error?
Never mind, I ended up re-directing this through IIS internally
I have a checkout page written in PHP that uses affiliate tracking.
Many affiliates like to advertise via Instagram.
When using the Instagram In App Browser on mobile phones anything within the code that relies on the $_GET variable is failing as it never seems to have any available data.
Thoroughly tested and issue is specifically with the Instagram browser, Facebook browser works as expected.
I can detect the Instagram browser ok via User Agent to do a bit of damage control but don't have a full working solution.
I attempted to force my page open in native browsers on the phone but couldn't get it to work, it was just refreshing the page In-App.
I've attempted loading scripts in iFrames to get needed data but those seem to be blocked as well when going through the In App Browser.
Open to any suggestions.
This resolved the issue for me.
WP Engine host Redirecting Bots
WooCommerce Checkout Issue specific to Instagram In-App Browser
I'm trying to track from where my links are clicked.
Exemple I place a link to my website on facebook, instagram, linkedin.
I would like to know where my link is clicked most of the time.
bit.ly does it and I don't know how.
One of my ideas was to identify links like
www.exemple.com/facebook_url
www.exemple.com/instagram_url
but if I can avoid this it would be perfect.
Any idea ? :)
I found how !
req.headers.referer;
give me the url used to redirect my user :)
The simplest way to do this would be to set up a web server with redirects and analytics already built in. You could also build your own analytics using a redirecting html + js
If you have access to a webserver, you could use PHP to do a conditional redirect.
I have set my redirect uri to something like this:
../index.php?r=spotifycollegeplaylists/tab/index
I was able to setup the login using this example
https://github.com/jwilsson/spotify-web-api-php
The login is working fine, I can trigger the login popup and I am able to login. Now the problem is with the redirection. After logging in I am redirected to this URL:
../index.php%3Fr=spotifycollegeplaylists/tab/index&page=index?code=AQCtOWUzHM
See the problem with the redirect is that it has two "?" If i manually change %3F to ? and ?code to &code, the links is working okay.using the method from the API above how will I be able to fix this issue?
I've made a query on the Spotify Web API site as well, and I got a feedback from one of their support team / developer.
"I understand your issue and I would recommend that you don't have any query parameters in your callback URLs. We have a known issue in that we don't allow the Redirect URI to include parameters and hopefully this will be fixed soon. Meanwhile, you could use the state parameter that you'll get back when the code is returned through the callback."
I've recently began learning AngularJs for web development and am loving it so far. However, I'm not so sure about having hashtags withing the link when routing between views. My main concern is how Google will cache the pages on the site and whether the links will work both ways, i.e. whether users can just click www.sampledomain.com/#/orders/450 and be directed straight to the order page. Is this an okay method or is there a way to route views without the hashtag?
When I remove the hashtag, the reload the page and gets 404 error. Can anyone give me a decent explanation of what is going on. Thanks
When I remove the hashtag, the reload the page and gets 404 error
That's because in your server side code you are probably not handling a request like "www.sampledomain.com/orders/450"
You can have your server-side code handle this request by either returning a redirect to the new URL ("www.sampledomain.com/#/orders/450") or just return the correct HTML directly. The "right" solution will depend on your needs.
User can just click link with a hashtag and it will be directed straight to the order page.
Google treats links with hashtags as different URL's when the content is different. It's more about SEO then angular.js, but here is an article about that: The First Link Counts Rule and the Hash Sign - Does it Change PR Sculpting?
You might want to set Angular's $locationProvider to use html5Mode.
FTA:
$location service has two configuration modes which control the format of the URL in the browser address bar: Hashbang mode (the default) and the HTML5 mode which is based on using the HTML5 History API. Applications use the same API in both modes and the $location service will work with appropriate URL segments and browser APIs to facilitate the browser URL change and history management.
html5Mode will give you "normal" urls in modern browsers while falling back to hash bangs on older browsers.
An html5Mode url:
http://foo.com/bar?baz=23#baz
a hashbang url:
http://foo.com/#!/bar?baz=23#baz