Well, I am a new guy who is trying to develop a web application whose user are will be authenticated through Facebook. I am developing the application in MVC 4 .Net Framework.
As it’s internal programs are already done so I need not to do much coding. I have just put the API ID
and Secret Key
in the scope
OAuthWebSecurity.RegisterFacebookClient(
appId: "750397051803327",
appSecret: "**************************");
And here is my Application http://imgur.com/a/k4Vd0
My Application is taking properly the user permission from the user perfectly. http://imgur.com/a/bqzj5 but after taking permission it is not providing the login state of the user by showing such exception http://imgur.com/a/h81Oh login failed. I debugged form the code end and I observed that it is sending isLoggedin as false http://imgur.com/a/UuLIe therefore my I am not getting the access.
However 2 days before I am not getting such exception. I was getting data simply fine. Here is a snapshot of my previous data. http://imgur.com/a/Bc49F
I need that data again, but how? Is there anything need to change in my application dashboard? Possibly I have changed something in application dashboard. if yes then what is particularly that?
Another things I’m confused that what is the need for PRODUCTS? Do I need anything from the products for this special reason to get the data. If yes then which one shall I need and how to configure it to get back my previous systematic process in which I was getting data smoothly.
If I add App Center
from the PRODUCTS
I am obtaining two other secret keys like Account Kit App Secret
and Account Kit Client Token
Is that I need to use these keys for my requested case. For such login approval specific which Products
are need or nothing need at all from PRODUCTS
. I am so confused about it how to configure an application.
Please suggest me how to solve this problem in addition how to configure my application API. Thank you.
2
Answers
Yes!!!! I got the solution of my own problem. According to Facebook developers bug report all Facebook log is not working from 28th March 2017. They also let us know through their developers Facebook group. The post link is here.
According to Previous Answer I got my solution. In
MVC4
everyone write down theirAppID
andSecurityCode
. Due to change of facebook GRAPH API those previous links are broken. Consequently everyone need to change theRegisterFacebookClient
calss. But this class is a sealed class in the .Net library, so anyone can’t extend or overwrite it. As a result we need to use awrapper
class. Let us consider my Wrapper class isFacebookClientV2Dot3
therefore my class will beLook here you I have replaces all the API links by newer version links.
Now you need to modify your
Just use a wrapper class
Then all success. You facebook login will be back in previous state.
However you can face a new issue regarding this new API rather than previous API, the problem is that
IP Whitelisting
. Like this image. Hope you will need nothing but this. Happy coding.