12

Resolved

API Error Code: 100 - Requires valid next URL.

description

When authenticating an application, you will received this error.
 
WORKAROUND:
Turn off the new dialog in your application settings in Facebook (Developer App -> Your App -> Settings -> Migrations -> "New Data Permissions" -> Disabled
 
NOTE the WORKAROUND WILL STOP WORKING JUNE 1, 2010.. Code needs to be fixed before then.

comments

wrote Apr 28, 2010 at 4:01 AM

Resolved with changeset 49932.

jimzim wrote Apr 28, 2010 at 4:04 AM

I just updated the source to support the new data permissions and have tested it in two of our apps that are written in MVC. I have tested it briefly in a webforms sample project, but any extra testing is appreciated. :)

petercarter wrote Apr 28, 2010 at 6:58 AM

I have an experimental application at http://apps.facebook.com/podhawk. It is not in sandbox mode, so anyone can access it. I have changed "New data pemissions" to enabled. The authorisation dialogue still returns the above error message, so it appears that the issue has not in fact been resolved.

jimzim wrote Apr 28, 2010 at 3:54 PM

** Closed by jimzim 4/27/2010 9:01 PM

jimzim wrote Apr 28, 2010 at 3:54 PM

Want to show it is fixed so people see it

wrote Apr 28, 2010 at 3:57 PM

wrote Apr 28, 2010 at 7:19 PM

Associated with changeset 49954.

NemoKrad wrote May 5, 2010 at 9:39 AM

Hi, I have just started to play about with this and I am getting this issue also. I have posted on the FB Dev forum, but guess I should be doing it here, here is my FB Dev post, but will describe my issue again here as I now understand it: http://forum.developers.facebook.com/viewtopic.php?id=57109

If I set Master.RequireLogin = true; in my calling page I get the above error message, I think this is due to the Api.LoginUrl being incorrect as when I take this url and paste it directly into a browser I get the same error. I am guessing that either the token should be populated OR there is a parameter missing....

The URL it gives looks like this (sec key altered): https://login.facebook.com/login.php?api_key=8a17f1e4a522785f7efda64654bf70f2&auth_token=&v=1.0&popupsky = 53d456df6fb0537c15a332f9684a6772

Any help would be greatly appreciated, I would hate to have to learn PHP :P

Thanks in advance :)

NemoKrad wrote May 5, 2010 at 9:44 AM

FYI, the workaround described here did the job, but as described only seems like a temp fix to this issue..

jondaley wrote Jun 17, 2010 at 4:33 PM

Any update from the developers in the last month and a half? The "workaround" of disabling isn't the real fix is it?

jondaley wrote Jun 17, 2010 at 4:33 PM

Any update from the developers in the last month and a half? The "workaround" of disabling isn't the real fix is it?

wrote Feb 21, 2013 at 11:37 PM

wrote May 16, 2013 at 11:10 AM

wrote May 16, 2013 at 11:10 AM

wrote Jun 14, 2013 at 7:27 AM