Skip to content
This repository has been archived by the owner on Oct 5, 2024. It is now read-only.

Make it clearer that the application can't be used when OW4 is down #73

Open
henrikhorluck opened this issue May 9, 2019 · 1 comment

Comments

@henrikhorluck
Copy link
Member

henrikhorluck commented May 9, 2019

If OW4 is down it still appears as the app is functional, even though all transactions will fail

This could be solved by pinging (an api-endpoint on) OW4 on a set interval, and add a status screen saying "can't connect to OW4 " or something when that doesn't return the expected result

@henrikhorluck henrikhorluck changed the title Make it clearer that the application is can't be used when OW4 is down Make it clearer that the application can't be used when OW4 is down May 9, 2019
@FredrikAugust
Copy link
Contributor

There are calls with fetch (I believe), so you could just add a toast to the onError callback.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants