this is a show stopper here for us. I realise why the code is not availible,
but an unhandleble error coming from the lcds swc's is a pain. anyone...?

On Mon, May 25, 2009 at 3:36 PM, Johannes Nel <[email protected]>wrote:

> My bad, we get it on windows as well.
>
>
> On Mon, May 25, 2009 at 2:17 PM, Johannes Nel <[email protected]>wrote:
>
>> Hi All
>>
>> I have a LCDS app which must stay open for ages, deal with dodgy internet
>> connections and all such fun things.
>> Thus far we have managed to get the NetConnection to re-establish itself
>> nicely when the line drops, but here is a wonderful error (which does not
>> actually break the app) that i get after having the app open for a few
>> hours,  only on OS X.
>>
>> So, the fact that it does not touch our code anywhere means that I have no
>> way of trapping this. I would really like some advice on how i can suppress
>> or even catch it.
>>
>>
>>
>> TypeError: Error #1034: Type Coercion failed: cannot convert
>> mx.data.events::dataservicefaultev...@2cb864c1 to
>> mx.messaging.events.MessageFaultEvent.
>>     at mx.data::ConcreteDataService/sendRefreshFault()
>>     at mx.rpc::AsyncResponder/fault()
>>     at mx.rpc::AsyncToken/
>> http://www.adobe.com/2006/flex/mx/internal::applyFault()<http://www.adobe.com/2006/flex/mx/internal::applyFault%28%29>
>>     at mx.rpc.events::FaultEvent/
>> http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()<http://www.adobe.com/2006/flex/mx/internal::callTokenResponders%28%29>
>>     at mx.data::ConcreteDataService/
>> http://www.adobe.com/2006/flex/mx/internal::dispatchFaultEvent()<http://www.adobe.com/2006/flex/mx/internal::dispatchFaultEvent%28%29>
>>     at DataListRequestResponder/fault()
>>     at mx.rpc::AsyncRequest/fault()
>>     at NetConnectionMessageResponder/channelDisconnectHandler()
>>     at flash.events::EventDispatcher/dispatchEventFunction()
>>     at flash.events::EventDispatcher/dispatchEvent()
>>     at mx.messaging::Channel/disconnectSuccess()
>>     at mx.messaging.channels::NetConnectionChannel/internalDisconnect()
>>     at mx.messaging.channels::RTMPChannel/internalDisconnect()
>>     at mx.messaging.channels::RTMPChannel/statusHandler()
>>
>> regards
>> Johan
>> --
>> j:pn
>> \\no comment
>>
>
>
>
> --
> j:pn
> \\no comment
>



-- 
j:pn
\\no comment

Reply via email to