Hello,
When authenticating to V3, I'm using
https://www.themoviedb.org/authenticate/%requestToken%?redirect_to=%APP%
And I get the following screen on Android: https://i.imgur.com/3X1MpCC.png
However, using V4, the URL will be
https://www.themoviedb.org/auth/access?request_token=%requestToken%?redirect_to=%APP%
And the screen that I get is: https://i.imgur.com/BVVYIU4.png
With V3, it is not required to be signed in - the user gets the Login and Signup options and the token is not lost after either action. However, for V4 the user gets an 'error' message, and when he chooses to sign in or sign up, the token is lost.
I can't access the /authenticate/ route for V4, it seems to only work with V3 tokens. With the V3 system, the user only needs to go to TMDB once. With V4, I'll need to open TMDB once to log in and another for the user to allow my API key (approve his request token and ask for an access token).
Am I missing something or is it really necessary to do that for V4?
PS: I only want to have one auth system in my app, however I was having problems with V4 and decided to try V3. I will need V4's features in the future.
Thank you in advance, Luís
Nu găsiți un film sau un serial? Autentificați-vă pentru a-l crea.
Doriți să evaluați sau să adăugați acest element într-o listă?
Nu eşti membru?
Răspuns de Travis Bell
pe data de 21 noiembrie 2018 la ora 10:39PM
Hi Luís,
You are not missing anything, the token should be persisted in v4 calls. I'll see if I can find some time to work on this in the next few days. Worst case I should be able to get to it next week.
Thanks.
Răspuns de opanao
pe data de 22 noiembrie 2018 la ora 10:25AM
Hello Travis,
Also, when using redirect_to with V4 as:
It seems TMDB will always redirect to /auth/access/approve. Am I sending the parameters wrong?
Thank you for the great support.
Răspuns de Travis Bell
pe data de 22 noiembrie 2018 la ora 10:29AM
In v4, the redirection value should be sent as part of the POST body, see here. It's the
redirect_to
value in the POST request body.Răspuns de opanao
pe data de 22 noiembrie 2018 la ora 12:08PM
Hello Travis,
Thanks, that's working now. Sorry to keep bothering you, but when I convert an access token (v4) to session ID (v3), I can't make calls to, for example, /account. I get the status message "Authentication failed: You do not have permissions to access the service.". I can, however, delete the v3 session id (the one I converted from v4, but failed to get /account).
Thanks in advance, Luís
Răspuns de opanao
pe data de 24 noiembrie 2018 la ora 1:26PM
Bringing up my post because you might've missed my last issue. When I convert a V4 access token to a V3 session id, I can't make requests with the returned session id, except the deletion of the session Id itself. Am I missing something?
Thanks again, and sorry for bothering you!
Răspuns de Travis Bell
pe data de 24 noiembrie 2018 la ora 3:05PM
Heh, no, you're not bothering me. I'll see if I can find some time at a computer tomorrow, I haven't had time at to check any of this out yet.
Răspuns de Travis Bell
pe data de 25 noiembrie 2018 la ora 1:04PM
Ok, I found the issue and will try to get it deployed this week. I happen to be traveling this week so my availability is less than normal. Thanks for the report and patience.
Răspuns de joseBasso
pe data de 5 decembrie 2018 la ora 8:48AM
Hello, any news on this matter?
Răspuns de Travis Bell
pe data de 7 decembrie 2018 la ora 11:24AM
Not yet, I don't currently have a deployable version of the app. I've been doing some crazy low level work to the app. As soon as things are ready to go, and can be pushed up to production I'll get this done.
Răspuns de opanao
pe data de 7 decembrie 2018 la ora 11:28AM
Is there an estimated time for that deploy? We're working on a project and we are getting asked how long we will be delaying certain features. Thank you for your work.
Răspuns de Travis Bell
pe data de 10 decembrie 2018 la ora 11:56AM
Hard for me to say. Normally I'd say end of week for sure but I'm heading away for 4 days again starting Thursday so my schedule is very tight. I'll let you know as soon as I have it pushed.
Răspuns de Travis Bell
pe data de 23 decembrie 2018 la ora 1:11AM
Can you go ahead and try converting a new session and let me know if it’s working for you now?
Răspuns de opanao
pe data de 23 decembrie 2018 la ora 9:32AM
Convertion seems to be working now! Thank you. Seems like you forgot to push the original problem though (token not persisting when using V4 login).
Also, have a couple of questions regarding lists. Lists in v4 seem like they don't have a poster, and don't have a backdrop by default. I've noticed that in your website it is possible to update the backdrop, but haven't seen any API call to do so, are we missing anything here? Also, in the V4's documentation, Get Lists doesn't show any successful response, even though it works fine (I think this is Spotlight's fault though, think I've seen you mention that before in other discussions).
Thank you again.
Răspuns de Travis Bell
pe data de 23 decembrie 2018 la ora 11:50AM
Re: session, great.
Re: token not persisting, correct, I have not pushed that yet. I won't be back at work until Thursday the 27th.
You are correct, there is no such thing as list posters in v4 anymore, there is only the backdrop. Have you tried setting a
backdrop_path
field on your list? I'm fairly certain it will work, it's just not documented. The expected value would just be the path of a backdrop, ie./5A2bMlLfJrAfX9bqAibOL2gCruF.jpg
.Re: successful response, what exactly do you mean? What are you expecting that isn't present?
Răspuns de opanao
pe data de 23 decembrie 2018 la ora 11:53AM
Thanks, that's great.
Regarding the successful response, if you go to https://developers.themoviedb.org/4/account/get-account-lists it doesn't show the 200 response - just a minor detail, nothing to worry about.
Thank you for all your work, happy holidays.