Flex Viewer 3.2 GP Widget upload using 10.1.1 returns 'token required'

[ZacharyHart]

Flex Viewer 3.2
installed on ArcGIS Server 10.1.1
Secured services; map services access fine, adding and configuring the GP service to the widget goes fine
When attempting to navigate to a local file for upload, after file is selected, the error 'token required' is returned.

GP service & map services secured with the same authentication credentials; no proxy used in the application; all other secured services are accessible as expected.

[ZacharyHart]

Thank you for reporting this - we've now been enabled to reproduce it.  I think the problem is only for "file upload".  All other parameter types work fine.  (So it's not related to "that other 3.2 GP issue")

See https://github.com/Esri/arcgis-viewer-flex/issues/120.

Bjorn,

I've installed Flash Builder on my local system away from my server. I moved the re-compiled project over to the server, added the GP service and it works. So there's some joy there. However, as a ongoing workflow, will I have to do this each time and then configure my application? Or, can i just replace something in the builder templates?

[BjornSvensson]

I've installed Flash Builder on my local system ... and it works. So there's some joy there. However, as a ongoing workflow, will I have to do this each time and then configure my application? Or, can i just replace something in the builder templates?

This was all part of version 3.3 that was released this week. You no longer have to do this yourself.

[ChrisNorth]

Hi,

I am having a related problem with version 3.6 of the Flex Viewer.  I have token secured GP services. Server is 10.1.1. When I try to access them form the GP Widget, I am first prompted to login.  When I cancel that, t he widget then appears, but when I click "Submit" I get an error message that says "Could not determine geoprocessing execution type:". 

From what I've read this was supposed to be fixed in 3.3.  The widget and  same GP service works as-is in version 3.1 of the flex viewer.

I checked the source coud in v3.6 against all the suggested fixes, and they're there for 3.6

I'm stumped.