From 5e96f6fa772a105047f11fa143a529c24265f687 Mon Sep 17 00:00:00 2001 From: Jan Kubovy Date: Mon, 7 Oct 2019 10:27:50 +0200 Subject: [PATCH] Include session expired reason in API fetch error message. To improve user experience when fetch errors are encountered due to expired sessions, an additional common solution proposal is added here to the error message. Change-Id: If7f8e905969acabd3e66710c519267d86367289d --- web/src/actions/errors.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/web/src/actions/errors.js b/web/src/actions/errors.js index b90369d6b4..01a70b77b6 100644 --- a/web/src/actions/errors.js +++ b/web/src/actions/errors.js @@ -32,7 +32,8 @@ export const addApiError = error => { d.text = error.response.statusText d.status = error.response.status } else { - d.status = 'Unable to fetch URL, check your network connectivity, browser plugins, and ad-blockers' + d.status = 'Unable to fetch URL, check your network connectivity,' + + ' browser plugins, ad-blockers, or try to refresh this page' d.text = error.message } return addError(d)