You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loaded class definition for com.smartnews, module type: org.thingpedia.v2, version: 13
Cached module com.smartnews is out of date (found 14, want 13)
stdout Archive: /tmp/thingengine-com.smartnews--1-RSTSN15kzKeY-.zip
stderr
Cached module com.smartnews is out of date (found 14, want 13)
TypeError: deviceClass is not a constructor
at /opt/almond-cloud/node_modules/thingpedia/dist/factory.js:133:20
at async DeviceDatabase.addSerialized (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/engine/devices/database.js:314:26)
at async ExecutionDialogueAgent.tryConfigureDevice (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/execution_dialogue_agent.js:115:28)
at async ExecutionDialogueAgent._chooseDevice (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/abstract_dialogue_agent.js:230:28)
at async ExecutionDialogueAgent._prepareForExecution (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/abstract_dialogue_agent.js:198:17)
at async ExecutionDialogueAgent.execute (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/abstract_dialogue_agent.js:105:13)
at async ThingTalkDialogueHandler._executeCurrentState (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/handlers/thingtalk.js:369:81)
at async DialogueLoop._handleUserInput (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/dialogue-loop.js:308:27)
at async DialogueLoop._loop (/opt/almond-cloud/node_modules/genie-toolkit/dist/lib/dialogue-agent/dialogue-loop.js:354:21)
The text was updated successfully, but these errors were encountered:
Actually, it seems that the version number is going backwards. I think there is some confusion with developer keys? At the time of this issue, version 13 was approved, version 14 was developer only. The user that noticed this issue was not a developer and was running on the shared cloud backend.
From the logs:
The text was updated successfully, but these errors were encountered: