Large sigchains don't load properly

[NealHelman]

Using v0.9.4-4, I signed into my main signature chain which has been staking since 2017, and only amount that displays is the trust amount that was pulled over when Tritium converted from Legacy. Sometimes, I have seen everything else since then come over, and then that first legacy conversion amount registers as a current transaction. Attached is my 0.log.
0.log

[NealHelman]

This is still an issue in v0.9.5-2. What appears to be happening is that the original transaction that brought the staked amount from Legacy to Tritium to my current trust account is included in the trust account transactions.

[Qrysto]

@NealHelman that was a MIGRATE contract right?

[NealHelman]

@Qrysto "CREDIT to trust from Legacy transaction"

[Qrysto]

@VidereLicet Looks like another case where tx is from legacy

[NealHelman]

Just tried it with v0.9.5-5, and the problem still occurs. As soon as my balances load, my trust account balance is correct. Then, after 10 or 15 seconds, the balance is increased by the amount of the transaction erroneously loaded from my legacy transfer in Nov 2019.

[NealHelman]

It seems to work in 0.9.5-7. Thanks!

[NealHelman]

In Android version 0.9.9-2, core 5.1.43 (?), the only balance that shows is the original CREDIT that I migrated from Legacy in November 2019. It also only shows my default and trust account, and there are currently several accounts on my sigchain.