Since today the login page does not redirect back to the oauth_callback url given. Any one noticed that or has a clue?

Also, isn't there a technical forum for DA other than this one (which is under Application Policy...)?

I am experiencing the same issue on an app that was working yesterday.

Also for some users it does get redirected but then I get permission denied errors on things that were working yesterday. Looking around even the Techcrunch app is not working any longer:

http://www.techcrunch.com/myspace/app.php

This is affecting our service quite badly, would very much appreciate a quick fix!

Thank you

Hi,

There were 2 changes that was deployed yesterday.

1) Only live website/app will have their callback_url forwarded. For developers of the app, the callback_url will also work.

2) The list of returned fields coming back from the api will be 4 basic fields: {"thumbnailUrl", "nickname", "id", "profileUrl"}. To get more information about the user you will now need to explicitly list the fields in the fields parameter.

/v2/people/@me/@self?format=json&fields=aboutMe,dateOfBirth
The list is comma delimited and the full supported fields can be found at: http://developer.myspace.com/community/myspace/da.aspx

-V

Where are these changes announced!?

 I cannot stress enough the importance of communication with developers - to say this is frustrating is an understatement. Please - clearly communicate changes BEFORE they are made... It is maddening to try to play a guessing game to determine if the change was Myspace or a bug in my own code.

 I agree with Scott. This is a very unprofessional behavior. You guys make it impossible to work on your platform. 

 It seems there is more to only the callback_url that is not called. It is not possible anymore to obtain an OAuth access token for users that are not developers of the app.

 Not to mention that the response time of the api page is getting worse and worse each day to the point of being totaly unusable.

Does anyone know what code changes I need to make to the techcrunch sample app to get it working again?  

my understanding is that the techcrunch demo app uses “/authorize.aspx” during the OAuth process, but it needs to just be “/authorize” in order for it to continue to work as we roll out OAuth enhancements.

Alas, no.  It uses the correct url for authorize as far as I can tell.   I was hoping someone had already gone through the code and fixed it for themselves and would be willing to share this info and save me the time of having to hunt it down myself.  I'm new to myspace and oauth devel so it probably takes me a lot longer to figure some of this stuff out.

For anyone following at home here's a link to the techcrunch app (it will give the same error I get):   http://www.techcrunch.com/myspace/app.php 

 And it's source: http://github.com/techcrunch/myspace_oauth/tree/master

Because of the changes mentioned above.

The reason the techcrunch app has an error is due to the fact that we had privacy changes related to the friends api.
You can not use the /v2/people/[id]/@self against your friends data, since they have not authorize it. You can only grab the data related to the user that just approved it. Only the id, nickname, and thumbnailUrl are available in the /v2/people/@me/@friends. Only way to get your more detailed friends data is if they went through this process also and you have matched their user id.

Sorry for the inconvienent. Privacy is important to us.
-V

 How can I make my external application live?

Please, see http://developer.myspace.com/Community/forums/t/3870.aspx

It says NoPanelsDefined and doesn't let it go live.

we've just finished fixing this bug, and it just needs to get pushed to production to go live.  what is your app id?

I'm having the same or maybe related problem. A user different from me (as Developer) is not being redirected to the my server again, but instead to http://home.myspace.com/index.cfm?fuseaction=user. Is there any way to let someone else test my app which uses MySpaceID without adding him as developer?