Skip to content

Inconsistent Packet Parsing for Chat Errors #93

@IAmNolanPerry

Description

@IAmNolanPerry

I assume this is similar to #85

I am getting routine messages and several of my other users of my application

WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8738)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8744)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8746)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8751)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8759)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8763)
WARNING: Finished reading ImprovedInstantMessageMessage but we're not at the end of the packet (160 < 161, seq 8768)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions