Jump to content

Trakt Not Updating


majorsl
 Share

Recommended Posts

I noticed that since on or about November 28th my Trakt hasn't been updating from Emby.  I tried getting a new pin, but still doesn't update.  Here's a snip from the log, not sure if it is OS X or the Android App (MIBOX), seems similar to here in the Android TV Forum (but my PushOver is working):

 

https://emby.media/community/index.php?/topic/53774-trakt-and-pushover-not-reporting-playback-from-fire/?hl=trakt

 

Log snip:

 

2017-12-27 20:40:24.915 Info Trakt: Item is played. Scrobble
2017-12-27 20:40:24.915 Info HttpClient: POST: https://api.trakt.tv/oauth/token
2017-12-27 20:40:24.915 Info HttpServer: HTTP Response 204 to 10.0.1.46. Time: 4ms. http://10.0.1.200:8096/emby/Sessions/Playing/Stopped 
2017-12-27 20:40:25.295 Info HttpServer: HTTP GET http://10.0.1.200:8096/emby/Users/a6429ecdcf1746ffa8a3142bcca3a63e/Items/4b586f94e0859267a2f592c605f85877?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; MIBOX3 Build/MOB31Z)
2017-12-27 20:40:25.300 Info HttpServer: HTTP Response 200 to 10.0.1.46. Time: 5ms. http://10.0.1.200:8096/emby/Users/a6429ecdcf1746ffa8a3142bcca3a63e/Items/4b586f94e0859267a2f592c605f85877?format=json 
2017-12-27 20:40:25.391 Info HttpServer: HTTP GET http://10.0.1.200:8096/emby/Shows/NextUp?SeriesId=4a490cf4429a6864e82e6d0aa47ad7f6&Limit=1&UserId=a6429ecdcf1746ffa8a3142bcca3a63e&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; MIBOX3 Build/MOB31Z)
2017-12-27 20:40:25.420 Info App: Emby.Kodi.SyncQueue: Starting User Changes Sync...
2017-12-27 20:40:25.681 Info HttpClient: POST: https://api.trakt.tv/oauth/token
2017-12-27 20:40:25.811 Info App: Emby.Kodi.SyncQueue: "USERSYNC" User a6429ecdcf1746ffa8a3142bcca3a63e(majorsl) posted 2 Updates:  4b586f94e0859267a2f592c605f85877,ac6b0fb16e1c67588804645f48f97812
2017-12-27 20:40:25.811 Info App: Emby.Kodi.SyncQueue: User Changes Sync Finished Taking 00:00:00.3909570
2017-12-27 20:40:26.210 Info HttpServer: HTTP GET http://10.0.1.200:8096/emby/Users/a6429ecdcf1746ffa8a3142bcca3a63e/Items/4b586f94e0859267a2f592c605f85877?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; MIBOX3 Build/MOB31Z)
2017-12-27 20:40:26.214 Info HttpServer: HTTP Response 200 to 10.0.1.46. Time: 4ms. http://10.0.1.200:8096/emby/Users/a6429ecdcf1746ffa8a3142bcca3a63e/Items/4b586f94e0859267a2f592c605f85877?format=json 
2017-12-27 20:40:26.397 Info HttpClient: POST: https://api.trakt.tv/oauth/token
2017-12-27 20:40:26.622 Error Trakt: Exception handled sending status update
*** Error Report ***
Version: 3.2.60.0
Command line: /Applications/EmbyServer.app/Contents/MacOS/EmbyServer.dll
Operating system: Unix 17.3.0.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Processor count: 8
Program data path: /Users/majorsl/.config/emby-server
Application directory: /Applications/EmbyServer.app/Contents/MacOS
MediaBrowser.Model.Net.HttpException: Unauthorized
   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.<SendAsyncInternal>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.<SendAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<PostToTrakt>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<RefreshUserAuth>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<SetRequestHeaders>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<PostToTrakt>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<SendEpisodeStatusUpdateAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.ServerMediator.<KernelPlaybackStopped>d__18.MoveNext()
MediaBrowser.Model.Net.HttpException
   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.<SendAsyncInternal>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.<SendAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<PostToTrakt>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<RefreshUserAuth>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<SetRequestHeaders>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<PostToTrakt>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.Api.TraktApi.<SendEpisodeStatusUpdateAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Trakt.ServerMediator.<KernelPlaybackStopped>d__18.MoveNext()
 
Link to comment
Share on other sites

I did, or at least I thought I did.  I went to the plugin, clicked "Get Pin", returned with the new Pin and, and put it in.  "On the next request to the Trakt API, this PIN will be exchanged for tokens, and the text field will be cleared. You can input a new PIN to get new tokens."

 

I watched an episode of TV, figuring when that was complete that with be "the next request".  The log I posted above is the result and my PIN is still in the field, it was never cleared.

 

Did I miss a step?  I'll try again.

 

Thanks!

Link to comment
Share on other sites

After you enter the pin, then you need to fill out the rest of the page on the trakt configuration screen, and then click save.

Link to comment
Share on other sites

If by "rest of the information", yes, I choose which libraries I want and the other items and clicked save (and get the "Settings Saved" pop-up).  I've not tried again, but that's all I see.  If you're saying I should see something else on the Trakt page, I do not other than the last instruction to return to the app and enter the pin.  That's it.

Link to comment
Share on other sites

I'm either blind, crazy, or not looking in the right place.  Nowhere in the trakt plug-in setup page do I see a place for username/password.  Get pin only sends me to the trakt site (which I'm already logged in).  I have tried 2 different browsers.

 

Is the user/pass field not in the server dashboard?

 

5a4583f492299_ScreenShot20171228at65057P

Edited by majorsl
Link to comment
Share on other sites

Happy New Year!

 

Also, I got this working.  I suspect that I was waiting too long after entering the Pin to have Emby communicate with Trakt.  I'd put in the pin, watch an hour long show or even and movie, and wait for that to end and kick off communication with Trakt.

 

This time, I got the pin and immediately went to Emby and marked something as watched.  Sure enough, tokens exchanged and all is good.

 

What is the timeout, and if so, you may want to note it in the plugin setup?  I was reading the API docs for Trakt, and it seems once authorized the tokens are good for 3 months (then auto-renewal) but it also says "Use the device_code and poll at the interval (in seconds) to check if the user has authorized your app. Use expires_in to stop polling after that many seconds, and gracefully instruct the user to restart the process. It is important to poll at the correct interval and also stop polling when expired."

 

Just curious, I like to know how things work. :)

 

Thanks, as always, for the help!

Link to comment
Share on other sites

Thanks for the feedback !

 

As far as the timeout, i think we have it checking that api, rather than hard-coding it into the plugin.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...