-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.5.0 shows "nag" screen #204
Comments
Is that only the 1st login? |
Yeah, but it does not happen with 0.4.0 under the same circumstances. |
yeah, not sure what ms have changed on those checks, I will leave it open
for now and see if it can go away somehow.
…On Wed, Aug 7, 2019 at 11:58 AM rojaro ***@***.***> wrote:
Yeah, but it does not happen with 0.4.0 under the same circumstances.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#204?email_source=notifications&email_token=AADJHEGAOA6BCMFMD5G3VC3QDKTD3A5CNFSM4IJ63MIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3YAUQQ#issuecomment-519047746>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADJHEGGSLUQHSXWXIE5DCTQDKTD3ANCNFSM4IJ63MIA>
.
|
0.6.0, too |
If you just wait, does it go away? I have seen it before but normally trigger continues to the app after a few seconds (10 or so) |
I am seeing the same thing, and the screen does not go away automatically, even after waiting more than 60 seconds. It does seem to only happen once, so long as nothing happens to the ~/.config/teams-for-linux/ dir |
Next time when I've to delete the config folder again, I will wait a bit longer to check this issue with 0.6.0 on Ubuntu 18.04.1 HWE Kernel 5.0 BR, Alfred |
I blew away the ~/.config/teams-for-linux directory again and did some more testing/waiting. 12 minutes after relaunching teams, it was still sitting on the screen, waiting for a click on "Get the Windows app / Use the web app instead" |
Hi @whofferbert , @rojaro and @alfsch . Two things:
Alternatively, It might be possible to hide that screen if we get an identifier. I can't really get it as it goes in a few seconds. We then maybe try to add another line in here to "hide" that (not sure if that will work) |
Hey, thanks for the ideas. I registered the link with xdg-open, and that did not fix it. I poked around a bit more, and in the --help output, I noticed the default user agent was "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3835.0 Safari/537.36" (primary difference above is the X11; Linux x86_64 vs Windows NT 10.0; Win64; x64) This seems to have corrected it for me. I blew away the Cache, Service Worker, and Local Storage stuff under ~/.config/teams-for-linux , relaunched, and got no nag screen. Previously, clearing just those dirs would trigger the nag screen again the next time teams was opened |
That might have sneak in as a change when trying to get the screenshare to work again. Can you have a look if screenshare still works with those settings? Thanks! |
I think the sharing will work. anyone happy to do a PR? Changing this userAgent line: to "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3831.6 Safari/537.36" And the https://github.com/IsmaelMartinez/teams-for-linux/blob/develop/app/config/README.md file also... that seems to be out of sink. Thanks in advance! |
@whofferbert , Thanks again for finding the fix and for the PR! You are a star. 0.6.5 should be in the edge channel. That will need a clean config otherwise some conversations might be hidden. |
just pre-released 0.6.6 so people that don't use snap can test it also. |
works with 0.6.6 👍 |
When running 0.5.0 (and 0.5.1) for the first time, the user is presented with this screen after the login:
This does not happen with 0.4.0.
The text was updated successfully, but these errors were encountered: