🐞 [Bug]: Better error handling for fetching/setting price tables on client

[ozgunozerk]

What happened?

The API we are using may respond with "N/A" for the prices (although this happens very infrequently, still happens).
This causes parsing problems on the client-side, with unsubtle error messages.

platform

• Android
• iOS

Expected behavior

If the client can generate more elaborate error messages (for example, mentioning the failing price table date, and the category of the asset, etc.), would be much more helpful to detect and fix the issue on the server side.