I've taken the plunge to update to 3.6 in the hope that a few of the 3.5 issues have been resolved.
I used a full manual update process i.e. I downloaded the 3.6 files from MyEsri.
There was a .Net update which I grabbed with WinGet. It is 8.22 on 17th Nov.
2 & 3 are inconveniences but irritating and slows you down.
1 still not listed as a bug and not addressed in 3.6 makes me sad and I guess I have to go back to a much earlier version of 3 (before the license checking bug fiasco which I think makes it 3.1).
At least I have my Airpods transparent mode to entertain me.
BUG-000177301 for ArcGIS Pro in Product plan with a workaround
BUG-000177594 for ArcGIS Pro in review sadly, found in 3.5.1, so prior might be good
@DanPatterson
LOL at the workaround for BUG-000177301.
They should say you can click in any other part of the interface. Saying the best workaround is something that requires TWO clicks on the objects likely to be the furthest away from the user's mouse during 'normal' work is so...... inefficient.
edited OP to indicate which are issues from previous versions. I skipped 3.4 altogether.
Infographics Button in ArcGIS Pro 3.6 just spins once a point has been clicked on the map. Was working fine in 3.5
Since I've updated to 3.6 I have problems with WMS-Layers. They only partially display and even dissapear completely when exported to pdf.
Back after a few weeks off and I can honestly say it wasn't just a case of skill issue and me being tired towards the end of 2025 - 3.6 is a mess.
The copy issue is real and exists across versions of Windows, PCs and a new server setup I installed earlier this week. No mention of it being fixed in 3.6.1
Since Pro 3.5, it seems to lose the plot every now & then and common functions/features just stop working. This morning after an hour in an existing layout I could not drag items between legend columns. Great. Waste a few minutes overthinking it then restart Pro. Legend dragging works again.
Should I spend the hours needed to figure out how to replicate it and lodge a case or just yell at they sky here and hope someone at Esri has an epiphany and realise that maybe they should start coding better and testing more?