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
Under production environments the stack-trace (error log) cannot be displayed directly to the end-user (user-agent) because of privacy issues.
The proper way to handle this is to store the stack trace (and other error information) in an external database and then provide the end-user user with an error tracing code (SHA 256) so that he can provide that to customer service and have the error diagnosed.
Solution
Rely on an external service like Opbeat to do that
Implement our own solution and use a client on Appier Extras
Create an entity named Exception that stores all of this information in the data store
The text was updated successfully, but these errors were encountered:
Description
Under production environments the stack-trace (error log) cannot be displayed directly to the end-user (user-agent) because of privacy issues.
The proper way to handle this is to store the stack trace (and other error information) in an external database and then provide the end-user user with an error tracing code (SHA 256) so that he can provide that to customer service and have the error diagnosed.
Solution
Exception
that stores all of this information in the data storeThe text was updated successfully, but these errors were encountered: