[krola]

I tried watching two rented videos with this plugin yesterday. One of them worked fine, but one just played the trailer. I read the posts and it looks like others might have the same problem.

I checked the logs, added some debug logging and went through the code. Here is what I found out:

1) According to xbmc.log, the video fails because the Amazon server throws Java null pointer exception. After this, the plugin falls back on playing the trailer.
2) I copied and pasted the http request to the browser and I got the same exception.
3) Watching the video with the browser works fine. However, I noticed that the browser uses a different ASIN: If I hardcode this other ASIN in the plugin, the video plays fine also in the XBMC.
4) Initially, in LIBRARY_LIST_MOVIES, the plugin finds the right ASIN. However, then the moviedata is saved to the database and later when the moviedata is requested, the database returns a row with a wrong url. The url is otherwise fine, but there is wrong ASIN and exception follows.

It looked like in the non functiong video, the right asin was in the database field hd_asin and the wrong asin (the one being used) in the database field asin. In the functioning ones, the right asin was in the database field asin. I am not totally sure of this though. I did not dig very deep on this. Instead, I implemented the brutal fix below.

Since the right ASIN seems to be always initially available, I changed the code so that the ASIN is not fetched from the database. It is passed as is to the function which builds the list view for XBMC. The other moviedata is still fetched from the database. The fix worked for me. I can play all of my rental videos now. Of course, I only have a few rental videos so there might be others which don't work.

I only implemented the fix for rental movies. It might work for bought movies if they have a similar problem. I did not look at the tv show part at all since I don't have any tv shows on my Amazon account. If tv shows have a similar problem, then this fix will probably not help.

I am happy to share my fix. However, I think that it would be better if somebody with better understanding of the plugin internals would validate the fix or make a better fix based on the analysis above.