Just these past 2 days, all of the iOS users have complained that they are hitting a Page not found from their Facebook APP built-in browser to my site. It's been quite stressful for me.
The URLs have Chinese in them, and have always worked until these couple of days (I suppose when the built-in browsers started to work).
Any way to fix this? Thanks!
We had similar issue. In our urls we have hashes (#) when we remove it from shared links it works normally.
Question is why facebook built-in browser doesn't like hashes?
It can be connected with release new version of facebook app on iOS systems which was pushed on 29th August.
Related
Edit: Turns out the Uber app was botched - see answer below. Leaving this post as a reference for others.
I noticed that universal links I'm generating don't work reliably - I first thought it was only Android, but I'm also seeing this on iOS now.
Links like this one below just open in the browser when triggering the URL to be processed by the system (I removed the detstination and formatted addresses to get a minimal link, but it's still not working):
https://m.uber.com/ul/?action=setPickup&client_id=MY-CLIENT-ID&pickup[latitude]=47.5045573061129&pickup[longitude]=8.71492590755224
This is a Xamarin app, I'm just using the built-in Device.OpenUri(uri) method, which translates into a native call. That used to work in the past...
Turns out my Uber install got botched. I uninstalled and reinstalled Uber, and now the links are working again. Weird, but I'll just pretend that didn't happen ;)
I thought I heard a rumor that the chrome.fileSystem app API is going to be deprecated in Chrome in the near future. I already searched Google but could find nothing about it. Does anyone know what the status is on this API and whether I can expect to be able to use in the future?
Turns out I missed seeing the announcement at the top of the Chrome Apps pages until after I posted this question.
https://developer.chrome.com/apps/api_index
Chrome will be removing support for Chrome Apps on Windows, Mac, and Linux.
This will be completed in the spring of 2018. The app store will stop showing apps in the fall of 2017.
I have been going back and forth with my dev teams today to determine an issue that has come up. It appears that links shortened by bit.ly are not being directed to the proper URL on mobile devices only. This URL http://bit.ly/1aRvnqH will take you to the appropriate place on a desktop computer, but put it into a mobile device browser on your phone and it is broken. The URL that the mobile device renders is a very old link from our old web structure from more than a year ago.
Further it is appending a GA tag for our affiliate program platform as well as a reference code that does not exist in our affiliate program.
My dev guys think it may be something to do with this new deep linking on mobile that bit.ly recently rolled out. When I called bit.ly, they said they've never heard or seen of this before and asked I send an email to their support group which I've done.
Was hoping someone here may have some ideas as well.
Thanks in advance.
Brian
DISCLAIMER: I'm a developer at Bitly
This is a bug caused by our on-going affiliate test.
We're pushing out a fix for this link now and it should be working properly within the next 30 minutes.
If other links stop working for you in the future, please contact us at support#bit.ly or http://support.bitly.com and we'd be happy to look into it.
We use FB JavaScript SDK and we're loading it asynchronously, according to their docs:
https://developers.facebook.com/docs/reference/javascript/
We use it to handle the login and for some basic calls to their API (mostly to publish stories and share links):
https://developers.facebook.com/docs/reference/javascript/FB.login/
https://developers.facebook.com/docs/reference/javascript/FB.api/
Since we started using it, we have experienced different issues on some browsers and devices.
As an example, yesterday we experienced problems trying to post on the user's feed from an iOS device (FB.api('/me/feed', 'post'...)), this problem lasted several hours. Earlier, we experienced problems in other platforms such as IE.
It seems like FaceBook pushes changes to their SDK without testing properly on a wide range of devices.
My questions (not easy questions, I believe):
Have you experienced similar problems. Do you think it is reliable?
Is there any realistic alternative to it?
I've always used the JavaScript SDK and it's been fine. Sure, there are issues from time to time, but that's part of being a Facebook developer.
The only alternative I can think of would be the PHP SDK. Both should be equally reliable.
I have recently wired up my application to use the Facebook iOS SDK (http://github.com/facebook/facebook-ios-sdk). The integration works fine, but the pages loads really slow. It takes really a long time to load the login screen. Login action takes more than 10-60 seconds.
I didn't have this problem with Facebook Connect. Am I missing something? Is there a way to optimize this?
Update
I did scan the activity through HTTP Scoop over Wi-Fi which revealed something interesting, there are some .js and .css files that are taking a lot of time in the new Facebook iOS SDK (login.php, ar7ed2ft.css, 4wj242ne.js, abl6sgyy.js,) where as the old one was zippy. How to let Facebook know about it?
New Facebook iOS SDK
Old Facebook Connect
Implement OAuth 2.0 yourself. It just uses HTTPS, extremely easy to implement. In my experience, it was easier than using their confusing, document-less SDK. Important is getting authentication token. You can access all their graphs with it.
If you implement it yourself, you can choose login screen dialog design as one of:
touch
WAP
WAP is uglier because it's for older phones, but if you really need it, it may help you.
Try using this one http://github.com/facebook/facebook-iphone-sdk