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.
I have coworker who is experiencing the same issue, but myself and other team members who have 3.5 are not.
Another bug for 3.5.4:
- In previous versions (ArcGIS Pro 3.2), when you changed the map used in a map frame in a layout, it would zoom out to the world extent.
- This appears to have changed in ArcGIS Pro 3.5.4, so it keeps the original extent of the previous map (great!). But when you activate the map and pan/zoom to change the extent shown in the layout, it is extremely glitchy (glitches, goes back to previous location, etc).
- It looks like this doesn't occur if you click and pan very slowly.
I've just deployed a new PC with Server 2025 as OS and all new user accounts, etc.
The Freeze on Copy bug is alive and well.
Insert Map is greyed out in the QAT and in the Ribbon.
It re-appears after a while if you go and do something else and not feed its attention seeking behaviour.
I've had other buttons/tools mysteriously go inactive temporarily since updating to 3.5 e.g. "Zoom to selected" in the Attribute Table.
Sometimes they come back after a few minutes, other times it requires a Pro restart.
Not really a bug, but different behavior in ArcGIS Pro 3.5 that I can't find documented in a bug/enchancement, issues addressed list for Pro 3.5, or the "What's new in ArcGIS Pro 3.5" document: The service layer credits property now actually pulls all the service layer credits. Previously, it seemed like the serviceLayerCredits property was only pulling basemap information even if there were other service layers in a map that had credits.
Tested this with a basemap and service layer in a layout in Pro 3.4 and it only pulled the basemap credits. Tested it with the same basemap and service layer in 3.5 and it gets all the service layer credits (as intended based on the documentation for dynamic text tags: https://pro.arcgis.com/en/pro-app/3.4/help/layouts/add-and-modify-dynamic-text.htm)
Like I said, not really a bug, but it is a change that I couldn't find documented or mentioned anywhere so I thought I'd put it out on the Internet in some form in case others get confused by the increase in text in the service layer credits.
Updating with link to bug for the "jumping" that occurs in an activated map frame in a layout when panning: https://support.esri.com/en-us/bug/the-pan-and-zoom-tools-in-an-active-layout-in-arcgis-pr-bug-000177418
Update:
ESRI support has an existing bug for the symbology color scheme issue (BUG-000177332) and it should be fixed in ArcGIS Pro 3.6.
The ESRI support agent I had for this was extremely helpful and is relaying my information about the "create a case" form lagging when filling out the description box internally.
I think I've been trying to search for reported bugs in the wrong place so I'm noting this here for anyone else confused: If you go to support.esri.com, you can search and filter by the product and version to find reported bugs. In this case, I have to filter for all versions of ArcGIS Pro 3.5 and keep my search text simple, but I can find the bug.
Another bug for 3.5:
- set a layer to unique values symbology
- select a field to generate the unique classes
- select a color scheme to... well, I guess just change the color of the first item because it's automatically "selected" so now trying to change the color scheme for everything only does the first item. Now you have to manually scroll and select all the classes and then choose your color scheme.
Went to submit a case for this one, but the ESRI Technical Support "Create a Case" page doesn't even include 3.5.2 as an option for the ArcGIS Pro version. Also, that text field for issue description when submitting a case is still lagging. It gets worse the more you type - since there's some kind of AI running in the background to review what you've typed and offer suggestions, I'm assuming that it has poor performance which is making it difficult to actually submit a case.
More buggy behavior in 3.5: Pro is consistently ignoring zoom to and pan to operations when a feature is selected in the attribute table. Even if I'm selecting a single feature to try to view, double click on the record number does nothing, right clicking the record in the attribute table and using the zoom to or pan to from the shortcut menu does nothing. The zoom to operations that work are the button in the ribbon in the selection group or the button on the top of the attribute table. The zoom to and pan to options in the shortcut menu that opens when you right-click on the map still work; seems to be isolated to only the shortcut menu in the attribute table. Just noting it here since I would do nothing but ESRI support tickets if I submitted all the buggy behavior every time I identified it.
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-000163453), 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.
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??
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.
Trying to delete a SHP file:
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?
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.
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
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.
Issue with Ribbon config backup/restore.
To test my config to try to solve some of the other 3.5 issues I reset the Ribbon. That also cleans out the QAT. The reset did nothing for the issue I wanted to check so I wanted to restore the Ribbon config I'd exported before the reset.
Load the backup, QAT tools appear. Click OK to close Options and the QAT is reset back to clean default?
Did it a few times but behaviour is consistent (consistently wrong?) The only way to keep my beloved QAT is to restore the Ribbon config backup and then kill Pro through Task Manager.
There is something going on with the way Pro 3.5 'remembers' things and the populates input fields for operations/tasks.
Doing many attribute joins, and field calculations etc today and it is prefilling the various inputs with 'stuff' from previous operations in various forms.
Doing a field calculation on a table that has a join, the output value entry will have a joined field pre-populated in the form tablename.fieldname from a previous join that is no longer in effect.
Creating a new join will have joining fields populated with old tablename.fieldname entries that are completely irrelevant to the combination that is being used. I've also had joins not work where the output has very few matching results. The two source tables are derivatives of each other so the fields and attributes used to join on are 100% the same but it cannot match them up for some reason. Copy/paste into Excel, run VLookup and I get a 100% match.
ArcGIS Pro 3.5 seems to use a database that is not the default, nor added to a project, as the destination database for geoprocessing tasks.If you updated a project with new databases, folders etc, Pro will at times revert to using a removed fgdb as the destination database, even if that destination has never been used in a GP tool inn that project. As Pro seems to always pick a random location from your past to do something in, this is no surprise. The fact that the destination is not shown in the PG task unless you click on the output FC name, is a pain.
Basic workflow as follows:
I've not tested it fully but using a no-template start will see the future project refer to the temporary fgdb Pro created in your tmp folder. This does not seem to be the behaviour of remembering a previously used destination. It will revert to the wrong fgdb destination when you've never run a GP task in the new project before at all.
Local reseller/support trying tog et their head around it as well.
EDIT:
And to add to this – it will keep using the wrong database even after you’ve run a GP tool multiple times.
I’ve run the pairwise intersect tool multiple times this morning and every time the destination database is the wrong one i.e not any of the databases in the project nor the default one, and not one that I have used a a destination for any task in recent memory.
@JoshuaBixby which reinforces my Idea that Esri should pivot to separate Stable + Supported, and Feature Release version streams. Please upvote it!
You find a bug in version X, which is fixed in Version Y, but Y has another new showstopper bug so only option is to go back to W but lose new feature that made it a bit more efficient?
To be fair , adding SQL support in Calculate Field to file and mobile geodatabases is new in Pro 3.5. There is a big difference between an issue with new functionality versus functionality that is mature and been around for a while.
I don't agree with how Esri is handling the update service issue, especially if it is only because of this issue.
Here's a good one. It is the reason the update service to 3.5 to be disabled.
"In ArcGIS Pro 3.5, Calculate Field does not honor selection or layer filters when using SQL as the expression type on file geodatabase data"https://community.esri.com/t5/arcgis-pro-questions/pro-update-update-to-3-5-service-down/m-p/1617623#M96007
OK. This new copy issue is the most unstable & irritating thing I've had in Pro for a while.It 100% takes the place of the License Check bug (which seems 100% fixed now).
At any moment, with anything that you can CTRL-C or click Copy on in Pro, it will either have a small seizure or just lunch itself completely to where it has to be killed from Task Manager.
This started with Pro 3.5 and does not occur with any other app on this machine.
Anyone else have the same?
Thanks for the reply @RTPL_AU . If you hit this editing bug again feel free to reach out to me. I'll direct message you my contact info. The ArcGIS Pro Editing team is very interested understanding the problem.
New one - Case lodged.
This is behaviour I have not seen in any earlier version of Pro.
It seems every now & then when you copy something, Pro 3.5 will have a bad moment, sometimes even blacking out the app window, including any panes you have open on other screens.
This could be any copy, such as copying a layer name, symbology text, attribute, or even layers between maps or copying the layer properties. The petit mal will be as soon as you right-click > copy or hit Ctrl-C.
This is happening enough that I feel something is up. Computer has been rebooted since installing Pro, and Pro has been closed/started many times as I work through jobs. It happens with one or multiple Pro instances running. Have swapped DX versions to test out some of the other issues.
@Scott_Harris Clearing the cache doesn't change the behaviour. It has a temporary effect i.e. it forces you to save edits and reload the map/project but when you start editing, the display messes up again.I've also tried toggling between DX11 & 12, with various aliasing etc settings.
@Scott_Harris @JoshuaBixby
Item1: Lodged as an idea by others in 2022 (IIRC) and also filed as a bug with local reseller (who thinks it is an enhancement request). Rename a FC in FGDB and Alias is updated. Paste Special and rename copied FC = Alias not changed? Consistency much?
Item 2: If a bug gets stuck with the local monopoly reseller then no public bug nr will be available. Now you know of it as well.
Item 3: To quote Esri Inc:
BUG-000166795 - Undesired additional space when copying a numeric value of a record from the attribute table field popup in ArcGIS Pro 3.2.Status: Non-Reproducible (Learn More) Additional Information: Issue is not reproducible in versions 3.1 or higher. Alternate Solution: Delete the space manually after pasting it anywhere else.
A few things got lost in translation - it occurs for any data type. Local reseller has been able to replicate repeatedly on multiple Pro versions.
4 PDF Issues - nothing lodged yet as it seems some of it overlaps the multitude of 3.4 pdf bugs.
Lagginess in UI - no case lodged yet for this specific behaviour. Only installed it yesterday and will see if there is a pattern I can detect. It's not the hardware spec if anyone is wondering.
Clicking in ribbon or QAT not bringing Pro to the foreground - case lodged with locals.
@Scott_Harris re editing bug.I use FGDB (95%) & SHP most often. As far as I can tell it is related to having certain types of symbology in a map. I suspected coordinate systems and transformations but that seems to be coincident but unrelated.It is intermittent - partial behaviour map would be to open a new project, add FC, start editing, things work, save edits, add more data, save project., close Pro, come back ,open Pro, open project, start editing, things work, save edits, save project, start editing, things don't work and likely won't for that project again. Open new project, add data from catalog, start editing, things work, ..... and so it goes.We have near decades of ArcMap projects & styles that get carried over as clients come back or projects evolve. Working through all of that to find what triggers Pro to hose itself should not be my job. You guys develop it and should know exactly what could trigger specific behaviour. Forcing us to go through local resellers that gatekeep the info you get, again, is not a problem your clients have caused.
Workarounds such as clearing cache etc becomes unworkable very quickly - do I clear cache before every edit session, during editing, after editing? Who pays for the time wasted doing housekeeping that Pro should be able to do itself?I have had formal feedback on Pro UI lagginess bugs to "work slower"Leading space bug advice = "Delete the space manually"These sorts of things are why people still use ArcMap after Pro has been around for a decade.
Yes, I am frustrated.
When discussing defects, it is helpful to provide the bug number. Most defects, although not all, are searchable through Esri Support website and can be linked to in forums/communities like this one.
Hi @RTPL_AU
Regarding item 2,
During an edit session, Pro will stop showing the edited geometry once an edit is completed (press F2, etc) and revert to showing the old geometry on screen until you save and refresh the map.You can still interact with the geometry in its new location (edit vertices will show the correct geometry while using the tool but revert to display the last saved version when you finish the tool operation.)
The ArcGIS Pro Editing team is not aware of a bug that fits this description.
Do you have a bug number that I can look into?
If not, I have many more questions, but I'll try to keep it to a minimum.
Thanks for any more info!
-Scott
If Pro 3.5 is partially behind another application window and you click in a blank part of the Ribbon or QAT, Pro will not come to the foreground. You have to click inside another part of the application window.
Clicking in the pink areas does nothing when Pro is behind another app (File Explorer in this case):
Anybody else finding that Pro 3.5 will stutter for a few seconds when you try to switch back to it when you've done something in another app?
Also seems that there is a problem with some unresponsiveness when using copy - example is to copy the layer name in the layer properties window so I can paste it somewhere else. Select text > right click > Copy > Pro hangs a second or so (verified in Diag Monitor as Unresponsive) > continue to do what you wanted....
I'm on Nvidia Studio Drivers 566.36 which seems to be recommend as having less issues than some of their recent releases. Will try between DX11 & DX12 to see what rolls best.
@DanPatterson Agree - Making it easier to track bugs will make it so much easier to figure out what's going on. I guess you can look at the bug knowledge base and chase through what is still open. Filtering bugs by detailed versions (reported in vs fixed in) isn't possible last time I checked.As you're sort of retired maybe you can compile a blog post from all their sources? Maybe they'll give you a discount on your licenses....... If they wanted to make their support site AI useful this would be a start... Maybe not. It will probs hallucinate that all's well and the weather's good 🙂
Sorry, I misread and thought that these were new bugs.
It would be nice if there was a BUGS_NOT_FIXED to the
Release notes for ArcGIS Pro 3.5—ArcGIS Pro | Documentation
under Issues Addressed list
It would be much easier to keep track of bug version versus current release version
Esri are aware of these bugs as they've been around since 3.3 or earlier.
The leading space issue was lodged for 3.1 (IIRC) and I received a notification last week that it was fixed in 3.2. (LOL?) It wasn't and was reproduceable by the Esri AU support person while on the phone with me Monday in 3.3.5 as part of their follow up.
"Workflow' went out the window years ago. Some of the issues with Pro are just bad code or bad leadership.My gut feel is that they are pushing too hard to launch new versions every few months rather than taking the time to create stable release versions with long term support. We've just received 3.5 and there are still orgs on 2.x due to fundamental breakages or issues with new versions. It's truly a case of once you find a version that works stably for your scenario you stick with it because who knows what will break next.I have an Idea lodged that Esri should pivot to a Long Term Stable + Short Term Feature Growth cadence model so that we (the paying customers that are the reason Esri exists) can pick if we prefer a stable cadence (i.e. non changing + non-crashing) or need the fancy new beautiful feature but accept that it might blow up something else.Apologies for the rant - I haven't had red cordial in a while and thus tend to not read marketing brochures with tinted glasses much these days.....
Were these reported as bugs previously?
They may not be picked up during Beta testing unless it is part of someone's workflow.
Report these, maybe they can be resolved a near term patch.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
