This is a new one to me, and I'm not sure why it is coming up. It only happens when I try to use the API to post a timeline action. I have the new Auth enabled, publish_actions is included in the permissions list, and I am the admin. I have uninstalled the app, and installed it again, to make sure the new auth has run through. If I run any other query with 'me', it will return just fine. But if I try to run the following:
$facebook->api('/me/example:read?chapter=http://www.example.com/og.php?og=read&id=24131', 'POST');
I get this error: Uncaught OAuthException: Invalid token: "me" An ID has already been specified.
I am running it in ajax, so to make sure I have a valid access_token, I have var_dumped it and changed the line to read: $facebook->api('/me/friends'); In which case, I get valid output of my friends. So I have no clue what is causing this issue. I have also run a different ID (URL) each time, to make sure it isn't related to an action being posted twice (even though I got the error on the first try). Anyone else seeing this? Any clue why this could be happening?
It looks like you have two ? marks in your query string. You may need to urlencode the query string.
Related
Whenever I start workflow it automatically gets cancelled and gives '500' error. And here is screen shots of error.
I am using send email functionality in workflow, and it gives below error.
Please help me out on this.
My suggestion is to validate the log files on the web server to see what the actual error is. I can say, from experience, that the issue is likely with either the value entered workflow email in the "To:" address or the user profile is missing some information, namely the field with the internal name "EMail" field (which may be renamed to something such as "work email".)
You can view the user information list for users with a blank "EMail" column with the following URL:
https://YourPWAserver/_catalogs/users/detail.aspx?FilterField1=EMail&FilterValue1=
In my environment, we had several users with the actual value of "undefined" iun the "EMail" column which I was able to view with the following URL:
https://YourPWAserver/_catalogs/users/detail.aspx?FilterField1=EMail&FilterValue1=undefined
500 error it's an error email. If it's cancelled its because an error of one of your steps, if not you would get a suspended state.
I am unable to connect to the Thick Client.
I am getting the below mentioned error:
"The User ID or Password that u entered is incorrect".
But i am sure that the User ID and Password is correct because i use the same credentials to log into my thin client.
Siebel always shows that error message if anything goes wrong while authenticating the user. Anything may be:
Wrong username or password.
Database not available.
SRF file is corrupted.
SRF file is out of date (specially, if there have been any changes to the tables and those changes are not compiled in your SRF).
CFG file is not properly configured.
Custom code on ApplicationStart produces an exception.
...
Doesn't matter what the problem is, Siebel will always tell you that the username/password are wrong.
You may find what your actual problem is by checking the latest siebel.log file, which should be placed in .../Client/log/, unless you changed its location.
As an alternative, you can keep reentering your username and password. Siebel gives you 3 attempts to enter your credentials. The 2 first ones will show the "wrong password" message; however, the third and last attempt will show you the actual problem instead. At least, that's how it works in Siebel 7.8.
Anyway, it's better to just check the log file, since it will contain more information.
1st check your password. Connect to database. Now test connection with thick client ODBC if you are able to successfully connect.And if this works then delete local spf file of user and also delete diccache.dat file created in bin directly.
Then try login. This resolved my issue.
You can refer Oracle support as well if this issue is replicated for you.
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=ntde4ixli_1004&_afrLoop=479412795573402
Currently I have my production environment set up so that MANAGERS are emailed any time there's a 500 error. I would also like to be emailed anytime someone tries to access something they don't have permission to (i.e., they produce a 403 error).
As far as I can see, you can easily get Django to email you when someone produces a 404 (https://docs.djangoproject.com/en/dev/howto/error-reporting/#errors), but there's nothing like this for a 403.
What's the best way to get Django to send emails when someone produces a 403?
I am getting the following error ("Error: HTTP status code: 400") now that I have updated to facebook SDK 3.1 as of yesterday, 10/9. But everything is completely functional as far as connecting with facebook, I just see this error message every time I start a facebook session on my app. I have seen a few people commenting on this, but I can't determine from them if this is going to be a real problem or not. Does anyone know definitively if this is going to cause a problem? And if so, how to fix it? Thanks!
The original issue was resolved by Facebook just after the 3.1 SDK was released.
But some are still having issues, if you have this issue you should check the login flow, and look at facebooks examples, after that if you are still having issues this could be a hint to a solution.
I got the 400 error when I do not have authorization to get to my information. The strange thing is that I get an accessToken and even a valid login (this is because I structured my code, with the help according to Scrumptious example and did a valid login when the Session state is open).
The FBSessionState is only opened for like a second and then it changes to closed with an 400 Error.
With iOS6 native login you get the permission alert when you ask for it, and then the phone remember that choice for 24 hours. But if the user logs in to the facebook home-page and then deletes permission for the application the phone will not recognize that the user has deleted the permissions for 24 hours, since it remembers the that the phone has already asked it and approved it (in the 24-hour window), regardless if you re-install the app or not.
I found this out after some hours of debugging, since I allowed the application from the Settings in iOS, but I could not post, and since I deleted the permission from the facebook privacy, and the alert would not show again there was nothing I could do but to manually give me permissions via a debug tool or wait 24 hours so I could accept the facebook-permission alert again.
We have an application that allows to users publish content to their friends wall.
It uses the user's access_token given our application.
It works stable usually, but for some reason for one of our clients it doesn't work at all.
We've checked permissions several times, removed-added them again, but still no result.
There is no error message or something, everything looks fine, complete the action, but no posts published in fact. And it doesn't work only for one person.
What possibly can be a problem?
Updated: The problem is actually in this OAuthException:
Error validating access token: Session does not match current stored
session. This may be because the user changed the password since the
time the session was created or Facebook has changed the session for
security reasons.
We tried to get access token one more time, but that didn't help. Somebody familiar with this issue?
your user might forbid people/applications to post on his wall.
"There is no error message or something, everything looks fine, complete the action, but no posts published in fact."
Are you sure about this? You should be getting back a unique stream id of the feed item just posted.
Facebook frequently changes its policies that sucks!
Now, you need permission to access the wall.
You need to check if the user has permission to access your application / wall page. if user hasn't got permission then you need to ask for permission before message is streamed. Yes, that's true, it won't display any error message, unless you manually debug this to see where it is stopping.
My suggestion is:
1. use FB.login method to verify, if the user is not logged in then he should login
2. verify the user permission for the wall page
FB.api('/id', function(response){});
3. publish / stream the comments on wall
FB.api("/id/feed", 'post', { ... blah blah blah !
edits:
At FB.login method, you should ask for permisions
e.g. FB.login(function(response) {..} ... ,{scope: 'offline_access,publish_stream'});