Sharing some perspective on this (I was involved in the fix).
Basically what started happening at some point was that Maps had built in a “timeout” for the fetch of Saved lists. When the lists weren’t able to be downloaded/fetched in under X seconds, the system stopped trying, assuming that lists in general would always load in under X seconds.
For users with huge lists, and for some users with very slow connections, it would timeout and not show anything. The way to notice it was typically when sharing the list, because the receiving user would fall into that timeout trap. The owner of the list usually didn’t notice immediately because the places were cached on their devices.
It’s still being worked on, and being rolled out slowly.. Some changes will come though, not sure how it’ll be announced.
Sharing some perspective on this (I was involved in the fix).
Basically what started happening at some point was that Maps had built in a “timeout” for the fetch of Saved lists. When the lists weren’t able to be downloaded/fetched in under X seconds, the system stopped trying, assuming that lists in general would always load in under X seconds.
For users with huge lists, and for some users with very slow connections, it would timeout and not show anything. The way to notice it was typically when sharing the list, because the receiving user would fall into that timeout trap. The owner of the list usually didn’t notice immediately because the places were cached on their devices.
It’s still being worked on, and being rolled out slowly.. Some changes will come though, not sure how it’ll be announced.