Here are some technical details. Please forward to the tech team that maintains the Mission Authoring Tool. @NianticCasey
The Mission Authoring tool queries a backend server to get a list of points of interest. It has two different strategies to do so. At Zoom levels up to 17, it will use an endpoint at "/api/author/getClusters" which works fine.
However, at zoom level 18 (which is the max zoom level), the code switches to instead use the endpoint at "/api/author/searchPOIs". This endpoint seems to be broken when called with an empty query string . It returns a list of 1000 portals from all over the world completely unrelated to the location parameters supplied. The client script supplies the correct location as a parameter, but the location parameters don't seem to have any influence at all on the set of portals returned. Since all the returned portals are usually far away from the part of the map, the user is currently looking at, none is displayed.
Please send this information to the tech team. An easy workaround for a quick fix would be to set the AUTO_SEARCH_ZOOM variable from 18 to 19, basically forcing the script to not use the searchPOIs endpoint at all. But in the end the "/api/author/searchPOIs" has to be fixed to correctly handle empty search queries.
Apologies for the delay but this is a known issue that the team is currently investigating. I'll provide some an update as I know more. Thanks for your patience and so sorry for the inconvenience!
@NianticBrian and your whole crew who fixed the defect, "Thank you for the fix!! Moara Banner Missions, Everyone!!! Get Your Submissions Flowing, we're heading into some awesome holidays for beautiful artwork for banner missions!!!!!" - Thanks again, Niantic - A2PANTHER!
This had seemed to be fixed, but now it seems to have the same issue again - not showing portals/waypoints at the max zoom level. Anyone else having this issue?
Comments
Here are some technical details. Please forward to the tech team that maintains the Mission Authoring Tool. @NianticCasey
The Mission Authoring tool queries a backend server to get a list of points of interest. It has two different strategies to do so. At Zoom levels up to 17, it will use an endpoint at "/api/author/getClusters" which works fine.
However, at zoom level 18 (which is the max zoom level), the code switches to instead use the endpoint at "/api/author/searchPOIs". This endpoint seems to be broken when called with an empty query string . It returns a list of 1000 portals from all over the world completely unrelated to the location parameters supplied. The client script supplies the correct location as a parameter, but the location parameters don't seem to have any influence at all on the set of portals returned. Since all the returned portals are usually far away from the part of the map, the user is currently looking at, none is displayed.
Please send this information to the tech team. An easy workaround for a quick fix would be to set the AUTO_SEARCH_ZOOM variable from 18 to 19, basically forcing the script to not use the searchPOIs endpoint at all. But in the end the "/api/author/searchPOIs" has to be fixed to correctly handle empty search queries.
still broken
Hi folks,
Apologies for the delay but this is a known issue that the team is currently investigating. I'll provide some an update as I know more. Thanks for your patience and so sorry for the inconvenience!
This appears fixed now for me
Confirmed. Mission Authoring Tool is working again.
Yes is fixed, thanks.
@NianticBrian and your whole crew who fixed the defect, "Thank you for the fix!! Moara Banner Missions, Everyone!!! Get Your Submissions Flowing, we're heading into some awesome holidays for beautiful artwork for banner missions!!!!!" - Thanks again, Niantic - A2PANTHER!
😉
This had seemed to be fixed, but now it seems to have the same issue again - not showing portals/waypoints at the max zoom level. Anyone else having this issue?
This could all be related to the bug where 'intel' isn't showing all portals.
I'm able to see all portals, both yesterday and today.
If you're having a new issue, I suggest opening a new bug, as this particular bug is fixed. See image