Debug into the blazeDS call and see how it sets up the responders. The
responders should be listening for a response from NetConnectionChannel, I
Thanks. I debugged from NetConnectionChannel but could not find the class that outputs the TypeError message.
I am now trying to find the location using the netmonitor. I can correlate the time of the TypeError message with the response in netmonitor and then view the raw AMF response. I was hoping that I could find the 'Object@df1d551' as ASObject(233952593) in the output, but no luck. I guess I am on the wrong track.
The AMF responses are huge, so manually finding all the errors is not really an option.
Anybody who knows which class generates this message so I can debug?
What does that stack look like when the excpetion is thrown? What class does the debugger think is throwing the exception?
That's the whole point. There is no exception, just a message in the console.