Once version 3.x is retired, there will be no further bug fixes or enhancements to the API and hence no further 3.x API deployments to js.arcgis.com. In addition, technical support will no longer be available. Please refer to the Product Lifecycle Support Policy.
We will continue to host both the retired 3.x API versions on our CDN as well as the 3.x documentation site.
Yes. After retirement, the 3.x API will remain hosted on our CDN so that apps that have already been deployed which have a dependency on the API will not break. However, as mentioned above, developers should be mindful that browser updates could introduce new issues which won’t be addressed by API patches.
What action should I take to mitigate the impact of this product retirement?
When will ArcGIS Web AppBuilder retire?
There are three editions of ArcGIS Web AppBuilder.
- Web AppBuilder Developer edition will retire in July 2024, in alignment with the 3.x API.
- Web AppBuilder in ArcGIS Online will retire in the fourth quarter of 2025.
- Web AppBuilder in ArcGIS Enterprise is considered deprecated as of this announcement. Web AppBuilder will continue to be a part of Enterprise until the first half of 2025, at which point it will be retired and no longer released in new versions of Enterprise. Existing versions of Enterprise will continue to be supported in accordance with the ArcGIS Enterprise product lifecycle.
Please review this blog for more information on Web AppBuilder retirement.
When will Map Viewer Classic and ArcGIS Configurable Apps retire?
Map Viewer Classic, and ArcGIS Configurable Apps product life cycles are being managed separately. There are no changes to the product lifecycle stages for these components at this time.