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
If the app sends a corrupt or manually edited POST with a non-base64 encoded string, it will crash after the backend returns those values. Rejecting non encoded strings ought to fix this issue and prevent additional potential API problems.
The text was updated successfully, but these errors were encountered:
A colleague brought it up to me, the client side issue is Co-Epi/app-android#204. It has all the details I have, but I can request more if needed.
Ideally, the frontend can handle an improper response without crashing, but the backend should try to catch improper requests before they are sent back.
If the app sends a corrupt or manually edited POST with a non-base64 encoded string, it will crash after the backend returns those values. Rejecting non encoded strings ought to fix this issue and prevent additional potential API problems.
The text was updated successfully, but these errors were encountered: