Open Hetti opened 3 years ago
This is not anymore the case in the newest build.
Still having problems with https://github.com/signal-golang/textsecure/issues/43 and writing messages to numbers, but this is another problem.
ah it's still an issue, if I revoke from phone messenger
Can you try with latest v1.7.0 and if it happens again, please paste the error again here. Thanks
I just tested it. Now the Bot autojoins in Groups after invite :heart: Still, if you kick the Textsecure Client from the Group it Segfaults with SIGSEGV (but it seems, that the account is properly removed from the group)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x934f63]
goroutine 1 [running]:
github.com/signal-golang/textsecure.handleDataMessage(0xDUMMY0, 0xd, 0xDUMMY1, 0x24, 0xDUMMY2, 0xDUMMY3, 0x0, 0x38)
/go/pkg/mod/github.com/signal-golang/textsecure@v1.7.1/handler.go:86 +0x123
github.com/signal-golang/textsecure.handleMessage(0xDUMMY0, 0xd, 0xDUMMY1, 0x24, 0xDUMMY2, 0xDUMMY4, 0xfe, 0x150, 0x209, 0x240)
/go/pkg/mod/github.com/signal-golang/textsecure@v1.7.1/handler.go:22 +0x606
github.com/signal-golang/textsecure.handleReceivedMessage(0xDUMMY5, 0x209, 0x240)
/go/pkg/mod/github.com/signal-golang/textsecure@v1.7.1/textsecure.go:591 +0x7a5
github.com/signal-golang/textsecure.StartListening(0x0, 0x0)
/go/pkg/mod/github.com/signal-golang/textsecure@v1.7.1/websocket.go:194 +0x713
main.main()
/go/pkg/mod/github.com/signal-golang/textsecure@v1.7.1/cmd/textsecure/main.go:669 +0x6cb
I found a reproducible Crash in the textsecure Client
So running textsecure in Combination with a Desktop Client ist still bugging for me. For example Group Invites not working (like https://github.com/signal-golang/textsecure/issues/43) and I can't read the messages on the Desktop Client as it only states all the time "Unterhaltungssitzung aktualisiert" on the Desktop Client.
So for the SIGSEGV Crash; How to reproduce:
1) Make Group 2) Invite Textsecure Client Number 3) Client will be invited but does not automatically accepts invitations, therefore there is an open invitation for that client 4) Revoke invitation for the invited textsecure client 5) SIGSEGV
I replaced some of the values with 0xDUMMY. If needed, I can share in private the full logs.