conv.data (session data) rots on long sessions of actions.intent.MEDIA_STATUS
See original GitHub issueI occasionally get empty object in conv.data (session data) for actions.intent.MEDIA_STATUS intent.
This bug isn’t easy to reproduce but in long sessions, about an hour or more of media responses, I get empty conv.data
(session data), which we use heavily and it shouldn’t be empty. Because we store playlist there, we lost context with empty session data.
It seems like conv.data rots maybe because actions.intent.MEDIA_STATUS
intents there could be few minutes without any interaction with user.
What is interesting conversation is still active:
{
//...
request: {
conversation: {
conversationId: 'ABwpp....',
type: 'ACTIVE',
conversationToken: '["_actions_on_google"]'
}
//...
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Saving session data for Google Actions with Dialogflow and ...
try conv.data = sessionVars;. to set the variables and access them using conv.data in other intents. data will be lost when the conversation ......
Read more >Storing data during a session and between sessions ... - Medium
The values stored on app.data are persisted as long as the action is running, or until the conversation ends (either by error or...
Read more >Diff - platform/frameworks/base - Google Git
String ACTION_CREATE_LIVE_FOLDER = "android.intent.action. ... +package android.hardware.camera2; /** * The rational data type used by CameraMetadata keys.
Read more >Using a media session - Android Developers
Media sessions provide a universal way of interacting with an audio or video player. By informing Android that media is playing in an...
Read more >Untitled
Mhz to nm conversion calculator, Pludselig sebastian tekst, Rs components spa ... Lev 21 16, Kane vs ryback 2014, Data-wise, Droge schrale mondhoeken, ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah you’d be able to store the timestamp for a session within Firestore, then create a cloud function connected to Cloud Scheduler to clear out old entries.
That’ll work. I believe you’ll need user consent to store data before that’ll pass certification though.
Also there’s
conv.user.userStorage
or similar for that.