Error on Force Sync #378
Comments
|
@MythriNagaraju the error popup tells you the line number where the error occurred. Maybe you can look there, and at the logs generated right before the error to see what is going on. I don't have access to your source code, and the popup is not very informative otherwise. |
|
I am going to assume that this is related to the failing force sync in #377. Please reopen if it turns out to be more substantive. |
shankari
added a commit
to shankari/e-mission-phone
that referenced
this issue
May 8, 2019
- Define a new function (displayError) that deals with undefined messages,
formatting the error stack, etc.
- Replace all .catch(function(error)) calls with a call to displayError so that
we can:
- have a unified format that we can modify in one location
- display meaningful error messages that should make it easier to figure out
what is wrong.
This makes the error message from e-mission/e-mission-docs#378
more meaningful
shankari
added a commit
to shankari/e-mission-phone
that referenced
this issue
May 8, 2019
- Define a new function (displayError) that deals with undefined messages,
formatting the error stack, etc.
- Replace all .catch(function(error)) calls with a call to displayError so that
we can:
- have a unified format that we can modify in one location
- display meaningful error messages that should make it easier to figure out
what is wrong.
This makes the error message from e-mission/e-mission-docs#378
more meaningful
Bonus fix: fix the formatting in e-mission@94ffa9f I am not sure how this ever worked!
shankari
added a commit
to e-mission/e-mission-phone
that referenced
this issue
May 8, 2019
) * Unify the handling of error messages - Define a new function (displayError) that deals with undefined messages, formatting the error stack, etc. - Replace all .catch(function(error)) calls with a call to displayError so that we can: - have a unified format that we can modify in one location - display meaningful error messages that should make it easier to figure out what is wrong. This makes the error message from e-mission/e-mission-docs#378 more meaningful * Unify the handling of error messages - Define a new function (displayError) that deals with undefined messages, formatting the error stack, etc. - Replace all .catch(function(error)) calls with a call to displayError so that we can: - have a unified format that we can modify in one location - display meaningful error messages that should make it easier to figure out what is wrong. This makes the error message from e-mission/e-mission-docs#378 more meaningful Bonus fix: fix the formatting in 94ffa9f I am not sure how this ever worked!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running into this error on Force Sync. I suspected it occurred only when there are no trips to log to the server, but it also shows up otherwise.
The text was updated successfully, but these errors were encountered: