Android: Not getting Two factor login prompt from app

Created on 29 Dec 2018  Â·  17Comments  Â·  Source: nextcloud/android

Actual behaviour

  • I try to login to Nextcloud and choose notification for my TFA method. I dont get any notification on phone so I have to open up the app, go to notifications, then approve

    Expected behaviour

  • It should present a push notification.

    Steps to reproduce

  1. Enable TFA by notification
  2. Log out of your account on the computer and add the app on a phone
  3. Try to log back in

Environment data

Android version: 7.0.1

Device model: LG Stylo 3

Stock or customized system: Stock

Nextcloud app version: 3.4.1

Nextcloud server version: 15.0.0

bug needs infdiscussion stale

Most helpful comment

I only have my tablet and my phone, so the 2FA notification goes to the tablet, not the phone. I'm gonna look for some other devices in my house when I get home to get a better sample size.

@tobiasKaminsky Thanks for the distinction between the two. I guess the regular notifications work fine on the phone, just not the push notifications. Both types work fine on my tablet.

@AndyScherzinger I understand that there are just notifications, however I'm going to keep referring to them as "push" and "regular" referring to notifications either generated in the app or generated from the nextcloud server pushed to the app. Since technically they are two different "types" of notifications

All 17 comments

GitMate.io thinks possibly related issues are https://github.com/nextcloud/android/issues/1738 (Not Able To Login In Android App), https://github.com/nextcloud/android/issues/822 ([Feature request] get login data from qrCode), https://github.com/nextcloud/android/issues/2939 (Login failed on the app ), https://github.com/nextcloud/android/issues/2552 (App closes upon login), and https://github.com/nextcloud/android/issues/243 (Two factor verification could not login).

cc @tobiasKaminsky afaik a push notification should be send (is 3.4.1 signed properly?)

What he is saying is there are no buttons in the notification itself :)

On Sat, 29 Dec 2018, 18:40 Andy Scherzinger <[email protected] wrote:

cc @tobiasKaminsky https://github.com/tobiasKaminsky afaik a push
notification should be send (is 3.4.1 signed properly?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/3413#issuecomment-450508465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsuoRowFFYcqghJDb0ciWoZryGlLYks5u96kogaJpZM4ZknSH
.

@mario from what I understood there is no incoming push notification at all!

No, I'm saying I'm not getting a push notification in my top bar. If I go into the app and then to notifications I can see it and the buttons are there ;)

Just noticed, I'm getting the notification fine on my tablet just fine. Same app version and same android version. Notifs are not blocked on my phone and I have nextcloud set to ignore battery optimizations so it shouldn't be closing. Anyone have any ideas? I'm stumped.

When opening notifications within our app, do you see a warning stating that there is a problem with push?

Nope, nothing. Interestingly, when i put a usb stick in my phone, the
app sends a push stating a new media folder was detected just fine. The
2FA dont get pushed though.

push stating a new media folder was detected just fine

This is not a push notification, but a regular notification.

A push notification is something that is triggered by server and send to the device via googles cloud messaging service.

Is it? It gets pushed to my tablet just fine, just not my phone. When I get
home I'll make a video to show the issue, since I think the distinction
between "push" and "regular" notifications needs to be made.

On Jan 8, 2019 10:58 AM, "Tobias Kaminsky" notifications@github.com wrote:

push stating a new media folder was detected just fine

This is not a push notification, but a regular notification.

A push notification is something that is triggered by server and send to
the device via googles cloud messaging service.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/3413#issuecomment-452350617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP8_o0HWyvjxUFPzQ6aSHX-E-3kw_c_qks5vBMAogaJpZM4ZknSH
.

@nextcloud/server-triage does the push notification get send to just one device or several for a 2FA request?

Side note:
Notifications are just that, notifications. There is not distinction between them within Android, same for any other app on the Android platform.

It gets send to all registered devices as far as I know.

I only have my tablet and my phone, so the 2FA notification goes to the tablet, not the phone. I'm gonna look for some other devices in my house when I get home to get a better sample size.

@tobiasKaminsky Thanks for the distinction between the two. I guess the regular notifications work fine on the phone, just not the push notifications. Both types work fine on my tablet.

@AndyScherzinger I understand that there are just notifications, however I'm going to keep referring to them as "push" and "regular" referring to notifications either generated in the app or generated from the nextcloud server pushed to the app. Since technically they are two different "types" of notifications

I have (had?) the same issue. When I looked at the devices registered for notifications, some were missing:

select uid, token, deviceidentifier, apptype from oc_notifications_pushtokens;

I went to Android's Settings -> Apps & notifications -> Nextcloud, clicked Force stop, selected Storage, and then cleared cache and storage. After restarting Nextcloud, it registered for push notifications again.

What's interesting is that the wifey's phone (Nextcloud and Talk apps) disappeared from the table shortly after I got all 4 of our devices working. It could be a coincidence, but her battery had died just before I noticed it was no longer registered. Is there any scenario such as multiple failed push notifications that causes the server to unregister a device?

@ryan77627 Did you get your notifications working? If not, does the fix I described above (clearing the app cache and storage) resolve it for you?

@tobiasKaminsky / @AndyScherzinger Do either of you know whether the server will unregister a device under any scenario? I suppose the client could be unregistering itself, but that seems less likely.

Sorry, I'll try later today, I ended up turning it off. I think it worked
every since I bought a new phone, but I'll verify and try your fix if it
doesn't work.

On Sat, Apr 20, 2019, 11:03 AM Chris Wells notifications@github.com wrote:

@ryan77627 https://github.com/ryan77627 Did you get your notifications
working? If not, does the fix I described above (clearing the app cache and
storage) resolve it for you?

@tobiasKaminsky https://github.com/tobiasKaminsky / @AndyScherzinger
https://github.com/AndyScherzinger Do either of you know whether the
server will unregister a device under any scenario? I suppose the client
could be unregistering itself, but that seems less likely.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/3413#issuecomment-485134229,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7T7IZYBBYIN5ADR4FRA6DPRMWFTANCNFSM4GMSOSDQ
.

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

Was this page helpful?
0 / 5 - 0 ratings