On 3/27/2016 12:30 PM, Alex Harui wrote:
It looks to me that a server request has returned with a successful result, but the esri handler decided there was something wrong and is calling an error handler (handleError), which tries to call the fault() handler on that server request. The function signature on that fault handler is expecting a FaultEvent when it either should expect an mx.rpc.Fault, or maybe handleError passed an mx.rpc.Fault when it should have passed a FaultEvent.
so likely a bug in the ESRI lib? they abandoned flex so i guess this is now a feature :-( not a show stopper, i guess we can live with it.
If you can catch this in the debugger, there should be more information in the various objects to further help you figure out which request is doing this. I don't know this code at all, but it could be that ESRI is checking for licensing or authentication when the request is successful.
bingo. yes it was an out-dated security token. this client has serious network issues & the bits that grabbed the token hasn't been able to connect to the authorizing server since late-2015. this functionality only gets used on occasion so nobody noticed. now to see why no errors were logged.
many thanks again.
