No capabilities token error

[alastairong]

Occasionally we receive this error that puts Chaperone in a failure state and requires UI refresh and sign up/in again

Mar 05 10:49:03 hpos holo-envoy[785]: CONDUCTOR CALL ERROR:
Mar 05 10:49:03 hpos holo-envoy[785]: {
Mar 05 10:49:03 hpos holo-envoy[785]:   type: 'error',
Mar 05 10:49:03 hpos holo-envoy[785]:   data: {
Mar 05 10:49:03 hpos holo-envoy[785]:     type: 'zome_call_unauthorized',
Mar 05 10:49:03 hpos holo-envoy[785]:     data: 'No capabilities grant has been committed that allows the CapSecret None to call the function list_channels in zome chat'
Mar 05 10:49:03 hpos holo-envoy[785]:   }
Mar 05 10:49:03 hpos holo-envoy[785]: }
Mar 05 10:49:03 hpos holo-envoy[785]: 2021-03-05T10:49:03.272Z [ index.js   ] ERROR: Failed during Conductor call with error: Error: CONDUCTOR CALL ERROR: {"type":"error","data":{"type":"zome_call_unauthorized","data":"No capabilities grant has been committed that allows the CapSecret None to call the function list_channels in zome chat"}}
Mar 05 10:49:03 hpos holo-envoy[785]: 2021-03-05T10:49:03.272Z [ index.js   ] ERROR: Failed during Conductor call: HoloError: Error: CONDUCTOR CALL ERROR: {"type":"error","data":{"type":"zome_call_unauthorized","data":"No capabilities grant has been committed that allows the CapSecret None to call the function list_channels in zome chat"}}
Mar 05 10:49:03 hpos holo-envoy[785]: 2021-03-05T10:49:03.272Z [ index.js   ]  WARN: Setting error response to raised HoloError: HoloError: Error: CONDUCTOR CALL ERROR: {"type":"error","data":{"type":"zome_call_unauthorized","data":"No capabilities grant has been committed that allows the CapSecret None to call the function list_channels in zome chat"}}
Mar 05 10:49:03 hpos holo-envoy[785]: 2021-03-05T10:49:03.273Z [ index.js   ] NORMA: Returning error: 
Mar 05 10:49:35 hpos holo-envoy[785]: 2021-03-05T10:49:35.325Z [ index.js   ] NORMA: Socket is closing for Agent (uhCAkrHIL5psIUFP0Ob-S9llpOD1-S7ZEhr4DOI3z-RcmtHLCbYFg) using HHA ID uhCkkihH-AGTAffws7BjuJx-aBviIFJw4zarV-KPy0Q8hI2aQDmMB

[timotree3]

This error is caused by using a different agent_id for the zome call than the one the app was installed with. Not sure how that would happen. Do you have any idea what steps can cause it?

[alastairong]

Only that it happened around sign-in / sign-up time. So perhaps it signed in but still tried to use anonymous keys to make this call?

[timotree3]

Seems likely