ArcGIS API 3.4 for Flex released July 3, 2013!!

[HeatherGonzago]

Today we've released version 3.4.

Read the details in the What's new documentation.

You may have already noticed that our documentation for the API has moved from http://resources.arcgis.com/en/communities/flex-api/ to the new https://developers.arcgis.com/en/flex/ site on developers.arcgis.com.

We are excited about this move and new format. Please take some time to navigate around this site to become more familiarized with its layout.

This release focused on data validation, Portal for ArcGIS, ArcGIS for Organizations, and ArcGIS Online integration, in addition to map and legend updates (to name just a few.)

For a complete list of "what's new" in addition to updated concepts/documentation, please refer to the ArcGIS API for Flex Home page and the What's new in 3.4 documentation.

[PaulHastings1]

just re-compiled our main app w/3.4 & the compiler threw a bunch of "Uncaught exception in compiler" errors. the error details look like this: https://issues.apache.org/jira/browse/FLEX-33155 FB version: 4.6, flex version: Apache 4.9.1

before i do the workaround dance, can you confirm this release was compiled w/java 1.7?

thanks.

[PaulHastings1]

couldn't wait (too many timezones 😉

probably best to ignore the workaround advice in that jira post (at least for FB4.6 plugin). just add "-Djava.util.Arrays.useLegacyMergeSort=true" to the eclipse.ini vm args.

you guys might want to note this someplace.

[SebastianZarzycki]

It looks like something's wrong with this build (agslib-3.4-2013-06-30.swc). It still asks (throws error) for mx.swc (mx.controls.DateField). It wasn't the case with 3.3 - it shouldn't be needed?

I don't use AttributeInspector nor any custom skins. The error triggers right after runtime initialization, no matter if any map component is used in code.

[MatthewMah]

I have the same problem identified by rattkin for all mobile projects with the 3.4 API. There is no problem with the 3.3 API.