Sean Hagstrom

Hey @chaitanyaprem thanks for analysis, great stuff 🙌 I've attempted to reproduce this glitch again, but this time I reproduced the .glitch using a combination of an iOS simulator for...

Here's some updated logs and context from reproducing this glitch: - It was difficult to reproduce this glitch, so it took me multiple attempts of disconnecting the iOS device from...

Some follow-up notes: - What’s interesting is that the message does make it through to the physical iOS device, but it seems to be invalid because of `received messagepush with...

It seems that a contentTopic filter is marked as Ephemeral here: https://github.com/status-im/status-go/blob/3179532b645549c103266e007694d2c81a7091b4/protocol/messenger_store_node_request_manager.go#L284 I've checked around and added some logs debug logs for a contentTopic being Ephemeral, and it doesn't seem...

I've reproduced the issue again and this the logs will focus on: - `contentTopic` is `0x479e6e55` - missing `messageID` `0x850e6ac49c6f715d17fab609cbcf4faf813f51f601321256184caecade741a00` So far it seems like there are some issues with...

@chaitanyaprem yup yup I'll test those changes, sorry for the delay, should be able to try them out and post some results soon.

Okie dokie I've run the experiment again with both the the iOS simulator and iOS device running the patched code in your branch. Though I did need to rebase your...

@chaitanyaprem Yup yup I'll re-run by tests and share soon --- > Can you point me to the messageID of the message so that i can trace it in the...

Okay I've re-run my tests with the updated changes in your status-go branch - Overview - This time I was able to reproduce the issue by disconnecting the network, waiting...

Hey @chaitanyaprem 👋 Is there anything else I can do to help with this issue? 🙏