Does the value for the 'application_name' query parameter in your Access Token differ from your registered Application Name shown on http://developer.netflix.com/apps/myapps ?
We're having a hard time duplicating this. You don't need to specify application name for the access_token request, but you do need to send it for the login request. One thing we've seen in the past is when things get double-encoded. (e.g. Having an application name of "foo bar" may be encoded once to "foo+bar" then encoded a second time to "foo%2Bbar".) This can cause various errors on our side as we try to match up the application name "foo+bar" to "foo bar" and fail.
For reference, you do need to encode things like spaces, and we encourage you to use "%20" for spaces instead of "+" (Partly because it makes spotting things like double encoding really easy.)
That must have been the problem. My application name did have a plus sign in it. Last night, I thought that might be the issue so I removed the "+" from my app's name. But the netflix login page was still using the original name like it was being cached.
Anyways, I just tried to rename my app again (so that it does not have a plus sign) and now the login page displays the correct app name and I successfully get the access token.
When attempting to get an Access token, I get this error:
"Netflix API error Status Code = 401
Application name Mismatch"
What does that mean?
Message edited by dsims 3 years ago
Tags
Morgon – 3 years ago
Does the value for the 'application_name' query parameter in your Access Token differ from your registered Application Name shown on http://developer.netflix.com/apps/myapps ?
Morgon – 3 years ago
'.. in your Access Request', rather.
dsims – 3 years ago
The access request doesn't need "application_name".
I did try adding it though, and still got the same error.
JR Conlin – 3 years ago
Hi,
We're having a hard time duplicating this. You don't need to specify application name for the access_token request, but you do need to send it for the login request. One thing we've seen in the past is when things get double-encoded. (e.g. Having an application name of "foo bar" may be encoded once to "foo+bar" then encoded a second time to "foo%2Bbar".) This can cause various errors on our side as we try to match up the application name "foo+bar" to "foo bar" and fail.
For reference, you do need to encode things like spaces, and we encourage you to use "%20" for spaces instead of "+" (Partly because it makes spotting things like double encoding really easy.)
Does this help solve the problem?
dsims – 3 years ago
That must have been the problem. My application name did have a plus sign in it. Last night, I thought that might be the issue so I removed the "+" from my app's name. But the netflix login page was still using the original name like it was being cached.
Anyways, I just tried to rename my app again (so that it does not have a plus sign) and now the login page displays the correct app name and I successfully get the access token.
Thanks JR!