Entered By user is replaced by placeholderUsername after initialisation

[alainsussol]

Describe the bug

After initialising mobile, if you login with a different user than the one with whom the transactions has been entered the "Entered by" field of that transaction will be filled by "placeholderUsername". If you then login with the user that entered the transaction then it will appear correctly.

Happened on 8.4.2 and on 8.6.3 as well.

To reproduce

Steps to reproduce the behaviour:
Install mSupply mobile on your tablet. If it is already setup go to the App settings in Storage and clear the data

1. Connect to the cloud by putting the credentials of the site and the URL of the cloud server
2. Wait until it finished initialising
3. Login with mSupply Support user. Make sure that he has right to login to that store (edit users window > Login rights tab)
4. Open a transaction
5. See error

Expected behaviour

Should see the name of the user who entered a transaction even though he didn't loginsince the new intitialisation

Proposed Solution

Leave if you don't know how to fix/implement. Edit this issue description and explain here if you know the best path of implementing the fix within the codebase.

Version and device info

• App version: 8.4.2 or 8.6.3
• Tablet model: Galaxy A8
• OS version:

Additional context

Add any other context about the problem here.

[sah-arjun]

Hi @alainsussol, this issue has been tested by @bipinraiTMF and me using mobile v8.4.2, v8.6.3 and latest.
We looked at the emulator as well as apk and noticed that the issue was existed in the v8.4.2, and fixed in later version.
As it is fixed we can close this issue. Just needs your confirmation.

[alainsussol]

@arjunSussol I am surprised. I believe I tested with 8.6.3 and I had the problem. I will retest it if you don't mind.

[alainsussol]

@arjunSussol

I have tested and I have still the problem with v8.6.5.

So if you initialise and log with the mSupply support or Sussol user, you will see the problem. But then once I login with the user that have created the invoices, the problem disappears. So if I upgrade to a more recent version without re-initialising I am not experiencing the problem.

So it is not a big problem since it will not happen very rarely and has a work around to fix it but it still exists in 8.6.5

[sah-arjun]

Thanks @alainsussol for update.
We will look at it after priority work then.