Community
Select to view content in your preferred language

Time to Say Bye: ArcGIS API for JavaScript, Version 3.x is Retiring in July

697
4
03-28-2024 12:50 PM
YixuanEmilyHu
by Esri Contributor
Esri Contributor
7 4 697
‎03-28-2024 12:50 PM

3x-retirement.png

 

Officially announced February 2023, the 15-year-old legacy ArcGIS API 3.x for JavaScript will be retired on July 1st, 2024. Version 3.46 is the last 3.x version. We fully appreciate all the amazing works you created with the 3.x API over the years.

We strongly encourage you to build all new apps using the more powerful, performant, and modern 2D/3D ArcGIS Maps SDK for JavaScript and migrate 3.x-based apps.

Find more migration resources and FAQs at the retirement blog.

THANK YOU!

4 Comments
Kevin_MacLeod
by
Frequent Contributor
‎04-25-2024 12:30 PM

If there is a more detailed change list for 3.46 would it be possible to see it? More than the generic list of what's new. I have some WAB apps that live on AGOL that broke after the update. I didn't change anything so I am wondering if the update or the AGOL stack update Feb 2024 caused issues.  

 

We will migrate to the new stack, but many or even most apps are still 3x and probably WebApp Builder for most large customers. New viewer and ExpB still lag on functionality with related records, and various WAB widgets. Migrating to Pro is easier than migrating web stacks.  

 

0 Kudos
BjornSvensson
by Esri Regular Contributor
Esri Regular Contributor
‎04-25-2024 03:00 PM

Hi @Kevin_MacLeod , what specific things broke? Do you have a testable URL?

My recommendation is to contact Support and they can help investigate whether it's a JSAPI, WAB, AGOL or something else, issue.  Or if you want to keep it on the Community forums, create a new post. 

As for JSAPI 3.46, there were not really any functional changes in the public API (compared to 3.45). Which is why https://developers.arcgis.com/javascript/3/jshelp/whats_new.html is as short as it is. 

0 Kudos
Kevin_MacLeod
by
Frequent Contributor
‎06-18-2024 06:17 AM

Bjorn it turns out it was some schema changes that did it. Alas it is all internal. All good! Thank you. In general for new API versions, I welcome as much detail as practicable in documentation. 

0 Kudos