-
-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VOD Home has lost most categories #698
Comments
Signed-off-by: Sandmann79 <[email protected]>
Amazon has added a new API endpoint, which is mandatory to use. |
Thanks Sandmann79, will wait patiently for a new beta |
Beta 3 is available at #700 |
Thank you Sandmann79, will give it a shot now |
Installed Beta 3 and it logs in and displays everything once again. Now we're going through the categories to download the catalogues and images, so I haven't tested a playback but she'll be thrilled to have VOD working properly again. Thank you so much for all your efforts. |
Addon used
Account type
System Setup (please provide the following information):
Upload Logs
Describe the bug
Have been running 0.99 Beta1 since released, been performing really well. Cancelled Britbox $2 trial on 20/7 so it stopped which was expected.
The last few days though the VOD Home screen has lost most of its entries. Tried Clearing Cache Both, installed the Capture thing them 0.99Beta2 on NUC8 but still the same lack of categories on VOD Home even after clearing cache & cookie.
Just booted up the RPi4 which is still running 0.99 Beta 1. Did a cache/both clear but the VOD Home is the same, lacking a lot of the category items.
Shows play correctly but to find new shows we go into Categories, choose a genre, select Prime Movies or Prime TV, wait for the catalogue to download etc. The download seems to be limited by genre, I guess eventually if I go through all the genres I'll get most of them downloaded,
I tried choosing a genre/TV show and made Home default but then I'm stuck with nothing else. Reset Home in Settings sorted that.
The text was updated successfully, but these errors were encountered: