I saw other issues that seem related to the problem I have (#4836 & #angular-377), however the mentioned temporary solution of using listview.refresh() does not help.
The view has a single ListView with items. The properties of some of the items are not immediately visible - they sometimes become visible if I scroll down and then back up. There's an onTap handler which console.logs the correct item properties even for currently hidden items.
Android (haven't tried iOS)
3.2.13.2.03.2.0package.json file of your"dependencies": {
"moment": "^2.18.1",
"nativescript-theme-core": "~1.0.2",
"tns-core-modules": "^3.2.0",
"underscore": "^1.8.3"
}
Use this repo to launch the app and then scroll down/up. There's a gif in the repo showing the problem.
Check:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Hi @jorotenev,
Thank you for reporting this issue and for the sample project.
I reviewed it and found that the problem might be related to the earlier firing of loadMoreItems event for the ListView. We will investigate further the case and regarding that, you could keep track on the issue.
In the meantime, as a temporary solution, I would suggest setting a timeout inside the event callback, which will resolve the problem. For example:
list.ts
export function loadMoreItems(ev: EventData): void {
console.log("loadMoreItems");
setTimeout(()=>{
listModel.loadMoreItems(ev);
}, 0);
}
Thanks for the prompt response, @tsonevn
I tried your fix but it didn't seem to remedy the problem. I used different delays for the setTimeout() - 0,100,1000ms, etc. but the "amount" property (the right-most column) doesn't show on some rows, as it was the case before.
Hi @jorotenev,
I tested again the above-given workaround and it seems to work as expected. Try deleting platforms',node_modulesandhooks` and rebuild again the application.
Might be related to #4962
@tsonevn deleting the folders didn't help. deleting them and setting the timeout to 100ms helped though.
Thanks :)
Hi. Just checking what's the status of this issue.
I could still experience the bug every now and then even with the fix applied (with a considerably lower frequency though).
Cheers
Hi @jorotenev,
This issue is still under review. You could keep track on the issue, for further info.