Thanks for pointing this out. It is a bug that we will fix in the next release, caused by the fact that protocol 10010 does not support off-chain data.
For now the workaround is to unsubscribe from the stream, and then re-subscribe to it, now that the chain is running the newer protocol.