Here are some bugs that I've found after using Pro 3.5 for a few minutes.
These all occurred in 3.3.5 so nothing new.
Issue with attribute table.
When you have several rows selected, and 'View selected records', then select a row (turns yellow), then click Unselect , Pro 3.5 will unselect a different row.
In Pro 3.5 the Zonal Statistics tool gives error "010819: The input path contains spaces".
This happens when you drag a layer from an existing map into the GP tool field.
It seems to work OK when you go from the source in Catalog.
The same data dragged from a map works in < 3.4
When in a layout and you activate a map, zooming and panning is weird. Let's call it jumpy or sticky. Sometimes it jumps back to a near-previous extent/zoom, but not quite exactly the same.
Not experiencing it in other versions, nor does my mouse act up in other apps. New wired mouse too so that we can rule out wireless issues.
Run GP task to merge FC to SHP and rename a few fields.
Output empty !!>???? (of course you get the green bar saying everything is just dandy....)
Run it again. Output empty. Spend time checking coordsystems, sources, path names, field lengths, etc.
Save Project. Close Pro. Open Pro. Open Project. Go History > Run previous task.
SHP file contains data as expected.
Seriously?
Trying to delete a SHP file:
I have also had issues in 3.5 with copy operations locking up the software. I had initially assumed it was an issue with our network or security software and didn't report it.
I have also had issues with selecting layers from the drop down menus in geoprocessing tools only to be told "the path contains spaces". Then if I navigate in file explorer to the same exact feature class it accepts it just fine.
I have also had issues with "jumping" when panning in an activated map frame within a layout. I suspect it has to do with it rendering or labelling.
For years I have had issues with annotation "vanishing" after being moved or the text being changed. Clearing cache and refreshing doesn't work. You can interact with the annotation in the new location but it isn't visible. You have to close and open the software again. Maybe that's similar to the issue you're having with other feature types now?
I would report more of these issues, but the last two times I filled out a support case online via Chrome, the textbox where you enter the details would lag as I typed. As in, I would type a sentence and then had to wait over a minute to see what I typed. It took me so long to submit the last case that I've given up. I mentioned the lagging in the support case and again in the survey but haven't heard anything. It's the box that says "powered by CKEditor" or something similar.
Hi @Melissa_B
For the vanishing edits - try switching to Single Workspace Editing (Options > Editing). It seems to fix it while Scott & his team are looking into it. They were able to replicate the behaviour so we may see a fix in the future.
Are you in the US? If not, just email your local distributor's Support line rather than using the online form. That's why we pay a premium for local Support right? Right??
Thanks for the workaround on the vanishing edits! I reported issues with edits not saving when switching between editing data in enterprise and geodatabases back in 3.2 (https://support.esri.com/en-us/bug/in-the-multiple-workspace-edit-session-default-setting-bug-000163...), but I haven't had similar issues in 3.5 yet - granted, I've also greatly reduced the amount of data in enterprise that I work with. The issue with vanishing annotation has been going on for over 4 years though - I'll see if that settings change helps it just in case.
I'm in the US so I just create a case with ESRI Technical Support directly via the form since that's usually the best way to outline all the testing and versions tested on. The best work around for that issue has been to type it up on another text editor and copy and paste it over all at once. Just makes me feel silly to have to type outside of a textbox on a webpage in 2025 because the textbox isn't responsive.