Signal-ios: Getting “No available session for contact” error

Created on 29 Dec 2019 · 9Comments · Source: signalapp/Signal-iOS

[x] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[x] This isn't a feature request or a discussion topic

Bug description

Getting the dreaded “No available session for contact” error with a single contact. This only happens with a single contact and that contact has iPad and iOS devices linked.

I just changed SIMs in a foreign country and was briefly using a VPN for part of the conversation, but I’m able to message other users who do not have a conversation across multiple synced devices without issue. Mentioning these two just in case.

Deleting message history didn’t resolve the issue for this specific contact.

Filed a new report per request on #1939.

Steps to reproduce

Send a message.

Actual result: Get an error on every message.

Expected result: No errors.

Screenshots

n/a

Device info

Device: iPhone 11 Pro Max

iOS version: 13.3

Signal version: 3.0.6.0

Link to debug log

https://debuglogs.org/84707034d983b3aad72090dd451ed1e6d0787750f25d0be69f64251a5c81456b.zip

Source

joestump

😕1

All 9 comments

This started happening for @joestump when I re-linked my iPad to my account for signal. All messages send and receive on my end without issue. On occasion I’ll see the sent check mark and not the received, but other than that I’m seeing no errors on my end.

EDIT: deleting and relinking my iPad fixed this issue. Wanted to add a solution that worked. This just seems odd though as I saw no errors on my end.

jonstump on 29 Dec 2019

😕3

I've gotten this too. I was able to reproduce it by clearing the data on my (iOS) phone, but not clearing data on the desktop. Clearing data on the desktop afterwards didn't help, nor did re-linking it.

I was only able to get the message to go away by messaging contacts with the error, and then resetting the session if the option is provided.

Log: https://debuglogs.org/6bbfc76548c7a16e45da5d41da68fd9cb83f0664385cdd6278c782efb707dd4a.zip

(See the December one)

billatq on 30 Dec 2019

This issue appears to be closest match to the bug I have to report. The other day I texted my friend, they say they received notification but no message. Here is the debug log from friends' iPhone:

https://debuglogs.org/a0a4beb54ea1e886d3646f321d6c770dcf26231213c77cb2d84e0088de524d03.zip

and the debug log from my iPhone:

https://debuglogs.org/f62ffea16b3a15930082f459666a5e8790912ea86d49aa8b322f9715de71121f.zip

and here is a screenshot of the experience... signal

thnx!

rhodey on 18 Jan 2020

Hi Rhodey!

It’ll be helpful to have the utc “sent” timestamp for that “...would like to hangout” message, so we can cross reference it in the log.

Easiest way is from a desktop device - if you had a linked desktop at the time. On desktop, view the details for that message and copy and paste the timestamp.

On Jan 18, 2020, at 15:02, rhodey notifications@github.com wrote:

This issue appears to be closest match to the bug I have to report. The other day I texted my friend, they say they received notification but no message. Here is the debug log from friends' iPhone:

https://debuglogs.org/a0a4beb54ea1e886d3646f321d6c770dcf26231213c77cb2d84e0088de524d03.zip

and the debug log from my iPhone:

https://debuglogs.org/f62ffea16b3a15930082f459666a5e8790912ea86d49aa8b322f9715de71121f.zip

and here is a screenshot of the experience...

thnx!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

michaelkirk-signal on 19 Jan 2020

Can confirm the issue with ios user to ios user communication. The other user uses Mac and Ipad Pro as linked devices. I'm getting it as Geen beschikbare sessie voor contactpersoon. (dutch, nl) which comes from the ERROR_MESSAGE_NO_SESSION message. Other user was using Signal 3.1.1.1, so will see if it happens with upgraded Signal and relinked devices again. I use Signal 3.2.0.10 on ios (also linked to a Mac).

PieterGit on 19 Jan 2020

Hi Rhodey! It’ll be helpful to have the utc “sent” timestamp for that “...would like to hangout” message, so we can cross reference it in the log. Easiest way is from a desktop device - if you had a linked desktop at the time. On desktop, view the details for that message and copy and paste the timestamp.
…
On Jan 18, 2020, at 15:02, rhodey @.*> wrote: This issue appears to be closest match to the bug I have to report. The other day I texted my friend, they say they received notification but no message. Here is the debug log from friends' iPhone: https://debuglogs.org/a0a4beb54ea1e886d3646f321d6c770dcf26231213c77cb2d84e0088de524d03.zip and the debug log from my iPhone: https://debuglogs.org/f62ffea16b3a15930082f459666a5e8790912ea86d49aa8b322f9715de71121f.zip and here is a screenshot of the experience... thnx! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

sent 1/14/20 10:56 AM - East Cost North America

rhodey on 21 Jan 2020

note: I have no linked devices and I am almost certain my friend does not either, I would think you'd have this somewhere in the debug logs tho...

rhodey on 21 Jan 2020

I don’t think I got that idea?

Get Outlook for iOShttps://aka.ms/o0ukef

From: rhodey notifications@github.com
Sent: Tuesday, January 21, 2020 11:00 AM
To: signalapp/Signal-iOS
Cc: Subscribed
Subject: Re: [signalapp/Signal-iOS] Getting “No available session for contact” error (#4353)

note: I have no linked devices and I am almost certain my friend does not either.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/signalapp/Signal-iOS/issues/4353?email_source=notifications&email_token=AH32IM7OJF7PTFAKQCCX2ITQ64LX7A5CNFSM4KAU3WLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQICII#issuecomment-576749857, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH32IM4PH765J6E3B4ANPWLQ64LX7ANCNFSM4KAU3WLA.