Unable to authenticate with error - "Network unavailable. Try again later." #49

New issue

Closed

opened 2019-07-03 20:54:30 +00:00 by thrrgilag · 6 comments

thrrgilag commented

2019-07-03 20:54:30 +00:00

(Migrated from gitlab.com)

New user is unable to complete the authentication process after installing. Authentication with pnut.io is good, but an error is produced on the callback.

It's BB Classic, OS version 10.3.3.3216, software version 10.3.3.2137.
After reinstall still the same: I can input my pnut login and password push the login button and since then I get only "Network unavailable. Try again later."

https://beta.pnut.io/@logout/posts/629799

New user is unable to complete the authentication process after installing. Authentication with pnut.io is good, but an error is produced on the callback. > It's BB Classic, OS version 10.3.3.3216, software version 10.3.3.2137. After reinstall still the same: I can input my pnut login and password push the login button and since then I get only "Network unavailable. Try again later." https://beta.pnut.io/@logout/posts/629799

thrrgilag commented

2019-07-03 20:58:59 +00:00

(Migrated from gitlab.com)

changed the description

By Morgan McMillian on 2019-07-03T20:58:59 (imported from GitLab project)

changed the description *By Morgan McMillian on 2019-07-03T20:58:59 (imported from GitLab project)*

thrrgilag commented

2019-07-03 21:06:30 +00:00

(Migrated from gitlab.com)

This happens on my 10.3.3.2129 and not on my 10.3.3.1463.

After attempting to log in when Goober BB10 is not authorized at all on pnut.io/account/security, the first attempt it will give me the mentioned screen. This does authorize it as far as Pnut is concerned, but Goober doesn't manage to pick up the access token.

After attempting to log in again, it will work.

I also managed to get it to show me a screen saying "Account linked, go ahead back to the app and check the status!" but that was toggling login and killing tokens haphazardly.

By 33MHz on 2019-07-03T21:06:30 (imported from GitLab project)

This happens on my 10.3.3.2129 and *not* on my 10.3.3.1463. After attempting to log in when Goober BB10 is not authorized at all on pnut.io/account/security, the first attempt it will give me the mentioned screen. This does authorize it as far as Pnut is concerned, but Goober doesn't manage to pick up the access token. After attempting to log in again, it will work. I also managed to get it to show me a screen saying "Account linked, go ahead back to the app and check the status!" but that was toggling login and killing tokens haphazardly. *By 33MHz on 2019-07-03T21:06:30 (imported from GitLab project)*

thrrgilag commented

2019-08-03 23:42:26 +00:00

(Migrated from gitlab.com)

assigned to @thrrgilag

By Morgan McMillian on 2019-08-03T23:42:26 (imported from GitLab project)

assigned to @thrrgilag *By Morgan McMillian on 2019-08-03T23:42:26 (imported from GitLab project)*

thrrgilag commented

2019-08-04 00:39:29 +00:00

(Migrated from gitlab.com)

mentioned in commit aba4a2bdea

By Morgan McMillian on 2019-08-04T00:39:29 (imported from GitLab project)

mentioned in commit aba4a2bdea6383d2d265a97f3f3b96585f10d998 *By Morgan McMillian on 2019-08-04T00:39:29 (imported from GitLab project)*