You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FATAL EXCEPTION: main
Process: io.github.lydavid.musicsearch, PID: 8005
java.lang.IllegalArgumentException: Key "af7347df-ef5a-3c41-826d-d884f8916c17" was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item.
Problem
Somehow we're inserting a second copy of a rg, but with artist_credit_names.
Note that this is a query, not the rg table itself, hence why duplicate rg id is possible
inspecting artist_credit, we see there's an entry for the empty string
Notice that we're matching this rg with the artist_credit_names "" (not NULL) and a-ha
why does using ktor vs retrofit cause any issue like this? it's possible it's due to some other changes in that massive PR
The text was updated successfully, but these errors were encountered:
Issue did not exist before ktor changes: e219759
Temp fix
Comment out
key = lazyPagingItems.itemKey { it.id },
We only lose the ability to animate sort
Log:
FATAL EXCEPTION: main
Process: io.github.lydavid.musicsearch, PID: 8005
java.lang.IllegalArgumentException: Key "af7347df-ef5a-3c41-826d-d884f8916c17" was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item.
Problem
Somehow we're inserting a second copy of a rg, but with artist_credit_names.
![rg inserted twice](https://private-user-images.githubusercontent.com/22302001/265162826-0f20a7e1-5fd8-481d-994b-cdbc2cd0a011.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1NjY5ODcsIm5iZiI6MTcyMDU2NjY4NywicGF0aCI6Ii8yMjMwMjAwMS8yNjUxNjI4MjYtMGYyMGE3ZTEtNWZkOC00ODFkLTk5NGItY2RiYzJjZDBhMDExLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA5VDIzMTEyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThmMGY0M2MzMjY0NWI1NzAwZjBkZGI5MzAxZmNlZTgzM2ViYWE5MTVlZjBiZThjODJmOGQ2YTA1MjBkNmVlOTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hNg5ebS8xvP19eOyuUTpnrQhA1-6CxDkdIlMi9WOm-E)
Note that this is a query, not the rg table itself, hence why duplicate rg id is possible
Notice that we're matching this rg with the artist_credit_names
""
(not NULL) anda-ha
why does using ktor vs retrofit cause any issue like this? it's possible it's due to some other changes in that massive PR
The text was updated successfully, but these errors were encountered: