I'm building a very simple facebook application that just fetches a user's notifications from Facebook and also allows them to login. The URL is: http://widget.sidepage.co/_jump_frame.html
This works perfectly on Chrome - where the user is allowed to log in and authorize the app through a standard Facebook popup and once the app is authorized, it works well.
The problem is, on Firefox, clicking on the Facebook icon on the widget only opens a blank tab. There are no popup blocker warnings or JS errors thrown at the console.
Any pointers on how to fix this?
oh dude easy fix this is a Defining document compatibility issue...
and for what exactley you will need i suggest doing exactly what I did to find out what your issue was run your app in firefox 16 and request to view the page source and observe the mark up as it is rendered to firefox and then do a little research on what it is that firefox 16 needs as far as a compatible input to run your code. It shouldn't be too bad. Best to you.. A few other sources. On this topic and legacy compatibility.
helpful link
helpful link
hope that helps dude :)
Related
When I start a debugging session on VSCode, it opens a new Chrome window and loads my web app. My web app requires the user to sign-in via Google to use.
When I try to sign in, I get an error saying "This browser or app may not be secure". There is no option that allows me to bypass this and sign in. Does anyone know a way around this?
There is a Bug filed with Chrome Team.
https://bugs.chromium.org/p/chromium/issues/detail?id=1173641
Also here's the issue on github of VS Code
https://github.com/microsoft/vscode-js-debug/issues/918
As of now (9th Jan 2022), the only solution is to use other browser or use different way of Debugging.
Logged into the correct google account turning on "Less secure app access" on https://myaccount.google.com/security should work
From google support: https://support.google.com/accounts/thread/22873505?msgid=24501976
I have a link on my web page that links the user to a certain application in App Store. But when the user clicks on that link, the browser throws an error saying "Failed to load page. Unsupported URL" I have tested this on various iOS device and this problem is observed on iOS devices that came out before iPhone 7. Here is the link to the application : https://itunes.apple.com/ca/app/bounce-mobile/id1346771528 I am not able to find out what's causing this and how to fix it. Any help would be greatly appreciated!
Thanks
Still missing some of the details, but looking at your URL, it seems somewhat non-standard. I would use the Apple-recommended URL format of https://itunes.apple.com/app/id1346771528
Other than that, I would make sure you do not have the App Store disabled on the devices through something like mobile device management (MDM). Make sure you see an App Store icon on those devices and can open it.
In addition, I would plug the device into your Mac while trying to click on the link and use Safari debugging to see if you get more information - more details here.
I'm trying to allow a user to login to my webapp via facebook login using the javascript SDK. It works on desktop (safari and chrome), however the pop up fails on both safari and chrome on iOS.
The error is straight forward to chrome where the browser and OS are not supported. This issue has a work around described here. It is less clear what the issue is with safari and not seeing the pop up. The login call is called on a button click so I don't believe the browser should block it. I also tried allowing pop ups as suggested here but that solution did not work nor is it a viable long term solution to force users to change that setting.
How do folks use facebook login in production and expect it to work on mobile? Do you need to use the manual fb login? It appears that the javascript SDK doesn't work well with mobile browsers and OS's.
This is common issue among mobile browsers and you will find that it would also be in some android devices.
For precaution it is under best practice to build flow of login manually.
Go here as your link.
So yes, you will need to go with manual integration. But, it will be full-proof integration without doubts.
I'm currently looking at the Microsoft Live JavaScript SDK (OneDrive mostly) and I'm having some problems with the OAuth login process. I am using the examples found on MSDN pages to log-in/authenticate but there is something weird going on.
Whenever I do WS.init() my page refreshes... and when I call the same function again I get the popup window I expected. I click to accept, but the popup does not close and instead load the page which I came from.
I normally would expect no redirect here at all and the popup window should just close normally leaving me on the page from which I came.
I have ensured that my redirect URI (account.live.com application settings) is the exact same as the hostname I am developing this thing on. I faced a similar problem with dropbox.js's OAuth process, but that was simply solved by adding a OAuth reciever page. So I get the feeling that I'm missing something here. Anyone else familiar with how this works ? I'm having trouble finding any info on this.
After some more digging I finally found my answer. Turns out Windows Live SDK has the same solution as dropbox.js (which I mentioned in my question).
I'm implementing in-app purchase for an Android app from within a web view. The purchase is meant to be completed via Amazon's MP3 app. If the user does not have it installed, I want to open the Market app so they can download it before attempting to complete their purchase.
According to the official Android documentation, the following JavaScript should work:
window.location.href = 'market://details?id=com.amazon.mp3';
However, when I call that, I get a view that is blank except for a link to that link and half an upside-down Android dude poking out the top left of the view (you can't make this stuff up).
Anyone know why this might not be working? I've tested it on multiple handsets all running Android 2.1 and above. TIA for any help!
UPDATE: Thanks to #jtkendall on Twitter for this post that talks about how this behavior changed recently. Looks like this has to be implemented in native code.
Use the Http variant.
http://market.android.com/details?id=com.amazon.mp3
http://market.android.com/details?id=