Dynamic Lifelist doesn't load

my life list doesn’t load. Browser: Edge Version 151.0.4129.78 (Officielt build) (64-bit) URL: https://www.inaturalist.org/lifelists/bornfeta?details_view=unobservedSpecies&tree_mode=full_taxonomy. I have copied this from devtool: [NEW] Explain Console errors by using Copilot in Edge: click to explain an error. Learn moreDon’t show again
react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6 GET https://api.inaturalist.org/v2/taxa/lifelist_metadata?observed_by_user_id=bornfeta&locale=da&fields=all 500 (Internal Server Error)
value @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6
value @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:11
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
(anonymous) @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
dispatch @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
Promise.then
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
(anonymous) @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
39058 @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
t @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:8
t.O @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:8
e @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:1
react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6 Uncaught (in promise) Error: Internal Server Error
at value (react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6:29540)
value @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6
Promise.then
value @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:6
value @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:11
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
(anonymous) @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
dispatch @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
Promise.then
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
(anonymous) @ react-main-webpack-7d9ce937de137d4c250e60632a9e6b1285dbcaf7b2699649415327fa4f7965aa.js:31
39058 @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:6
t @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:8
t.O @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:8
e @ runtime-webpack-7087601a8f9d45bfd892ae2deabf5c6cb22ead639ddbe93f05404c67fdae235a.js:1
(anonymous) @ lifelists-show-webpack-b1f3ecc548f2201b21daa8bcb69befacc96098d67c713cda7feec934912b0b00.js:1
util.js:30 Google Maps JavaScript API warning: RetiredVersion https://developers.google.com/maps/documentation/javascript/error-messages#retired-version
ADa @ util.js:30
(anonymous) @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:1537
Promise.then
(anonymous) @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:1537
setTimeout
Sea @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:1537
(anonymous) @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:14
(anonymous) @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:1848
(anonymous) @ js?key=AIzaSyDsHVgl1tZrI_tlyI8Rg6n6SUEvSHQjfkE&language=da&libraries=places%2Cgeometry&region=uk&v=3.51:1848

Platform:

App version number, if a mobile app issue:

Browser, if a website issue:

URLs (aka web addresses) of any relevant observations or pages:

Screenshots of what you are seeing:

Description of problem:

Step 1:

Step 2:

Step 3:

I can reproduce it with your list and Vivaldi/ WIN 10.

My own list is loading normally.

I have no idea, what can be the reason for it.

a chatbot suggests a faulty taxon or observation, but I don’t now how to identify it. I tried to run: api.inaturalist.org/v2/taxa/lifelist_metadata?observed_by_user_id=bornfeta&locale=da with this result {“status”:“500”,“errors”:[{“errorCode”:“500”,“message”:“Invalid response for status code 200: results/6295: must be object”}]} does that make sense?

i think the technical issue has to do with some extra checks that the v2 endpoint for /taxa/lifelist_metadata applies, which v1 does not. there is at least one taxon getting returned as null in v1, which is disallowed altogether by v2. i’m not sure why null is produced in this case.

it might have something to do with the difference between:

you could try modifying the observation returned by the latter to force a reindex, and see if that does anything.

another possible taxon that could be involved is 1659206.

Okay thank you, I tried to modify the location of 1645545 and later delete the obervation, but it’s still not working. It doesn’t look like I have any 1659206 observations to me. There is still a “null” in api.inaturalist.org/v1/taxa/lifelist_metadata?observed_by_user_id=bornfeta&locale=en I have tried to modify the diameter of the locations of the two closest taxons to the “null” 1684298 and 1692474 but it still doesn’t work.

you do, but it’s attached to 17486 only for some reason. see: https://www.inaturalist.org/observations?taxon_id=174586&user_id=bornfeta.

if you deleted it, and the v1 endpoint is still producing a null item at the same position, then i’m not sure what the problem is. you can try modifying the other thing under 17486, but i don’t think that will change things, if modifying the other thing didn’t do anything.

UPDATE: actually, i made a small change on that observation, and it did reindex and associate it with taxon 1659206 correctly now, but there’s still a null item in the v1 API response. there aren’t any other taxa from your life list that seem to be missing from the response at this point. so i have no other guesses about what why the null item is there.

it may be worth noting that several of the iNat staff also will have problems viewing their dynamic life lists now that the page uses v2.

When I click on my dynamic lifelist it doesn’t open. I was able to open another persons lifelist but most other lifelist also won’t open. ?? Everything else is working.

https://www.inaturalist.org/lifelists/bobbybo123?view=tree&details_view=unobservedSpecies&tree_mode=full_taxonomy

Hi Bobby, I get the same error when trying to view your list (endless loading). Looks like this is an issue some others are experiencing with their profiles so I merged your post to this existing bug report in case they are related.

@bouteloua, Thank you.

This was a bug and should be fixed now.

Below VIEW DYNAMIC LIST are 2 button, Asc. or Desc, I switched and now it works. Maybe someone fixed the bug.. Idon’t know.