When calling logout on the identify object the following exception is raised:
Error: ChannelSet is in the process of logging in or logging out.
at mx.messaging::ChannelSet/logout()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\messaging\ChannelSet.as:1172]
at org.granite.tide::Tide/tryLogout()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/Tide.as:2251]
at org.granite.tide::Tide/logout()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/Tide.as:2223]
at org.granite.tide::BaseContext/meta_logout()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/BaseContext.as:1734]
at org.granite.tide.spring::Identity/logout()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/spring/Identity.as:112]
at com.asm.shop.control::LoginCtl/logout()[C:\Users\stefaan\devel\asm\project\head\flex\src\com\asm\shop\control\LoginCtl.as:106]
at Function/
http://adobe.com/AS3/2006/builtin::apply()
at org.granite.tide::Tide/invokeObservers()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/Tide.as:2018]
at org.granite.tide::BaseContext/meta_dispatchEvent()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/BaseContext.as:1471]
at org.granite.tide::BaseContext/meta_componentEventHandler()[/var/bamboo/xml-data/build-dir/GDS-CORE/as3/framework/org/granite/tide/BaseContext.as:1419]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()[C:\autobuild\3.5.0\frameworks\projects\framework\src\mx\core\UIComponent.as:9440]
at Shop/profileEvent()[C:\Users\stefaan\devel\asm\project\head\flex\src\Shop.mxml:149]
at Shop/__loginText_link()[C:\Users\stefaan\devel\asm\project\head\flex\src\Shop.mxml:226]
At Tide.as line 2250 I find the following:
if (ro.channelSet)
ro.channelSet.logout(); // Workaround described in BLZ-310
My UI ends up calling logout twice in succession rapidly (my own bug). Only when this occurs and the granite/tide has not finished processing the first logout, will this error happen.
FYI I'm on spring.