Ha ha - seems like I got lucky. The thing about a stack trace is that it runs from the specific to the general - it’s not just a list of things, but a picture of the nested interactions from general code down to the specific machinery. So, the ‘image’ idea seemed interesting, because there are only profile images in the message list. And I think we’ve seen odd issues with profile images before.
But I have no idea why the code is looking at secure storage, if you’ve never used it.
I suspect a database query could list the images which would be fetched in this case, but I don’t know how you might find the rogue profile. If indeed, this is the story behind the stack trace.