Bug - Litewallet iOS: Syncing is inaccurate

[jeff169]

Describe the bug
Note: This is a different variation of an issue I previously logged. Yesterday I received some LTC and it showed up in my history just fine. It went through all the steps of processing (the percentage completion etc) and then showed as complete. Balance was correctly updated and everything was good. This morning, I sign in and see everything is good, but then all of a sudden, yesterday's transaction said something like "processing" and then magically disappeared from the history, and the balance was reduced. So there is some sort of persistent sync issue, that seems like when you sign in, sometimes it may not sync correctly, and just lose the transaction. It's like it connected to my history from before when I received the transaction. Syncing the blockchain fixes it, but the transaction should not disappear right before my eyes. I did notice something though. When I synced with the blockchain, all my transactions showed as "complete" but when I signed in for the first time, I don't believe any of them showed any status except the one that disappeared, as mentioned above. So, it's like Litewallet had no memory of any of the transactions ever being completed, although only the most recent one disappeared.

To Reproduce
Receive LTC and verify it shows as complete in the history. Close out of Litewallet. Sign in to Litewallet the following day. Look at the history. If the most recent receipt shows as "processing", it will disappear shortly.

Expected behavior
Once a transaction is completed, it should remain in history.

Screenshots
Did not have time to capture. The transaction was gone before I realized what was about to happen.

Desktop (please complete the following information):

Smartphone (please complete the following information):
iOS 14.4 iphone 11

Additional context

[kcw-grunt]

Thanks @jeff169

This is something I have seen as well. The issue is Litewallet has to sync at launch and whenever the difference in the local block height and the network block height.

So, the syncing is 'showing the making of the sausage'. And it may be that we are discussing how we present to the user. So, if the sync sample rate is reduced, the transaction view will always stale for everyone. This is less than ideal.

It may be we need a better way of letting the user knowing the some local syncing updating is being calculated?

[jeff169]

Isn't there a way to have it sync from the last login to the present time? It seems like it's syncing to an older time, or not syncing at all and reverting to a prior time. It seems like a mislignment of present time and Litewallet time.

[kcw-grunt]

I need to dig into the loafwallet-ore lib. Its a good idea. But considering the dev time , I may have to just to fix the way it'
s updated

[kcw-grunt]

@jeff169 this was looked at at addressed in v3.4.0. Should I close this ticket?

[jeff169]

I was just going to report this again. I am still seeing transactions appear "in progress" or as "just now" even if they are a month old. There are still syncing issues. I took a couple screenshots - let me know if you need to see them. This was just a couple days ago.

[kcw-grunt]

I was thinking maybe our node list is too stale.