#171 [bug] Intermittent failure when sending messages, reactions, replies

[Anonymous]

Originally created by: endernoke
Originally owned by: endernoke

Describe the bug
Sometimes, when a regular message, reaction, or reply is sent from the CLI, the update appears on client-side but disappears after reloading. They also might not show up on Instagram's official clients.
It is observed that reactions sent from official clients made to messages sent from the CLI sometimes do not get registered as well.
Because of the second bug, we suspect that this is caused by instagram's database sync issues with the specific mqtt API we use. It might be because that we are using an deprecated schema or have an incorrect workflow when sending messages.

To Reproduce
Steps to reproduce the behavior:

1. instagram-cli chat
2. Select a chat
3. Send messages and reactions
4. Observe the result from Instagram's web or mobile client

Expected behavior
Every message and rection sent from the CLI should be registered.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Anonymous]

• assigned_to: supreme-gg-gg

[Anonymous]

• assigned_to: endernoke

[Anonymous]

Originally posted by: endernoke

Temporary fix is available by forcing chat to not use realtime:

// instagram-ts/commands/chat.tsx
// ...
export default function Chat({args}: Properties) {
    const {client, isLoading, error} = useInstagramClient(args[0], { realtime: false });
// ...

[!WARNING]
This makes the client use RESTful API for sending messages which might significantly raise the risk of your account getting flagged by instagram since the offcial clients don't use this.

We might add a config for this soon.

[Anonymous]

Originally posted by: supreme-gg-gg

Temporary fix is available by forcing chat to not use realtime:

// instagram-ts/commands/chat.tsx // ... export default function Chat({args}: Properties) { const {client, isLoading, error} = useInstagramClient(args[0], { realtime: false }); // ...

Warning

This makes the client use RESTful API for sending messages which might significantly raise the risk of your account getting flagged by instagram since the offcial clients don't use this.

We might add a config for this soon.

I think we can use mixed client no? Just instantiate realtime for receiving, but still use the API client for sending, I think this will not make it more likely to flag your account