Wire-webapp: Page shows: "Wire is already open in another tab." Even though it isn't

[Don42]

Wire for Web Version: 2017-06-22-12-18-prod Doesn't seem to show on the error screen
Browser Version: 54.0 (32-bit)
Installed Browser Addons: Ghostery, µblock origin (Tested with both 'paused') Firefox Sync is set up
OS: Windows 7 (Not sure were to find a specific version)

What steps will reproduce the problem?

1. Have app.wire.com open and be logged in; Firefox set up to restore session; (Tab is pinned)
2. Close Firefox and reboot the computer (I did a full reboot)
3. Start Firefox

What is the expected result?
Open Firefox should contain a app.wire.com tab ready to login.

What happens instead?
Firefox contains a app.wire.com tab with only the message "Wire is already open in another tab"
And the URL shows https://app.wire.com/auth/#tabs

Please provide any additional information below. Attach a screenshot if
possible.
Reloading the page, even with with Shift+F5 does not solve this problem.
Closing the tab and reopening also doesn't help. Restarting Firefox was also tested.
Opening https://app.wire.com/auth/#login in the same tab only works for less
than a second.
The only way to "fix" this issue was to make Firefox forget the site and then login.
This unfortunately deletes keys and history, which creates a new client.

[maximbaz]

Workaround:

• Go to https://app.wire.com
• Hit Ctrl+Shift+J (Cmd+Opt+J) to open Dev tools in console
• Paste document.cookie = 'app_opened=;expires=Thu, 01 Jan 1970 00:00:01 GMT;Path=/;'
• Hit Enter
• Go again to https://app.wire.com and it will let you in.

[jarvis-owl]

Hej,

same issue here:
OS: Linux Mint 18.1 Serena - Cinnamon | and also with Windows 10
Firefox 54.0(64-bit) with disabled µBlock

@maximbaz Workaround seems to work :+1:

[Don42]

@makingthematrix Confirmed, Workaround works for now. Thanks.
I expect the issue will pop up after the next restart.

[gregor]

Thank you for your reports. We introduced the multiple tabs detection in the last release to prevent decryption errors like #1287. Obivously this has some undesired side effects if the cooke enabling this behavior is not properly cleared. I will look into fixing the behavior for the next release or disable the feature temporarily until we have a permanent fix in place. Please excuse the inconvenience.

[deadalnix]

Workaround works.

[Don42]

Any timeline of when this is going to land in production?

[gregor]

@Don42 No promises, but this is planed for this week. Maybe we manage to get it out as early as tomorrow.

[deadalnix]

It's the second time this is breaking for me :/

[piegamesde]

If have this issue too, the workaround didn't work for me. Deleted the cookie and after every crash of Chromium I get this screen again.