ArcGIS Server 11.1: accent not properly encoded when "returnAdvancedSymbols"

[NicolasGIS]

Hello,

Since I upgraded from ArcGIS Enterprise 11.0 to ArcGIS Enterprise 11.1, many of my ArcGIS Field maps are broken.

In Field Maps, I have the following error:

[LOADING] Layer (Arrêts d'urgence AUG) failed to load with error: Error Domain=com.esri.arcgis.runtime.error Code=2 "Invalid argument" UserInfo={NSLocalizedFailureReason=UTF8 contains invalid characters, NSLocalizedDescription=Invalid argument., Additional Message=UTF8 contains invalid characters}

When debugging with Fiddler, I noticed that the following request:

https://agsserver.company.com/arcgis/rest/services/MyServer/FeatureServer/3?f=json&returnAdvancedSym...

returns badly encoded accent letters (I am French):

The funny thing is that if I remove 'returnAdvancedSymbols' parameter, it is clean:

I made a test with an ArcGIS Server 11.0 and even if 'returnAdvancedSymbols' parameter is specified, the response is properly encoded.

I also made a test to bypass WebAdaptor 11.1 thinking it might be the culprit but I am getting the same poorly encoded reply from ArcGIS Server.

Thanks !

NB: The error is from IOS FieldMaps. On android it does not crash but I have this weird � character instead

[TanuHoque]

It appears to be this bug that you are running into. We will try to resolve this as soon as we can.

BUG-000158047

[NicolasGIS]

Thanks for the quick reply @TanuHoque.

I will ask support to attach my case to this one. Out of curiosity, what’s the title ?

Also what is the ETA for the patch ? Hours, days, weeks, months ? My users can’t go on the field right now and I would like to know whether it is worth modifying all my domains, symbology and feature services for critical services like fire fighters ?

Thanks

[TanuHoque]

@NicolasGIS 

here is the title of the bug:
"Encoding in Response (effected non ascii-characters) is not correct, on 2nd request againts MapService with returnAdvancedSymbols=true"

About the ETA, unfortunately I don't have anything to share at this point 😞 Thanks for letting us know that this is very critical for you. I will try out best to get a resolution as soon as we can.

As for a patch request, please reach out to support to request for one. That is beyond me.

Sorry that I don't have any good news for you... but I will keep you updated as we make progress.

[NicolasGIS]

Thanks for your reply @TanuHoque .

True, I had noticed that first request is correct: I had thought the problem was solved after republishing 😅

[LiisiPark]

We run into the same issue. Is there any hope to fix te issue soon?

[NicolasGIS]

Hello @LiisiPark ,

I personally asked for a patch on MyESRI.  The BUG reported me yesterday that it will be fixed at 11.2. If you want a patch for 11.1, I understood you should ask to ESRI support to be attached to this BUG and then you can also ask for a patch on MyESRI. The more people complain, the more we get a chance to get  a patch from what I understood.

[TanuHoque]

hi everyone,

I just wanted to provide an update here.

We are investigating with the intention to patch. Hopefully it will be released soon to all of you. When it does, I will update this thread too.

We appreciate your patience and bring this issue to our attention in the first place.

Thanks a lot

[schenardi]

This patch is absolutely urgent for us as well. 

[TanuHoque · Accepted solution]

hello folks,

Thanks a lot for your patience and understanding. I'm happy to share that we were able to release a fix for this issue as a patch.

Here is the url to the patch:
https://support.esri.com/en-us/patches-updates/2023/arcgis-server-11-1-map-service-and-custom-data-f...

please let us know if you run into any issues.

Thanks

Tanu