-
Notifications
You must be signed in to change notification settings - Fork 504
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
Can't see a new user #2249
Comments
@rlevit thanks for the report. I'll see if I can repro and circle back probably not until next week. Sorry for the inconvenience this is causing. |
This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days. |
@mvilanova I redeployed Dispatch from the latest master and now can see all users registered to a non-default org. Thank you for fixing this. |
@mvilanova, oh, sorry, I have to take the previous message back. After the login I switched to Amplify org and went to "Settings->Members" and I saw all the user I didn't see before. But I didn't realized that I still was in the "Default" org. So now looks like the org switcher is not working because no matter how many times I click on the arrows sign next to the desired org it won't switch to it. To actually switch to Amplify org I had to replace "default" with "amplify" in the URL and now can't go back to the "default" org using the org switcher. Sorry about confusion. I can make a screen recording to demonstrate the issue. |
Known issue. Working on a fix. |
Great, thank you. Also, after switching to the Amplify org I couldn't see users registered to that org, meaning the issue persists. |
This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days. |
I haven't forgotten about this one. I should be able to resume work on it soon. |
This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days. |
This issue was closed, because it has been stalled for 5 days with no activity. |
@mvilanova. are you looking for contributors? If so, I'd like to work on this issue |
@vijal-patel sure, go ahead. Thanks! |
@rlevit I'm not able to replicate the missing user issue. Can you provide the exact steps you used?
I see @mvilanova is already working on the organization switch issue #2599 |
This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days. |
This issue was closed, because it has been stalled for 5 days with no activity. |
Describe the bug
In the newly deployed locally Dispatch app, where the
dispatch-local
image was built from Dockerfile pulled today, I created a new organization namedAmplify
with a user ([email protected]) who is an admin of the default org. I logged out and changed URL tohttp://localhost:8000/amplify/auth/register
and registered with a new user[email protected]
. I randocker exec -it dispatch-web-1 bash -c 'dispatch user update --role Owner --organization Amplify [email protected]'
command and gotUser successfully updated
response.When I log in to Dispatch as
[email protected]
and go toMembers
I see my user but don't see the test user. If I switch to Amplify org I don't see any users. If I log in to Amplify org with the test user I don't see that user inMembers
at all. I see the same thing in the API calls - the test user is not showing up regardless which user auth bearer token I use (rlevit or test). With Dispatch running from the image created by theinstall.sh
I was able to see all users in the API and UI.Expected behavior
All users appear and the
Members
section.Screenshots
The text was updated successfully, but these errors were encountered: