See the end of this thread: http://developer.myspace.com/Community/forums/t/2553.aspx?PageIndex=3 Effectively you can't use http_build_query, you need to build the querystring yourself being sure to use rawurlencode()

In that case I do see the issue on my side: http_build_query() internally uses urlencode() instead of rawurlencode() so the spaces get converted to + instead of %20 Thanks for giving our concern your attention.

The main problem is the opensocial_token. I see no field for in it OAuth tool...  so how can I test it with the OAuth tool? I'm using custom signature code, it is possible there we're not handling the spaces in the opensocial_token appropriately on our end... but are there supposed to be spaces there in the first ...

[quote user="ZeroSleep"]It used to be there, even if you had nothing in that field. I'm certain of that. I have example base strings saved from earlier tests that showed it present -- albeit with no value.[/quote] I understand that, but I was expressing how I'm not sure it's related. [quote user="ZeroSleep"]At ...

Some changes were made regarding the oauth tokens last week, which was around when all this started. [quote user="Release Notes"]oAuth: Implement Token Secret [/quote] I don't know if that relates to the opensocial_token issue we're having but I know I can't reproduce the opensocial_token in the OAuth Test Harness.  ...

The only pattern I'm noticing between the request URIs that work and the ones that don't is the opensocial_token has spaces (%20s) in the ones that don't.  Can anyone corroborate this?

I really don't want to bump this thread but usually these sorts of issues don't go on for this long.  I've been getting messages from aggravated users for the last 5 days... I'd really like to be able to tell them something new. Any new information would be very much appreciated.

I can't speak to Smart's problem, mine is the same as the OP; the oauth_signature generated for the iframe src doesn't match more than half the time.

I seem to be having this problem as well at the moment, but I am still double-checking things.

Same problem for me as well... this issue is not yet fixed.