I have successfully integrated Paypal Embedded Chained Adaptive Payment system.
I have been testing it in sandbox environment. On GOOGLE Chrome, when user initiates the payment procedure, a light box gets opened with a login button inside it, but once user clicks on that login button, user comes across with following message
"Please continue with your purchase in the secure browser we launched. If you don't see it, click on Go."
The reason for this is that Chrome blocks the paypal login pop-up window. End user would not be able to figure out that what happened. Most of end users would not be aware about that paypal login pop-up window being blocked. Can we do something here so that we can avoid that pop-up window and can perform whole operation inside the Iframe only ?
Is there any solution this problem ?
Will it get resolved automatically once we shall move to production/live environment?
Please help me out.. We are going live very soon!!
I have been playing around with this a lot today and I too encountered the same issue with the lightbox. HOWEVER after much fiddling and time I decided to just try expType="mini" and it worked flawlessly. I did find one site that managed to get chrome to display the lightbox method correctly, but it was only successful about half of the time. It seems chrome is very sensitive to popups and sometimes it can be fooled and sometimes not.
Anyway the solution I found that worked was to scrap expType=lightbox and just go with expType=mini - seems to work without any problems. In the back of my mind I'm a little concerned that future browser releases (in particular chrome) will have updated popup blocking code may soon block this too. I hope this remains working, but I don't have a great deal of confidence in it. Make sure you have the good old Express Checkout method as a backup.
Hope this helped.
Related
I am working on a project that needs a permission for user_link. Functionality that implements this feature is currently implemented on https://staging.meetmeinthe.bar/. I have fixed all of our bugs and made our app comply fully with the requirements. But, for some reason, one of FB reviewers keeps declining our submission, saying that our Login button does not work. We have tested our login functionality many times from multiple devices - it works. Why do we keep getting rejected? Any advices are welcome.
When you land on a web page, you should click orange "Login" button in the top-right corner to see it.
Thanks in advance for your time!
The solution was to contact support that verified the fact that everything was working correctly.
I've been trying to pay the 5$ fee to be able to publish a chrome extension, but I'm stuck at the dialog. I've successfully added my card and I'm also able to select it in the dialog but when hitting the "buy" button the page just refreshes and the dialog appears again. When taking a look at the console I can see that there seems to be an invalid adress (see image) Error in console
I know this forum isn't made for these type of discussions but I couldn't find any way to contact the team behind it and the website itself links to stackoverflow (more specifically the google-chrome-app tag).
I think this has been for over one week.
https://www.reddit.com/r/chrome/comments/c1strb/cant_pay_5_developer_fee_its_been_days/
https://support.google.com/chrome/thread/7999997?hl=en
https://support.google.com/chrome/thread/8312321?hl=en
Nobody knows what to do, nobody knows where to actually get help, nobody knows how to reach anyone that could properly fix this, not even google support employees...
I have my Facebook login process working on desktop and mobile, except for Facebook's inapp mobile browser (ios and now android). The issue is that if you call FB.login(), nothing at all happens. I assume this is because the inapp browser doesn't deal with popups.
I understand that a redirect auth flow circumvents the need for a login/permissions popup, however I have built a web-app, which means it is a pain to deal with storing the users current state at the point of signing in.
Does anyone have any good solutions for this?
Also I have tested many other sites login buttons through the inapp browser, and all of the ones I have tried so far don't work. Facebook has done a great job of breaking a large amount of sign up processes.
As stated in the comments, that seems to be a bug either in the Android FB- App or in the Android 5 WebView component. There is a bug report at facebook, but they are still working on it. The only solution i could find for now is to turn off the internal browser: http://www.androidpit.com/facebook-disable-browser
Because that action has to be taken by the user itself, it's no satisfying solution. Therefore i guess the only thing we can do at the moment is to stay tuned for facebooks fix.
Update
Facebook confirmed this is a bug. They are working on it. Stay tuned...
2nd Update
Facebook rolled out a patch. Works for me now.
I'm trying to create a page that requires visitors to 'Like' a Facebook Page before showing all the content.
The page with the like button is hosted on herokuapp.com but the URL to like is a Facebook page (ie. the host URL and the 'Like' URL are different).
I've successfully included a like button and I have subscribed to the edge.create event, and everything was working fine (I could write to console.log or run custom javascript) when clicking on the Like button.
However in the course of testing I've clicked Like/Unlike so many times that my site has now been flagged as potential clickjacking and the Like button now changes to 'Confirm' and asks the user to go through the Confirm dialog process.
I understand that I just need to accumulate more 'white' Likes and this dialog will go away eventually, but in the meantime it's causing me problems.
Basically, when I go through the 'Confirm' process in Google Chrome or on my iPhone, the 'Confirm' link never changes to 'Liked', the number of likes doesn't change and the edge.create event doesn't fire.
Has anyone else encountered this behaviour? I've read just about every post on Stack Overflow relating to either the Confirm process and edge.create but no one seems to have had this particular problem. I'd really appreciate any suggestions :)
I was able to resolve this problem by moving my app to be hosted my own domain instead of heroku, even though I was liking the same page. Not an ideal solution for everyone but it worked for me. In future I will create dummy apps and pages to test this process out.
Javascript authentication works great on browsers but once I use the website on mobile, I always get this error on the login popup.
Sorry, the application you are using is misconfigured for Facebook integration. Please download the newest version of the application.
Instead of showing the usual login popup, it goes to m.facebook.com and it produces this error. Whats interesting is clicking on the spanish link, makes it work again.
--EDIT--
After doing some research and tinkering, ive nailed it down to this:
<fb:login-button registration-url="http://www.example.com/page#register" onlogin="authenticate.facebookLoginCallBack()"></fb:login-button>
Its possible the pound sign blows it up. I need the pound sign because i dont want to redirect off the page,instead i want to trigger a js registration popup.
My guess is that the # gets into the redirect-url, and then must somehow get transformed again on its way to getting redirect to m.facebook.com and that makes it fail there.
--EDIT--
I thought about redoing the flow by creating my own button and calling FB.login, but there is no way to tell the API to stop at login, and load my own registration. The problem is summed up here Registration flow using FB.login
Realistically it seems we are only provided with one option here:
https://developers.facebook.com/docs/plugins/registration/
Login + Registration Flows
and it doesnt work in my situtation
VISUALS
Typically the user clicks on this button
Then they see this dialog. (Notice it says www.facebook.com in the url)
But they see this dialog on mobile. (This is loading from m.facebook.com)