Handle database or diskfull error

[ravikp]

Is your feature request related to a problem? Please describe.
When the database(from AsyncStorage lib), gets full, the UI to store the VC's gets hung.

Describe the solution you'd like
Instead of show the UI getting frozen, an error needed to be shown for the user to recover from the error

Describe alternatives you've considered

• Delete oldest VC's behind the scenes

Additional context
Add any other context or screenshots about the feature request here.

[ravikp]

@nayakrounak - Need input clarification on what happens to the incoming VC when we see that there is no space to save the VC?

[lsivanand]

If we are going to delete oldest VC's automatically, (behind the scenes), we should have some where mentioned in the documentation that when or after how many VCs the older will deleted..

Also it is not the number of VCs.. it depends on each VC size.. (depending the data (text/image) in the VC..

[ravikp]

It is required to understand the limits of the system, what are those limits, and how to address when the system reaches its limits.

[ravikp]

That is the reason for keeping the ticket in input clarification phase.

[nayakrounak]

For now, let show an error message, stating that, no more cards can be added or received as app data is full (Please reframe the statement as needed).

We will later give a patch with feature to remove VC (received or downloaded) and update the error message.

Sasi also has some comments over this, we should store the received VIDs externally and add a reference in app data. We can discuss this after our release and add this feature later.

[vharsh]

The following change is available on branch=0.9 & on branch=develop as part of the 17th March, 2023 release and a custom error will be shown as requested.

PR for mosip/inji(branch=develop): #655,
commit: aff1c4f
PR for mosip/inji(branch=0.9): #653
commit: 4c2ca4b

[gsasikumar]

While this is an important problem we need to solve it more better. I would prefer not to store the VC directly in the DB rather in a encrypted file. and the reference and metadata in the DB.

Can we make this as an enhancement?

Also i wanted to cache the schema that the VC refers. This will be needed for our offline validation of VC.

[Raginikrishnamurthy]

This bug is not a part of the 0.9 release, hence assigning back to dev team for further investigation and changes as mentioned by Sasikumar.

[Pragya279]

This bug has been moved to Jira.
Link to Jira bug: https://mosip.atlassian.net/browse/MOSIP-26846