I have up voted answer some month ago, now I just tried to toggle it, throws correct error message, but incorrect year as seen in pic below

Thanks, see you soon

  • App Version:
  • Device: iPhone 5 (GSM)
  • OS Version: Version 9.2 (Build 13C75)

voting on locked answer

1 Answer 1


This will be fixed in

The app uses unsafe filters when performing API calls, so I had assumed error_message would be an unsafe string since it's not annotated "unchanged with unsafe filters".

That said, the docs actually say:

The error_* fields, while technically elligible for filtering, will not actually be excluded in an error case. This is by design.

In talking with Kevin, since an error occurred we can't assume that the filter is valid so it is completely ignored, both for field filtering and safe-vs-unsafe strings. I'm now applying HTML decoding at the alert UI.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .