Signal desktop app says "Disconnected" with active Internet connection

ATL-Flaneur commented 1 year ago

[x ] I have searched open and closed issues for duplicates
[x ] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

Signal desktop app says "Disconnected" on a machine with an active Internet connection.

Steps to Reproduce

Launch Signal
Get yellow box: "Disconnected. Check your network connection. Click to reconnect."
Click box.
Text changes to: "Connecting… Shouldn't be long"
Go back to 2.

This is the first time I've had this problem. Perhaps not coincidentally, we're staying at a place with T-Mobile 5G Internet service. Oddly, the Signal app on my WiFi-only iPad is not experiencing this problem and sends/receives Signal messages just fine. It's only my MBP that the app can't connect.

Screenshots

Platform Info

Signal Version:

Signal 6.16.0 production (Apple silicon)

Operating System:

MacOS 13.3.1 (22E261)

Linked Device Version:

Link to Debug Log

debuglog.txt

geustace commented 1 year ago

The prod of 6.20 fixed it for me and updating to 6.20.1 it is still fixed. I have a dual stack environment. With 6.19 turning off IPv6 was a work around but not something I can do as I need IPv6 for other applications.

Message ID: @.***>

--

(√-1) 2^3 ∑ π it was delicious

The world cant be flat, if it was the cats would have pushed everything over the edge by now!

krosseyed commented 1 year ago

Looks like 6.20.2 fixed the issue. Thanks!

indutny-signal commented 1 year ago

Hooray! Glad to hear that!

krosseyed commented 1 year ago

Looks like there was an issue with MTU settings, as I had run into other issues with apps after using signal for a bit. It wasn't working well on my phone and after changing it to 1452, things seemed to work a bit better.

sbbgromit commented 1 year ago

It's baaaaack on intel or apple silicon v 6.21 with Ventura all latest os.... Been doing this for about a month now, and 6.20.1 was working, but the new update broke it!

TomJD commented 1 year ago

Can confirm this is the case with Windows 10 as well on 6.21

llebout commented 1 year ago

Happened briefly on 6.21.0 on Linux x86, but then it started working OK again, can confirm I had proper DNS etc Internet access while it happened.

jon-signal commented 1 year ago

Friends: if you're still following this issue and were previously having problems with curl -6 -k https://chat.signal.org/, could you please give it another try now and let us know if anything has changed?

byzantines0ldier commented 1 year ago

Still an issue, was using 6.18 until today with no problems but now its expired.

I can seemingly receive news messages, but I cannot send any... there is a circle spinning next to the text bubble.

On latest OSX os + signal version

trevor-signal commented 1 year ago

@byzantines0ldier sorry to hear that -- can you share a debug log so we can take a look?

marlock9 commented 1 year ago

I also have what @byzantines0ldier described Debug log right after it happened: https://debuglogs.org/desktop/6.22.0/431ca38fd544cddafd068ae75749e9331a8c12f38ef037d4d294860b94b382a5.gz

byzantines0ldier commented 1 year ago

Can you please make 6.18 available again?! Its been weeks this issue is open. At least give us an option to roll back while you fix the problem.

byzantines0ldier commented 1 year ago

I deleted all my firewall rules and re-allowed Signal to query and now things seem to work.

Something must have changed with how you handle your traffic that was previously not required (and could be blocked by firewall) but now thats no longer the case.

scottnonnenberg-signal commented 1 year ago

@byzantines0ldier What were the firewall rules you deleted? That would help give us a key to what went wrong in in your scenario.

byzantines0ldier commented 1 year ago

It was for "Electron Helper" -- someone else had mentioned it in a comment a few weeks ago.

For some reason this could be blocked in earlier versions of Signal but not anymore.

NoXPhasma commented 1 year ago

@jon-signal

> curl -6 -k https://chat.signal.org/
curl: (7) Failed to connect to chat.signal.org port 443 after 1 ms: Couldn't connect to server

And when I try to reach https://chat.signal.org/ in firefox I get a SEC_ERROR_UNKNOWN_ISSUER error.

indutny-signal commented 1 year ago

Sorry, but it looks like the original issue is back. I'll keep you posted on our progress in resolving it.

wendybujalski commented 1 year ago

I am experiencing this same issue on Windows 10 running the Signal desktop app version 6.26.0

RX14 commented 1 year ago

Hi, I run my own network and I have a short ipv6 path to amazon, so I might be of some use debugging this issue. From my debugging I think it is likely something on amazon's end is droping ICMPv6 packet too big messages, breaking PMTUD.

My route to chat.signal.org:

mtr -rwb -c 1 chat.signal.org
Start: 2023-08-23T13:34:38+0200
HOST: uiharu.iscute.moe                                                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2a11:f2c0:acac:10::1                                                                            0.0%     1    0.6   0.6   0.6   0.6   0.0
  2.|-- flag.shinra.systems (2a0d:1a40:7a02::1)                                                         0.0%     1   12.4  12.4  12.4  12.4   0.0
  3.|-- core1.fra1.as207960.net (2a0d:1a40:7900:8::1)                                                   0.0%     1   14.2  14.2  14.2  14.2   0.0
  4.|-- xe05-cr02-fra01.ifog.ch (2a0c:9a40:1030::1)                                                     0.0%     1   14.5  14.5  14.5  14.5   0.0
  5.|-- decix1.amazon.com (2001:7f8::407d:0:1)                                                          0.0%     1   15.7  15.7  15.7  15.7   0.0
  6.|-- 2a01:578:0:8002::183                                                                            0.0%     1   14.5  14.5  14.5  14.5   0.0
  7.|-- 2a01:578:0:8102::645f:631                                                                       0.0%     1   16.9  16.9  16.9  16.9   0.0
  8.|-- 2a01:578:0:11::6d                                                                               0.0%     1   16.5  16.5  16.5  16.5   0.0
  9.|-- ac88393aca5853df7.dualstack.awsglobalaccelerator.com (2600:9000:a507:ab6d:4ce3:2f58:25d7:9cbf)  0.0%     1   15.3  15.3  15.3  15.3   0.0

I have a 1400 MTU link between hop 1 and 2 on this link. I have verified that ICMPv6 packet too big messages are being sent back from another machine:

ping -s 1400 2a11:f2c0:acac:10::1
PING 2a11:f2c0:acac:10::1(2a11:f2c0:acac:10::1) 1400 data bytes
From 2a0d:1a40:7a02::1 icmp_seq=1 Packet too big: mtu=1400
1408 bytes from 2a11:f2c0:acac:10::1: icmp_seq=2 ttl=52 time=118 ms

When I don't have TCP MSS clamping enabled on my router (2a11:f2c0:acac:10::1) then curl -6 -k -v https://chat.signal.org/ will hang. When MSS clamping is enabled, the issue disappears.

Here is a tcpdump of connections. The first dump is with MSS clamping enabled (working), and the second is without MSS clamping, relying on PMTUD and ICMP delivery:

13:17:16.721807 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [S], seq 1737552093, win 64800, options [mss 1440,sackOK,TS val 4027709925 ecr 0,nop,wscale 7], length 0
13:17:16.738334 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [S.], seq 3202106923, ack 1737552094, win 65535, options [mss 1340,sackOK,TS val 2394619425 ecr 4027709925,nop,wscale 8], length 0
13:17:16.738424 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 1, win 507, options [nop,nop,TS val 4027709941 ecr 2394619425], length 0
13:17:16.742283 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [P.], seq 1:518, ack 1, win 507, options [nop,nop,TS val 4027709945 ecr 2394619425], length 517
13:17:16.758277 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [.], ack 518, win 261, options [nop,nop,TS val 2394619445 ecr 4027709945], length 0
13:17:16.940592 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [.], seq 1:2657, ack 518, win 261, options [nop,nop,TS val 2394619628 ecr 4027709945], length 2656
13:17:16.940654 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 2657, win 494, options [nop,nop,TS val 4027710144 ecr 2394619628], length 0
13:17:16.941610 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 2657:3571, ack 518, win 261, options [nop,nop,TS val 2394619628 ecr 4027709945], length 914
13:17:16.941673 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 3571, win 501, options [nop,nop,TS val 4027710145 ecr 2394619628], length 0
13:17:16.943888 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [P.], seq 518:644, ack 3571, win 501, options [nop,nop,TS val 4027710147 ecr 2394619628], length 126
13:17:16.959698 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [.], ack 644, win 261, options [nop,nop,TS val 2394619646 ecr 4027710147], length 0
13:17:17.050741 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 3571:3622, ack 644, win 261, options [nop,nop,TS val 2394619738 ecr 4027710147], length 51
13:17:17.050742 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 3622:3691, ack 644, win 261, options [nop,nop,TS val 2394619738 ecr 4027710147], length 69
13:17:17.051124 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 3691, win 501, options [nop,nop,TS val 4027710254 ecr 2394619738], length 0
13:17:17.051183 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [P.], seq 644:746, ack 3691, win 501, options [nop,nop,TS val 4027710254 ecr 2394619738], length 102
13:17:17.051289 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [P.], seq 746:815, ack 3691, win 501, options [nop,nop,TS val 4027710254 ecr 2394619738], length 69
13:17:17.066914 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [.], ack 746, win 261, options [nop,nop,TS val 2394619754 ecr 4027710254], length 0
13:17:17.066916 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [.], ack 815, win 261, options [nop,nop,TS val 2394619754 ecr 4027710254], length 0
13:17:17.159351 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 3691:3729, ack 815, win 261, options [nop,nop,TS val 2394619845 ecr 4027710254], length 38
13:17:17.159790 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 3729:3887, ack 815, win 261, options [nop,nop,TS val 2394619845 ecr 4027710254], length 158
13:17:17.159791 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [P.], seq 3887:3925, ack 815, win 261, options [nop,nop,TS val 2394619846 ecr 4027710254], length 38
13:17:17.159941 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 3925, win 501, options [nop,nop,TS val 4027710363 ecr 2394619845], length 0
13:17:17.160233 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [F.], seq 815, ack 3925, win 501, options [nop,nop,TS val 4027710363 ecr 2394619845], length 0
13:17:17.174743 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.48382: Flags [F.], seq 3925, ack 816, win 261, options [nop,nop,TS val 2394619862 ecr 4027710363], length 0
13:17:17.174816 IP6 uiharu.iscute.moe.48382 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 3926, win 501, options [nop,nop,TS val 4027710378 ecr 2394619862], length 0

13:20:12.838466 IP6 uiharu.iscute.moe.49512 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [S], seq 3052941568, win 64800, options [mss 1440,sackOK,TS val 2177835737 ecr 0,nop,wscale 7], length 0
13:20:12.853196 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.49512: Flags [S.], seq 692329973, ack 3052941569, win 65535, options [mss 1440,sackOK,TS val 2268849587 ecr 2177835737,nop,wscale 8], length 0
13:20:12.853292 IP6 uiharu.iscute.moe.49512 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 1, win 507, options [nop,nop,TS val 2177835752 ecr 2268849587], length 0
13:20:12.857183 IP6 uiharu.iscute.moe.49512 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [P.], seq 1:518, ack 1, win 507, options [nop,nop,TS val 2177835756 ecr 2268849587], length 517
13:20:12.873118 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.49512: Flags [.], ack 518, win 261, options [nop,nop,TS val 2268849607 ecr 2177835756], length 0
13:20:13.099023 IP6 ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https > uiharu.iscute.moe.49512: Flags [P.], seq 2857:3571, ack 518, win 261, options [nop,nop,TS val 2268849833 ecr 2177835756], length 714
13:20:13.099078 IP6 uiharu.iscute.moe.49512 > ac88393aca5853df7.dualstack.awsglobalaccelerator.com.https: Flags [.], ack 1, win 507, options [nop,nop,TS val 2177835998 ecr 2268849607,nop,nop,sack 1 {2857:3571}], length 0

Notice how the connection hangs in the broken connection around the time the first large packet is sent by the working connection. Also notice the hole in the sequence numbers in the broken connection, and the subsequent ACK with selective ack sent due to the missing packet. The packet which should be retransmitted is still not delivered after 10 seconds, implying a MTU issue.

Due to this, I can only conclude there is a firewall dropping ICMPv6 packet too big on the path. I believe that firewall to be on amazon's side, since the other hops on the path are pure transit providers and are unlikely to be running firewalls in the forwarding path.

jon-signal commented 1 year ago

Thanks, @RX14. We've come to the same conclusion and are already working with Amazon to resolve the issue. This additional testing is very helpful, and we really appreciate the detailed investigation!

ca-boh commented 1 year ago

This just started to happen to me.....random, frequent yellow box: "Disconnected. Check your network connection. Click to reconnect."

Seems to also happen with desktop WhatsApp...

scottnonnenberg-signal commented 1 year ago

We're tracking this connectivity issue here: https://github.com/signalapp/Signal-Desktop/issues/6476

AndrewBendigo commented 1 year ago

Hello, I found this page because Signal app on my Macbook air was cycling the disconnected message on and off. It occurred as I set up a new computer. I checked the old computer - also happening for the first time. Shut down Signal on the old machine and the problem vanished. Thought that observation might help.

scottnonnenberg-signal commented 1 year ago

@AndrewBendigo You'll probably see some decryption errors as well. You had two Signal Desktops conflicting with each other, each trying to connect and booting the other. You should probably unlink that Desktop, and link them again from your phone - if you re-link to the same account, you won't lose any old messages.

reebalazs commented 1 year ago

Just for the record I had the Disconnected message appearing and disappearing forever, also loosing messages. The reason was that I migrated my Mac to a new one. So the Signal app on the new machine inherited the same id from the one on the old machine. Unlinking the machine and linking them separately fixed the problem.

khuopio commented 10 months ago

The same issue is with me on Windows 11, with ipv4/6 connectivity providet by Telenet in Belgium. If I enable F-Secure Freedome VPN terminating to Finland, the problem goes away.

grammophone commented 10 months ago

I just got this behavior on my Signal running on Windows 10. It is happening with all network connections; mobile hotspot, wifi's, everything. The proof that I have internet despite what Signal says is this very comment.

scottnonnenberg-signal commented 10 months ago

@grammophone Signal had a short outage in the last hour, sorry for the inconvenience. The good news is that you weren't seeing a Desktop bug there!

grammophone commented 10 months ago

Thank you for looking after the issue, @scottnonnenberg-signal !

landsolar commented 9 months ago

Manjaro user here Signal 6.43.2

Not connecting when USB tethering with Azilink on the phone (abd based tethering). Firefox or Chromium are working fine.

Here is the ovpn file content used on the laptop:

dev tun

remote 127.0.0.1 41927 tcp-client ifconfig 192.168.56.2 192.168.56.1 route 0.0.0.0 128.0.0.0 route 128.0.0.0 128.0.0.0 socket-flags TCP_NODELAY keepalive 10 30 dhcp-option DNS 192.168.56.1

Tests:

$ curl -6 -k https://chat.signal.org/ curl: (7) Failed to connect to chat.signal.org port 443 after 134 ms: Couldn't connect to server $ curl -4 -k https://chat.signal.org/ {"code":404,"message":"HTTP 404 Not Found"}

jamiebuilds-signal commented 9 months ago

@landsolar Could we get a debuglog?

landsolar commented 9 months ago

app.log main.log

indutny-signal commented 9 months ago

@landsolar Thank you for the log! Did you save this log right after turning on the tether mode? The connection to our server appears to be healthy at glance.

landsolar commented 9 months ago

The log show only tether connection. I did not use other connection type since 2 weeks.

I use azylink on android on usb

Signal Desktop connect fine if I use my phone Hotspot on the same line

indutny-signal commented 9 months ago

Ah, I see it now. Thanks! We will take a look.

Apikorus commented 9 months ago

On an Apple M3 MacBook Pro running Sonoma 14.3 WiFi should be strong in a faculty office at a major research university The message flashes with a periodicity of approximately 3s I am apparently able to use Signal while this is happening, but the flashing is a little irritating and so I'd appreciate a bug fix if the problem is with Signal.

ayumi-signal commented 9 months ago

Hi @Apikorus, sorry this is happening for you.

Can you please share a debug log when this situation is happening?
Regarding your app/computers setup -- is there a chance you've copied your data directory between multiple computers? We've seen periodic disconnections happen in that case as the multiple installs try to simultaneously connect.

Apikorus commented 9 months ago

Thanks. Here is link for debug log:

https://debuglogs.org/desktop/6.45.1/ddcde0e96a14cb5504d131e33178d1fbbc756daac14f466beb98f99691b7bdea.gz
ddcde0e96a14cb5504d131e33178d1fbbc756daac14f466beb98f99691b7bdea Archive · 3.5 MB

I’m not sure what you mean by copying my data directory between multiple computers, but I do use Signal on multiple computers. If that is a problem, what can I do?

-Daniel

On Jan 29, 2024, at 1:03 PM, ayumi-signal @.***> wrote:

Hi @Apikorus https://github.com/Apikorus, sorry this is happening for you.

Can you please share a debug log when this situation is happening? Regarding your app/computers setup -- is there a chance you've copied your data directory between multiple computers? We've seen periodic disconnections happen in that case as the multiple installs try to simultaneously connect. — Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Desktop/issues/6393#issuecomment-1915283100, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFU2WYFN5KCOWGS7UUIBNKTYQ7QAZAVCNFSM6AAAAAAXRATHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGI4DGMJQGA. You are receiving this because you were mentioned.

ayumi-signal commented 9 months ago

@Apikorus Thanks for the logs!

It looks like the same desktop linked instance is trying to connect:

WARN  2024-01-29T19:05:53.149Z SocketManager: authenticated socket closed with code=4409 and reason=Connected elsewhere

This can happen when you copy Signal data folders between computers to install, such as with MacOS Migration Assistant or just copying folders around.

You can resolve this by relinking the computers. This would preserve your existing messages on the computers.

Use your primary device to unlink the Desktop instances. On your primary Signal iOS or Android go to Settings -> Linked Devices and unlink the Desktop instance(s).
On each computer, the app will prompt the banner "Unlinked; relink to continue". Proceed with the relink and that computer will be fixed.
Repeat for other computers. (Note there's a max of 5 linked devices.)

Apikorus commented 9 months ago

Thanks, but I’m still not sure what to do here. I am on sabbatical leave away from my home institution. I was running Signal on four machines:

Office iMac
Home iMac
MacBook (no longer being used)
new MacBook

I only have access to #4 for the next several months. I am not even sure what my “primary device” is.

When I open my Signal settings on machine #4, I see the following:

I don’t see anything about “instances.”

-Daniel

On Jan 29, 2024, at 2:24 PM, ayumi-signal @.***> wrote:

@Apikorus https://github.com/Apikorus Thanks for the logs!

It looks like the same desktop linked instance is trying to connect:

WARN 2024-01-29T19:05:53.149Z SocketManager: authenticated socket closed with code=4409 and reason=Connected elsewhere This can happen when you copy Signal data folders between computers to install, such as with MacOS Migration Assistant or just copying folders around.

You can resolve this by relinking the computers. This would preserve your existing messages on the computers.

Use your primary device to unlink the Desktop instances. On your primary Signal iOS or Android go to Settings -> Linked Devices and unlink the Desktop instance(s). On each computer, the app will prompt the banner "Unlinked; relink to continue". Proceed with the relink and that computer will be fixed. Repeat for other computers. (Note there's a max of 5 linked devices.) — Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Desktop/issues/6393#issuecomment-1915407207, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFU2WYAPY5HP3ECQID3WQVLYQ7ZNZAVCNFSM6AAAAAAXRATHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGQYDOMRQG4. You are receiving this because you were mentioned.

ayumi-signal commented 9 months ago

@Apikorus The first (primary) device is always an iOS or Android device, so you need to find the original mobile phone you used to first install Signal. On the mobile app, access Settings -> Linked Devices to unlink the desktop instances.

Apikorus commented 9 months ago

I really appreciate your patience. Signal is installed on my iPhone 13. I suppose I had it installed on my previous iPhone 8 but I no longer have that device. Here’s what the linked devices page says on my current iPhone:

I don’t see how to unlink anything here.

On Jan 29, 2024, at 4:05 PM, ayumi-signal @.***> wrote:

@Apikorus https://github.com/Apikorus The first device is always an iOS or Android device, so you need to find the original mobile phone you used to first install Signal. On the mobile app, access Settings -> Linked Devices to unlink the desktop instances.

— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Desktop/issues/6393#issuecomment-1915564097, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFU2WYACNAU7RFG4ZZHNZKLYRAFH3AVCNFSM6AAAAAAXRATHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGU3DIMBZG4. You are receiving this because you were mentioned.

ayumi-signal commented 9 months ago

@Apikorus I cannot see any picture you may posted, but on the iOS Linked Devices page there's a top right Edit text button, when pressed it will reveal the delete buttons next to each linked device.

Apikorus commented 9 months ago

Thanks that seems to have worked.

On Jan 29, 2024, at 4:26 PM, ayumi-signal @.***> wrote:

@Apikorus https://github.com/Apikorus I cannot see any picture you may posted, but on the iOS Linked Devices page there's a top right Edit text button, when pressed it will reveal the delete buttons next to each linked device.

— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Desktop/issues/6393#issuecomment-1915600862, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFU2WYFL5CYNN27MLADFH4LYRAHY3AVCNFSM6AAAAAAXRATHZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGYYDAOBWGI. You are receiving this because you were mentioned.

signalapp / Signal-Desktop