We have used branch.io links in facebook posts and updated the target website after the facebook bot visited the website.
When we used the facebook sharing debugger to trigger the bot again, it turned out that the html code that bot received was still from the old version of the page.
We tested our site using curl on the target website url, and confirmed that the website was updated but facebook going via branch.io link didn't see the new content.
Also, when using the branch.io link with curl we didn't have any issue seeing the new content.
However, we did notice, that the results of the curl call differed quite a bit to what the facebook bot received from branch.io for the same url.
Branch.io did not only return old information to the bot but also rewrote some of the html (the latter is fine and expected).
The following is unclear to me:
How long will a page be cached by branch.io ?
Are (some) Cache-Control values respected ? I tried Cache-Control: no-cache but that didn't seem to influence the caching behaviour
Is there a way to force invalidation for a link ? I couldn't see any UI in the Branch.io dashboard.
Related
I have created an App in https://developers.facebook.com/apps and I have one Facebook page, in that I have created ads and I got some leads, those leads I can see in Leads Center in respective page.
So I need to retrieve this Leads into my server.
When I run this below API in browser excel file is downloading directly and I can see all my leads in that file https://www.facebook.com/ads/lead_gen/export_csv/?id=XXXXXXXXXXXXX&type=form.
By using my App(which I created in developer) done some setting and I created webhook for user,pages and permission, in permission I can see lead_retrival, ad_reads and I have tested, those tested leads are coming into my server by given webhook URL.
But how can I get my actual leads which is in Lead Center belongs to my page and is there any APIs are available ?
Is APP review necessary to retrieve leads from form or any other option(I tried Zapier but that is not I am looking for).
what I tried:
I am working on my server so I went through with this link PHP cURL to verify Facebook API login access_token on server?, and created all access tokens by my app and I am getting Success. Login is valid
then I did not understand next what I have to do.
Can any one help on it please?
Thanks
Sandeep
I'm using appgini to create some views on tables. One option is to have an Google maps field.
The strange thing I'm seeing is that the iframe generated by this application is looking good, but I'm getting an error like
The Google Maps API server rejected your request. This IP, site or
mobile application is not authorized to use this API key.
But when I'm copying the generated iframe to a separate html file (on same website) it is working fine.
Example of appgini http://www.cs010.cc/Test/Oefeningen2/Oefeningen_view.php
Example (with exact iframe): http://cs010.cc/Test/test.html
Hope someone can help me with this.
It had to do with the http referrers for the Browser API key.
I changed it to .cs010.cc/ (previously it was http://cs010.cc
Update: It appears Twitter has fixed this issue. Clicking the authorize button now works! Thank you all for the responses.
I have a UIWebView that opens and directs to Twitters Oauth/Authorize webpage. The user signs in with there Twitter details and authenticates the use of our application with there Twitter account. This process worked perfect before the release of Twitter 6.37 iOS application. What happens now is when the WebView detects https://twitter.com/oauth/authorize?oauth_token instead of staying in the WebView it opens the native Twitter application and dies. If you uninstall the Twitter application everything works as usually it staying within the WebView. How can I prevent this from happening? I want to stay within my UIWebView and not automatically open deep links. I have been reading about the new URL deep link changes in iOS 9, but not sure of how to stop them from my application to other native applications. Thanks for any help!
As a workaround, in twitter authentication screen we can use the Go button on iOS typing keypad instead of using the sign in button on web view until twitter fixes.
Please refer the attached screenshot link for clarity.
Screenshot for the workaround
I ran into this issue as well and figured out it was because my authorize endpoint was set to https://twitter.com/oauth/authorize?oauth_token="+oauthToken (I believe this was in the original documentation). If you add api as the subdomain: https://api.twitter.com/oauth/authorize?oauth_token="+oauthToken, it will no longer trigger the deep linking and load the twitter app.
My answer to this via a Xamarin question:
Unless Twitter removes/updates the apps section of "https://www.twitter.com/apple-app-site-association" to allow a bypass or a secondary oauth that is not in the apple-app-site-association file I do not see how you would do it. These files are signed and iOS handles them at an OS level.
I have not played around very much with the continueUserActivity delegate and the NSUserActivity object that is passed to apps launched from UNI links, but I do not see a way for the launched app (i.e. Twitter) to return control to the original app, and at that point the oauth call-chain would be broken anyway....
Unique. Unlike custom URL schemes, universal links can’t be claimed by other apps, because they use standard HTTP or HTTPS links to your website.
Secure. When users install your app, iOS checks a file that you’ve uploaded to your web server to make sure that your website allows your app to open URLs on its behalf. Only you can create and upload this file, so the association of your website with your app is secure.
Via: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html
I would report as an issue (bug?) to Twitter's Dev forum: https://twittercommunity.com
my first post after years of reading :P
I think that are some problem with the page of soundcloud https://soundcloud.com/popup_callback.html
My app uses the soundcloud api and work fine, but when my users try to connect with facebook and they are go from facebook to
https://soundcloud.com/popup_callback.html?returnTo=CALLBACK_URL
but it is not redirected to the callback url, only show a empty page.
Users need login in soundcloud in other window before to make login in my app.
Can be a problem my callback url? "http://domain.com/callback/"
I try it in ff, opera and chrome and diferents at S.O.
This seems to be a bug in the SoundCloud API (see Soundcloud: blank page with popup_callback.html when trying to auth using Facebook)
I was able to work around this by including display=popup in the querystring when redirecting to SoundCloud's OAuth2 authorization endpoint: https://soundcloud.com/connect?client_id=[my_client_id]&redirect_uri=[my_redirect_uri]&response_type=code&display=popup. This will force the mobile optimized display to show up, but fixes the Facebook login issue.
Note that I'm not actually opening a popup window, I'm just including this param when doing a client-side redirect using window.location='https://soundcloud.com/connect?...&display=popup'
I’m currently working with the Google Picasa API (C#) to display photos from public Picasa web album on my website.
The issue is that there is a delay (seconds to minutes) from the moment changes are done in web album to the moment it is reflected via API.
I need it to be reflected immediately: When new photo is uploaded to the album I need it to be displayed on the same time exactly in the web site.
It got even more interesting when I found out changes are displayed without delay when entering the URL (http://picasaweb.google.com/data/feed/api/user//albumid/) to IE9 or Chrome.
I have also tried to call the above URL via HttpWebRequest and set all no-cache headers, but it didnt solve the issue.
So, what is the difference between browsers request to the request done by the HttpWebRequest/API on this case?
Can anyone put me in the right direction?
Thanks
Just in case you haven't found out and might still be interested, I had the exact same problem (though in PHP) and it turns out that anonymous requests are delayed, while authorized requests are instant. Because your browser contained a cookie with your Google account, it counted as an authorized request and therefore was instantly updated. However, the request by the code was still anonymous.
The solution would be to make an HTTP POST to retrieve the feed, and authorize the request as described here.