[Bug]: Error not returned

[pichoemr]

What happened?

With some errors when opening the socket, the actual error is not returned, which causes a 500 error (default error code) and infinite loading.

Example:

• Opening an application that does not have a build (or first build is pending)
• Trying to open an unknown application (for example /app/12) causes an infinite loading and returns the default error (500) in the socket.

It seems that the error page no longer displays, probably due to a mismatch between the server's return and the client's expectation or a format error in the server's return.

[taorepoara]

We need more informations on when it happens before resolving it

[pichoemr]

@lenra-io/devs I have added a few cases where we have no feedback

[Nesqwik]

The infinite loading issue is a client-side issue. It should be fixed independantly.
We should add a Fallback for the default unknown issue client-side then server side and then only fix the 500 error to return a proper error.

If we only fix the error itself, any future 500 will create UI bug and/or no error displayed !