This is with code like:
foreach (var tile in ShellTile.ActiveTiles)
{
// update the tile.
}
At the moment I only have anecdotal evidence of this behaviour but wondered if anyone else could shed any knowledge or experience of this while I continue to investigate.
Deleting and repinning the tile in question seems to make the problem go away but this isn't a real solution.
Additionally it doesn't seem like it's the first or last created pin but I can't be sure of this.
Has anyone else seen this?
Hi Matt,
ReplyDeleteYour background agent isn't running out of memory or time before updating the last one is it?
We ended up having to liberally GC.Collect(2) to keep under the memory limit as we synthesized our tiles.
Hi Anthony
ReplyDeleteIt's not a memory or time limit issue. We have strict controls on memory and execution time, plus based on the order that the tiles are updated, we know it's doing some other tiles after it should have done the one that's missed.
We also had some issues reusing filenames with a lock screen provider, where they didn't update if they weren't seen.
ReplyDeleteAnthony, yes, you have to use a different filename when updating the lock screen image
ReplyDelete