You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deserialization errors can cause unexpected behaviour like not being able to login if e.g. an addon has a bad mainfest or library item has a bad field.
Consider adding special serde_with-like attributes to fields which may cause this issue, like:
BoolFromAny - like string: "true", "false", int: 0,1, bool: true, false, etc.
VecSkipError - for invalid addons - that indeed seems a must (re-adding the addon could update the manifest?)
BoolFromInt - for manifest.behaviorHints.configurable - I'm not so sure if this is the right way, as it will cause more cases we need to uphold
Consider
Deserialization errors can cause unexpected behaviour like not being able to login if e.g. an addon has a bad mainfest or library item has a bad field.
Consider adding special
serde_with
-like attributes to fields which may cause this issue, like:For example, serde_aux - https://docs.rs/serde-aux/latest/src/serde_aux/field_attributes.rs.html#586-646
Example
mad manifest causes user authentication failure on android tv.
INVALID Error: manifest.behaviorHints.configurable: invalid type: string "true"
The text was updated successfully, but these errors were encountered: