I'm using the new PHP SDK 3.0 and I use the new getLoginUrl() function with the following parameters.
$paramsLogin = array(
'scope' => PERMISSIONS,
'redirect_uri' => REDIRECT_URI
);
If the user clicks "cancel" on the application permissions popup, I redirect the user on an error page which contains a message explaining that he has to accept the permissions in order to participate to the contest and a new login button.
But when i click on the login button again, facebook displays the following message :
Sorry, something went wrong. We're working on getting this fixed as
soon as we can.
If I wait for a while then click again on the login button It works as expected.
I read somewhere that facebook should be displaying "Leave application" in the permission popup instead of "Cancel" I guess this is the issue.
Anyone has any clue on how to solve that problem or should I submit a bug report on facebook.
This is currently open as a bug in Facebook's bug tracker, see here: https://developers.facebook.com/bugs/287587111265733 - I reproduced it myself earlier, and it's been assigned for fixing
I believe if you wait a while the dialog works again (i.e the failure only happens if you go back to the dialog quickly after rejecting it, which shouldn't really happen except when aggressively testing).
Related
There appears to be a bug when clicking the inner close button of the ShareDialog, resolving the promise with {postId: null} instead of {isCancelled: true}
This only happens when selecting the inner close button. The outer button works fine.
Multiple button example:
The links are successfully shared though but do not return a postId(always null). Currently I can't determine whether someone closed the dialog or made a successful share...
To make matters stranger, everything works fine - closing the dialog with either button and also returning a valid postId - when using the LoginManager with the "publish_actions" permission and loading the ShareDialog afterwards.
However, Facebook deems the "publish_actions" permission unnecessary when using the ShareDialog.
The problem occurs in my own app and also the sample app found here: https://github.com/facebook/react-native-fbsdk/tree/master/sample/HelloFacebook
Other details:
react-native 0.45.0
react-native-fbsdk 0.6.0
android facebook sdk 4.22.1
problems occurs on emulator and physical device
Looks like this behaviour is part of the android sdk and not a bug. The onSuccess callback is called on closing the share dialog(why I don't know) and also a successful share.
https://developers.facebook.com/bugs/890116221030179/
So if you need to determine whether a post has been shared it looks like the "publish_actions" permission is needed.
im having a huge problem with the login node in the Web Browser. I click "Login" on the top right corner of my layout. It gets me to the login screen. All fine so far. Then im trying to login and as soon as i typed in my login-data and press "Sign in" Its just reloading the login-page. It doesnt take me back to the site i came from, it doesnt log me in, nothing. Im only having this issue in the web browser since it automatically logs you in, in the Notes Client. Thanks in advance.
PS: Sorry for the bad english.
Sincerly,
Brugen
Agree with Paul...
You could try: http://yourserver.com/names.nsf?open&login to check if your login is correct - disregarding any issues with your XPage.
Next, have a look at your server console to see if anything is written there to indicate a problem. If so it is easiest to use something like the XPages Log Reader to investigate the log files on the server. From the link there is a link to the project where you can download the database.
HTH :-)
/John
Sorry if this is assuming too little knowledge, but are you trying the correct username and password? By default Notes Client and web passwords are not synchronised, it's a separate HTTPPassword field in your Person document on the server. After changing, it may take a few minutes to take effect.
I have an app that I'm using the xcode IDE and writing in Objective-C that uses the twitter api and the 'default' twitter login page for username and password.
I already have all the oauth stuff set up and it is working fine.
I create a new view controller with a web view inside it, and pass the URL of https://api.twitter.com/oauth/authorize.
If I put in my email and password, everything works fine - the view disappears, and we are then off and running.
If I press cancel on the twitter login screen, I get a twitter page saying I need to log in. I need to capture the cancel in my code so I can dismiss the view controller, but I cannot find out what the name of the callback is? I tried didFailLoadWithError but that is not it.
Can someone shed some light on this please?
It turns out it can be handled from the same callback that handles a 'correct' login. except looking for a failure.
So, they have handled it correctly within the original callback.
I am reading a SharePoint list from Office 365 inside a Windows Phone 8 app. My app-code is based on this sample code from Microsoft. It uses
Microsoft.SharePoint.Phone.Application.ListDataProviderBase
Microsoft.SharePoint.Client.ClientContext
Microsoft.SharePoint.Client.Authenticator
The actual problem beeing signout not working!
On the first request to the server, the client asks for authentication and shows a hosted browser window where I can enter my account credentials. I select to stay logged in here.
If i restart the app, it authenticates me without showing the UI again.
I would like to be able to switch user or simply signout leaving no credentials on the phone behind.
I found the following static methods on Authenticator which do not change anything:
Authenticator.ClearAllCookies();
Authenticator.ClearAllCredentials();
Authenticator.ClearAllApplicationSettings();
What is the prefered way to do this?
This is an example of how I am logging out a user in my SP list App for WP8:
App.MainViewModel.IsInitialized = false;
Authenticator.ClearAllCredentials();
App.MainViewModel.Initialize();
MessageBox.Show("You have been successfully logged out, click refresh to login again.");
Your app maybe a little different, but you should at least get to the App and ViewModel to set Initialized as false. I did expxect the App.MainViewModel.Initialize() to show the login page but need to click refresh after calling this SignOut method to do so, that is why I displayed the messagebox.
Hope this helps you.
I'm trying to use the Google Analytics Query Explorer 2 to test a few API calls, but it says I need to authorize myself and I don't know where to do that. What am I missing? Here is a screenshot.
Try the big button on the right that says "Authorize Access"
Im not sure whats wrong with your screenshot but https://ga-dev-tools.appspot.com/explorer/ has the button. your screenshot doesnt.
The site was recently designed, and it looks like you've somehow got an old version of the layout with a new version of the stylesheet. If you refresh the page, I'm sure the problem will go away.
And in case it's not obvious, you can authorize the new version by clicking on the big orange banner that says Click here to authorize. That will authorize the query explorer as well as all the other demos and tools on the site: