The user opens the app (he was already logged in) and is on the main page when he suddenly loses connection
System response
The user should be informed that he doesn't have a connection but he should still be able to see the content that was cached before he lost the connection
When a user is logging in, a request is sent to the database, this has the objective of comparing whether the email and password registered in Firebase Authentication match and in this way being able to return an access key
Event description
The request cannot be sent and/or received due to problems in the network connection
System response
When the system does not register the receipt of the key, it confirms the different error cases. The system consults checkInternetConnection, in case of connection failures, it reports the connection problems through a Dialog. If no errors are reported, it will continue with more tests to validate errors in the entry of credentials
Caching + Retrieving strategy
The access key given by Firebase is cached, this way the login process is faster.
Storage Type
No clue
Stored data type
Key value <NPI, NPI>
Behavior in our app
Services
checkInternetConnection: A service was developed to check the status of the Internet connection. This function implements a http request (ping) to Google to check the internet connection and through this process returns false if the expected response is not received and true otherwise. This information is used to make decisions regarding requests to the database.|
