After Login I have to refresh the page again

cvu commented

2024-01-24 10:41:26 +01:00

Collaborator

After the Login I am still in the not-login-mode and have to refresh the page. For shure a lot of people do not know this.

cvu added the

bug

label 2024-01-24 10:41:26 +01:00

778a69cd commented

2024-01-24 17:49:54 +01:00

Owner

I observed this and it seems to happen only some of the times. The way I remember it one had to even force-reload the page, which is even more inaccessible (and actually not possible on mobile).

778a69cd added the

upstream

label 2024-01-24 17:50:03 +01:00

summersamara commented

2024-01-30 01:04:45 +01:00

Collaborator

If I logout and login again, everything seems to work. The issue seems to happen when I logout, refresh the page and then try to login, so in a way, the issue occurs on newly loaded/reloaded pages.

I had a look and the issue seems to be in views/User/LoginView.vue line 249 when trying the load the current User Identities via apollo's useLazyQuery (when the issue happen, the execution stops there / no result or promise are returned even tho the request to the server is successful)

anyway, I found the following issue on github that seems to have some answers but I'm not sure yet how to implement them (the discussion seem to be about an issue in React and not vue tho, but the issue seems similar to the one we're having):
https://github.com/apollographql/apollo-client/issues/9354

more specifically, the following comments:

This comment provides a workaround https://github.com/apollographql/apollo-client/issues/9354#issuecomment-1234952933
This comment seems to provide a reason for this issue https://github.com/apollographql/apollo-client/issues/9354#issuecomment-1423166206

If I logout and login again, everything seems to work. The issue seems to happen when I logout, refresh the page and then try to login, so in a way, the issue occurs on newly loaded/reloaded pages. I had a look and the issue seems to be in `views/User/LoginView.vue` line 249 when trying the load the current User Identities via apollo's `useLazyQuery` (when the issue happen, the execution stops there / no result or promise are returned even tho the request to the server is successful) anyway, I found the following issue on github that seems to have some answers but I'm not sure yet how to implement them (the discussion seem to be about an issue in React and not vue tho, but the issue seems similar to the one we're having): https://github.com/apollographql/apollo-client/issues/9354 more specifically, the following comments: 1. This comment provides a workaround https://github.com/apollographql/apollo-client/issues/9354#issuecomment-1234952933 2. This comment seems to provide a reason for this issue https://github.com/apollographql/apollo-client/issues/9354#issuecomment-1423166206

cvu commented

2024-02-05 14:56:17 +01:00

Author

Collaborator

For me its still like this - on Laptop (Ubuntu+Firefox) and Smartphone(Android+Firefox).

778a69cd referenced this issue

2024-02-26 11:47:35 +01:00

Problem logging in as admin user #58

778a69cd referenced this issue from a commit

2024-02-27 22:50:36 +01:00

use useCurrentUserIdentities instead of useLazyCurrentUserIdentities

778a69cd referenced this issue from a commit

2024-02-27 23:22:41 +01:00

use useQuery instead of useLazyQuery in useLazyCurrentUserIdentities

778a69cd commented

2024-03-01 16:06:32 +01:00

Owner

Just managed to reproduce this issue on a vanilla Mobilizon 4.1.0, so it's definetly upstream relevant.

👍 1

778a69cd commented

2024-03-01 16:54:37 +01:00

Owner

Created an issue upstream, as I'm able to reproduce on their flagship instance https://mobilizon.fr

https://framagit.org/framasoft/mobilizon/-/issues/1430

Created an issue upstream, as I'm able to reproduce on their flagship instance https://mobilizon.fr https://framagit.org/framasoft/mobilizon/-/issues/1430

❤️ 1

briefkastenoma commented

2024-03-04 17:37:11 +01:00

Owner

Still problematic on new version 4 (4th of March)

778a69cd commented

2024-04-11 00:38:13 +02:00

Owner

Should be fixed now by adc61a9234

Should be fixed now by adc61a92348a3d7093fbe9bab948af13e8ea752c

778a69cd closed this issue

2024-04-11 00:38:14 +02:00

After Login I have to refresh the page again #44