I got this error on the Facebook page.
App not active: This app is not currently accessible and the app developer is aware of the issue. you will be able to log in when the app is reactivated.
Also, I was implement facebook login in the Laravel with "Laravel Socialite".
It's happened because your app on Facebook for developers website is not live
solution
go to Facebook for developers from here
choose My Apps from the top bar
click on your app icon ( then you will notice that your app is not live from the top bar )
from the left side select settings >> basic
put your privacy policy link in the Privacy Policy URL and in the User data deletion field, you can make a copy from this privacy policy ( to make a copy from the privacy policy select file from the top bar and select make a copy )
press save changes
I hope that it was helpful
The error suggests your Facebook app is not active; it should definitely be in Development Mode.
You get that error because the Facebook user account you are using to test the login with Facebook feature is neither added to your Facebook app as an Administrative nor Developer account.
You should check and ensure the Facebook user account meets either condition above.
Alternatively, you can change you App Mode from Deployment to Live, if you are ready to make it accessible to your users.
Go to developers.facebook.com/apps/your-app-id/app-review/permissions
Change public_profile to Advanced Access.
Thats all.
I created a static Web site using Azure Static Web Apps (under the Free plan for now -- not sure if that's relevant to the issue at hand.) I can access the Web site through an ***.azurestaticapps.net URL.
I then tried to test Azure Active Directory authentication per Microsoft's instruction from this page:
https://learn.microsoft.com/en-us/azure/static-web-apps/authentication-authorization
My problem is that logging out does not seems to work as I would expect on a normal Web site. I could log out, but when I tried to login again (hoping to use a different Azure AD account,) the Microsoft login screen flashes by and I got logged right back in with the user that I just logged out from. Switching to a different tab doesn't help.
Steps to repro:
Navigate to /.auth/login/aad and login using a Microsoft Account. Say NO to 'Stay signed in?' prompt.
Navigate to /.auth/me to see the basic information on the logged in account to prove that I'm in the logged in state.
Navigate to /.auth/logout to logout. Immediately, navigate to /.auth/me again to confirm that my static Web App regards me as 'logged out.' I'd see this:
{"clientPrincipal": null}
Navigate to /.auth/login/aad again. Microsoft login page flashes by, and I am logged right back in with the previously logged out user.
Things that sort of worked
Any of the two actions below alone seems to make the browser forget my logged-in state:
Close the whole browser and relaunch it. I'd get asked to pick the previous user (and then enter the password) or choose a new user. This sort of works but reminds me of some Web sites 15-20 years ago that said 'For security reasons, please don't forget to close your entire browser after logging out from this one tab.'
Open a new tab in the same browser, and navigate to hotmail.com. That tab will enjoy my logged-in state from the Static Web Apps tab. I'd see my mails right away. Then I log out from the hotmail.com tab, switch back to ***.azurestaticapps.net tab and see that I am still logged into my Static Web App. Good! Then if I log out from my Static Web App and try to log back in, it has forgotten my logged-in state this time. In other words, logging out from the hotmail.com tab is somehow more powerful.
I also tested /.auth/login/google too and the same problem arises! So the issue seems to be on the Azure Static Web Apps side, not how idPs handle their logout process.
Am I missing anything obvious?
I have a PowerShell script that is supposed to open the web login popup, since the SharePoint site requires MFA. The script opens the popup, however, it does not load the Microsoft login page content. It loads just a blank page.
After some hours of troubleshooting, we identified that this is due to the security settings of the Internet Explorer. When the Security Level Setting is set to High in IE, neither the browser nor the popup loads the login page(presume the popup also loads IE).
Due to server restrictions,it is not possible to change the IE settings to a lower level.
Is there any other way of using Connect-PnPOnline in MFA environments/connect to SharePoint Online using MFA
OR is there a way to specify the browser opened by the popup(Edge loads the login page without an issue)?
Found that IE was automatically logged in to our Intranet (SharePoint Online). Logged out of IE, and got the webdialog back again.
I had the same. What helped for me was running PowerShell under administrative privileges...
I understand that you are not able to lower down the IE browser security settings level.
I suggest you add the SharePoint site to the trusted site list and configure the User Authentication setting may help you to fix the issue.
You can refer to the steps below to add the site to the trusted site list.
Go to Tools(ALT + X)-> Internet options-> Security tab.
Click on Trusted sites and click on sites button.
Insert the site URL and click on Add button.
Click on the Close button.
You can refer to the steps below to configure the User Authentication setting.
In the Security tab click on Trusted sites and then click on the Custom level button.
Scroll to the bottom and find User Authentication.
Select the Prompt for username and password option for logon setting.
Apply the settings and restart the IE browser.
Then after again try to check for the issue.
I'm trying to make a login with Facebook available in my script. I've done everything, but when I attempt to login with a Facebook account I get this error from Facebook:
Error
App Not Setup: The developers of this app have not set up this app properly for Facebook Login.
Here's error screenshot:
Any ideas?
the problem was you have to set
Do you want to make this app and all its live features available to the general public?
set status and review to ON and problem solved
enjoy coding
With respect to the all the other answers, here's the screenshot to help someone.
Go to https://developers.facebook.com/
Click on the Apps menu on the top bar.
Select the respective app from the drop down.
The circle next to your app name is not fully green. When you hover mouse on it, you'll see a popup saying, "Not available to all users because your app is not live."
So next, you've to make it publicly available.
Click on setting at left panel. [see the screenshot below]
In Basic tab add your "Contact Email" (a valid email address - I've added the one which I'm using with developers.facebook.com) and make "Save changes".
Next click "App Review" at left panel. [see the screenshot below]
Look for this, Do you want to make this app and all its live features available to the general public? and Turn ON the switch next to this.
That's it! - App is now publicly available. See the fully green circle next to the app name.
Since the UI of the facebook has changed recently, here's the latest update for setting the sandbox mode ON/OFF :
Go to https://developers.facebook.com/
Click on the Apps menu on the top bar.
Select the respective app from the drop down.
Go to 'Status & Review' from the table in the left side of the page.
Do you want to make this app and all its live features available to the general public? - Select switch to set YES/NO value.
Update:
The YES/NO button will be disabled until and unless you provide your contact email.
Go to "Settings" in the left menu.
Update your Contact Email.
Hit the "Save" button at the bottom of the page.
Update:
'Status & Review' is replaced by 'App Review' now
If the app is still in private mode (Status and Review set to NO), then only Facebook users with role in the app can login.
That unless you set it to public (Status and Review set to YES).
To add more users to be able to login to a private app:
Go to https://developer.facebook.com
Go to Apps -> "Your app" -> Roles
Choose Add Administrator,Developer or Tester.
Many reasons including:
Sandbox mode is ON
Domain name is different
Site URL is different.
This error also occurs when you try to log in in your test version of the Facebook app and you have not added the user you are trying to test the log in with in the Roles -> Testers section.
To fix it, just add the email address of the Facebook account you are trying to log in with in the section above.
Finally, make sure the user you added accepts the request sent before you try to test otherwise the log in process will fail in the second screen just after the user accept the conditions.
Make Sure in left panel App review tab selected (Your app is currently live and available to the public.) tab is ON and App status is GREEN
Happy Programming
And addition to all these beautifull comments dont forget to Start A Submission
There are a bunch of possible things which could trigger this error:
In your case, you just need to add your facebook account into either tester, developer or admin of your facebook app as you want to use that account to test.
But if you see the error upon clicking connect to facebook(before you have chance to enter facebook credentials), then it means your current facebook account detected from cookie is not a valid tester/developer/admin account for your app.
Your could either add your account in or just hit facebook.com and sign out(to remove the undesired cookie).
I had the same problem but now here is how I solved it
Go to https://developers.facebook.com/
• Click on the Apps menu on the top bar.
• Select the respective app from the drop down.
• Click Settings from the table in the left side of the page
• Then under the Contact Email type in your email you would like to use
• Then click save settings button
• Go to 'Status & Review' from the table in the left side of the page.
• Do you want to make this app and all its live features available to the general public? - Select switch to set YES/NO value.
For other users that run into this issue, the app I was testing against was a test version of our production app and didn't have the option to turn status and review to ON as others have mentioned here.
The fix was to create a new app which is not a test app, and configure it like the production version. The non-test version allows the option to turn status and review to ON.
My specific use was testing a user registered with a phone number instead of an email address. I tried adding that user into different roles of our test app (Developer and Tester), but to no avail. My guess is it has something to do with the user not having an email associated with it.
Here's more info on test apps: https://developers.facebook.com/docs/apps/test-apps
Hemang's answer was right, BUT, there's one extra step you'll need, which is to add a Facebook App ID. (I discovered I was missing this part):
Once you've done that in addition to Hemang's answer, you'll be good to go!
Okay - sandbox is off, domain has to be correct because 99% of the users can reach the app, and "all its live features available to the general public" is set to yes.
Now, You need to add a "Privacy Policy URL" in the App Details tab (developers.facebook.com).
This is a new Policy of Facebook.
This resolved my issue if you do not want to make the app available to the public (keeping Status & Review on NO)
I had to sign out of the previous account on the Facebook App and also remove the Facebook account in Settings. Removing just from the Settings will not remove the error because the App itself still has the previous account logged in.
If you have set your Roles as Administrator/Developer/Tester, you can put in that account login info in and it should work then.
do setup by following bellow link and domain name you need to mention as like wht you have mentioned in facebook app domain name.
Go to https://developers.facebook.com/
Click on the Apps menu on the top bar.
This is because you didn't make your Facebook app live. For this go to:
Facebook developer page->Select your app->you will see top of the right your live option is disable and click to enable it->It will refer to you in "basic setting section"->You have to add "privacy policy url" and "Terms and services url" also you may select app category->then save the setting.
Note: You can use any blogspot or website to make your privacy policy also terms and condition page.Both I gave same url which worked.
after a lot of tries, I've read in other topics which someone said "delete all your apps and create it again". I did that but, as you can imagine, a new App will create a new Application ID on Facebook's page.
So, even after all the "set public things" it didn't work because the application ID was wrong in my code due to the creation of a new App on Facebook developer page.
So, as AndrewSmiley said above, you should remeber to update that in your app #strings
Set LoginBehavior if you have installed facebook app in your phone
loginButton.setLoginBehavior(LoginBehavior.WEB_ONLY);
Been a while since I did an app. I created a new app but I can't seem to find the advanced settings (sandbox, etc) for it.
When I viewed the "roles" page, it had me listed as an admin but not as a developer and I can't find anyway to add myself as a developer.
How do I change this?
If you're an Admin then you're the top level controller of the application, and have developer privileges as well.
Go to https://developers.facebook.com/apps, select your application on the left, and then in the top right of the information window there is an edit button (part of the settings header).
Once inside the settings click on "advanced" in the left menu, here you can enable sandbox mode.
Let me know if you need more help and I can post a screenshot guide.
The sandbox option you find when you go to edit settings of app, and then check the advanced tab.
If you are a admin of the app you have all the permissions you need, instead of that, admin role have more permissions than developer role.