Firetv: Unable to unlock app

[Ponyo 22]

Hi,

 

I am unable to unlock the app. It says incompatible sever version however my server is running the latest stable.

 

Ps. The firestick is outside my LAN, in case that matters.

[ebr 16169]

What, exactly, are the version numbers of both server and app?

[Ponyo 22]

Firetv 1.1.49a expired

Server 3.0.5882.0

 

No idea why the Firetv version is saying expired but the store doesn't show a update button or anything.

 

Sent from my HTL23 using Tapatalk

[ebr 16169]

It is possible that a poor connection caused the app to not be able to retrieve information from the server in order to obtain the proper version.

 

Does everything else in the interface load?

 

What are the connection speeds both up and down on both ends?

[Ponyo 22]

Okay I found the problem. The user wasn't allowed to use the Firetv. A more descriptive error would have been nice.

 

I could however use it to login the first time I used the app.

 

Ps. When I bought the app it gave me the local price but the email I received from Amazon said the app was free due to a promotion.

 

Emby premiere was listed as null though I didn't have time to check if it was free as well. Maybe an error?

 

Sent from my HTL23 using Tapatalk

[ebr 16169]

Okay I found the problem. The user wasn't allowed to use the Firetv. A more descriptive error would have been nice.

 

You mean you had restricted their access to specific devices?

 

In matters of security, it usually isn't a good practice to spell out exactly why access is denied as that just then gives the person more clues on how to get around it .

[Ponyo 22]

You mean you had restricted their access to specific devices?

 

In matters of security, it usually isn't a good practice to spell out exactly why access is denied as that just then gives the person more clues on how to get around it .

Yes had previously limited this user's access. Seems like after limiting access new devices are not automatically allowed for that user.

 

Makes sense that would be the case, still a slightly more descriptive error would be nice. Maybe there should be a small notice on the server dashboard?