This looks like a real bug. The "Old application state/New application state" output is from the security manager. I'm not as familiar with this code but I'm guessing it's changing its internal database that tracks the work it has to do, but when it attempts to actually claim the door provider, it fails to do so. 0x9032 is ER_BUS_REPLY_IS_ERROR_MESSAGE.
SecurityApplicationProxy.cc:1035 is calling EndManagement, which suggests the Claim call itself was successful, and EndManagement for some reason is failing. Pawel, I seem to recall you changed Claim such that the app was in the managementStarted state, so this shouldn't be failing. Any ideas? From: Arvind Padole Sent: Tuesday, November 8, 2016 12:54 PM To: Lioy, Marcello <[email protected]>; Josh Spain <[email protected]>; Carrie Hertel <[email protected]>; Kevin Kane <[email protected]>; Pawel Winogrodzki <[email protected]> Cc: '[email protected]' <[email protected]> Subject: RE: Release note ASACORE-3464 We should probably investigate and understand what's going on here before we can decide if it's a blocking bug that must be fixed or just relnoted. From the output, it looks like a minor issue in the secmgr sample in that the provider is claimed but somehow the error is displayed. Adding Pawel as well. Kevin/Pawel - can you take a look to see if my theory above is correct or if there is a different issue here? Please enter the password provided by the application: A02D04 Claiming application ... 110.300 ****** ERROR ALLJOYN_OBJ lepDisp2_0 .../router/AllJoynObj.cc:4466 | 0x9029 110.300 ****** ERROR ALLJOYN_OBJ lepDisp2_0 .../router/AllJoynObj.cc:4466 | 0x9029 110.300 ****** ERROR ALLJOYN_OBJ lepDisp2_0 .../router/AllJoynObj.cc:4466 | 0x9029 >> Old application state : OnlineApplication: Busname: :1E7cCe4y.40, Claim >> state: CLAIMABLE, Sync state: SYNC_UNMANAGED >> New application state : OnlineApplication: Busname: :1E7cCe4y.40, Claim >> state: CLAIMED, Sync state: SYNC_UNMANAGED >> Application id : 9d3d951a5784efa7f84a2eafeb963f5d >> Application name : DoorProvider (CASS-IOT-WIN10) 135.375 ****** ERROR ALLJOYN_SECURITY external ...tyApplicationProxy.cc:1035 | 0x9032 135.375 ****** ERROR SECMGR_AGENT external .../ProxyObjectManager.cc:340 | 0x9032 135.375 ****** ERROR SECMGR_AGENT external ...c/SecurityAgentImpl.cc:516 | 0x9032 Failed to claim application ... From: Lioy, Marcello [mailto:[email protected]] Sent: Tuesday, November 8, 2016 10:49 AM To: Arvind Padole <[email protected]<mailto:[email protected]>>; Josh Spain <[email protected]<mailto:[email protected]>>; Carrie Hertel <[email protected]<mailto:[email protected]>>; Kevin Kane <[email protected]<mailto:[email protected]>> Cc: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: Release note ASACORE-3464 Importance: High Do people thing that we should include ASACORE-3464<https://jira.allseenalliance.org/browse/ASACORE-3464> (Security 2.0 Door Provider on windows 10 must be claimed first<https://jira.allseenalliance.org/browse/ASACORE-3464>) in the release notes? Or is that expected behavior?
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
