Select to view content in your preferred language

Now that Pro 3.4.2 has been released what issues do people still have that are not yet addressed?

3981
15
Jump to solution
01-30-2025 04:06 PM
RTPL_AU
Honored Contributor

The title says it all.
EDIT: Maybe it doesn't. 
What issues are you experiencing in Pro 3.4.2 that did not exist in 3.3.x or earlier?



I have a quiet few days ahead so want to know what issues you are experiencing with ArcGIS Pro 3.4 (that have not been addressed in 3.4.2)  before I upgrade from 3.3.2

There are so many bug fixes going from 3.3.x to 3.4 that I was quite wary to jump into 3.4 immediately. The old 'when fixing everything you're going to break something'....

There have been mentions of PDF issues elsewhere - sort of a deal breaker for me as a lot of projects I intersect require PDFs for static reports, submissions, etc. 
No mention of desktop-side PDF fixes in 3.4.2 hence this post.

 

I wish Esri was more open about known/reported issues but I understand why they aren't.

15 Replies
RTPL_AU
Honored Contributor

Hi @KoryKramer @Robert_LeClair 

I see there are a number of bugs slated as "Fixed" but will be only get fixed in 3.5 according to the bug tracker?

Does this mean you have fundamentally abandoned 3.4 after 3.4.3?

I guess I am installing 3.2 again as some of the issues in 3.3.2 are not fixed yet and the show stoppers in 3.4 seem to be deferred to 3.5 now.

I don't know what to say. Pro is getting to be extremely frustrating day to day and your continual chasing of new versions and new features make you look as if Jack wants to sell the joint to a VC. 
Just stop the race to Pro V99 and pick a version to fix everything in. 
That can form a decent base for future expansion. 

If some people are that hard-up for shiny new things have a public alpha>beta>RC channel with a containerised install model so we can run stable & dev branches easily. I'm sick of paying for the privilege of being a decade long beta tester with the same day 1 issues still around and every issue is gaslighted back to "use less data, work slower, get a better computer".
I'd love to see the installed version spread but I guess it is not something Esri'd share. Competitors might take adv.... I wish you had decent competition.

 

Robert_LeClair
Esri Esteemed Contributor

Hi @RTPL_AU - as I work in Training Services as a Senior Instructor/Principal Technical Lead, I am not privy to the ArcGIS Pro Development Team workflows for major/minor release cycles and how bugs are managed.  I see you've tagged Kory so I suspect he'll be better able to address your questions.

0 Kudos
RTPL_AU
Honored Contributor

Hi @Robert_LeClair 
as a clearly defined representative of Esri, communicating Esri ideas, ideology, opinions, or concepts, I included you as a contributor to this thread; and as a person that is a lot closer to the core team creating Pro, and who can much more efficiently communicate to those that determine Esri culture than I can.

0 Kudos
Robert_LeClair
Esri Esteemed Contributor

Thank you for the contributor add - appreciate it!  I will still defer to Kory as he's the Lead Product Manager for ArcGIS Pro for a response to your question though.

0 Kudos
RTPL_AU
Honored Contributor
0 Kudos
RTPL_AU
Honored Contributor

If you love the delays caused by excessive license checking you'll be elated to hear that it is fixed in 3.5.

I get the impression that if 3.4.x was used to run a car, all the cars using it would still be on the road....
.

.

.

 

The rest would've made it home 🤣🤣🤣

 

Screenshot or it didn't happen:

RTPL_AU_0-1743650322772.png

 

0 Kudos