Broken bookmarks in Arc Pro

[MichaelMorgan4]

In Arc Pro 3.3: I have a project that basically serves as my address management and dispatch data update project. My main map in this project is called "Addresses". I have several bookmarks created in this map representing different cities and unincorporated areas, and now most of these are "broken", i.e. they do not have a label, will not zoom or pan to their areas, and cannot even be deleted or reset. Bookmarks for other maps in the same project seem to work as normal. Is there some other way to get into the project file and remove the broken bookmarks?

I left a screen shot of what these bookmarks look like from the standard Map -> Bookmarks menu in Arc Pro.

[DavidPike]

I'm guessing the manage bookmarks option isn't working.

First I'd save a new copy of your APRX for this:

If you open the APRX using winzip or 7zip etc you have a folder called 'map'.  Inside there, the 'map.xml' seems to store the bookmark config.
I'd edit/delete what you need from there (When doing this, I would compare the map.xml from another working project with bookmarks to avoid any formatting mistakes or deletions).

I've not tried this and it's likely not recommended, and also again - do it on a completely isolated copy of your original, and backup the map.xml just-in-case anyway.

[MichaelMorgan4]

In the .aprx Map folder, there are several .json and .xml files. So far, none of them seem to have any reference to "bookmark". I had opened 3 files with a name "map": Map.json, map2.xml, and map3.json.

[imansbburg]

I too am seeing this same issue after having installed the latest patch for pro 3.4.2.

[Mark_Eygenhuysen]

This happened to me in ArcGIS Pro 3.5.2, I have a number of bookmarks that went "blank", do not function, cannot be edited, cannot be removed.  Is there anything I can do aside from messing with files I shouldn't mess with?  My coworkers told me my mistake was to upgrade to 3.5.2 & I should go back to 3.4 because of all the bugs in 3.5.x releases.  The "Technical Support" link is also broken, including the link in the message to "contact our support team".  How embarrassing is that?  Certainly more time-consuming and problematic than advertised!