A modern programming language that makes developers happier.

kotlinlang

```Key "..." was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item.```
For crashes like these, is there any work being done to improve the stack traces? I have a billion LazyColumn/Rows in my project, and while the error message explains the issue perfectly, I have zero insight into where it actually happens.

The full stack trace is available <https://gist.github.com/zoltish/4d4d238a95ffa98a4dcde7885cbece09|here>

The key is printed in the stacktrace so you could add a prefix to the keys, unique for each LazyColumn/Row
```items(fooList, key = { "fl-${it.id}" })```


Thanks for the suggestion <@U01F6UJ87U2>; Id love to see something "better" in terms of there being less boilerplate code. I would have to apply that to 300+ places in my codebase :sweat_smile: Preferrably what Im looking for is something akin to how crashes with views were reported back in the XML days, where the crash might occur inside a view, but it would still inevitably trace up to something in a fragment, activity, etc.