topic Re: ArcGIS Pro 3.5: Bugs found in ArcGIS Pro Questions

ArcGIS Pro 3.5: Bugs found

RTPL_AU — Mon, 09 Jun 2025 23:17:13 GMT

Here are some bugs that I've found after using Pro 3.5 for a few minutes.

When using Copy > Paste Special to copy a feature class in a FGDB the new FC retains the alias of the old FC.
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.)

This bug is extremely confidence inspiring to clients when you are sharing a screen during a VC to go over an earthworks design revision.
When copying text or numbers from a popup window you may get a leading space or tab character when you paste the selection into something else e.g. Excel, Notepad, etc.
There are still some PDF issues. When exporting a layout, an aerial image in ECW that is clipped to a boundary only partially displays in the PDF.

These all occurred in 3.3.5 so nothing new.

Re: ArcGIS Pro 3.5: Bugs found

DanPatterson — Wed, 14 May 2025 00:45:27 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 14 May 2025 01:28:13 GMT

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.....

Re: ArcGIS Pro 3.5: Bugs found

DanPatterson — Wed, 14 May 2025 02:08:43 GMT

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

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 14 May 2025 02:59:40 GMT

@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 🙂

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 14 May 2025 03:10:00 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 14 May 2025 06:55:39 GMT

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):

Re: ArcGIS Pro 3.5: Bugs found

Scott_Harris — Wed, 14 May 2025 13:13:08 GMT

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.

Is this with every workspace type (ex. File Geodatabase, shapefiles, feature services, enterprise geodatabases)?
In every project?
Does clearing the display cache resolve it? This button in Options > Display:

Thanks for any more info!

-Scott

Re: ArcGIS Pro 3.5: Bugs found

JoshuaBixby — Wed, 14 May 2025 14:10:06 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 14 May 2025 23:57:25 GMT

@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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Thu, 15 May 2025 01:16:53 GMT

@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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Thu, 15 May 2025 06:22:24 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

Scott_Harris — Thu, 15 May 2025 13:48:17 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Thu, 22 May 2025 07:24:18 GMT

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?

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Mon, 26 May 2025 01:49:03 GMT

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

Re: ArcGIS Pro 3.5: Bugs found

JoshuaBixby — Mon, 26 May 2025 13:36:10 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Mon, 26 May 2025 22:53:52 GMT

@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?

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Tue, 27 May 2025 00:57:15 GMT

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 open Pro with a template project, with an empty fgdb as default (to prevent random temporary bits & pieces all over the place)
Once open, I add and specify folders & fgdbs to use as default, and remove all other folders/fgdbs.
I do some work and save the project.
When re-opened - and you go to execute a new GP task, the orginal template fgdb is shown as destination, not any of the fgdbs added to the project and specifically not the default fgdb.

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Tue, 27 May 2025 04:25:59 GMT

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.

Re: ArcGIS Pro 3.5: Bugs found

RTPL_AU — Wed, 28 May 2025 03:35:39 GMT

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.