Skip to content
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

When adding a second organization the add organization flow does not complete #1183

Open
SimiHunjan opened this issue Nov 15, 2024 · 2 comments
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs

Comments

@SimiHunjan
Copy link
Contributor

Description

This seems to be regression as when adding more than one organization to the app it does not complete the the temporary password step. I had the development organization added previously and was adding this as the second organization to the app.

Steps to reproduce

Add a second organization to the application.

Additional context

No response

Hedera network

other

Version

0.4.1

Operating system

None

@SimiHunjan SimiHunjan added the Bug A error that causes the feature to behave differently than what was expected based on design docs label Nov 15, 2024
@SimiHunjan
Copy link
Contributor Author

When restarting the application (deleting the application and reinstalling) the step to enter the login credentials for the second organization showed up.

@yiliev0
Copy link
Contributor

yiliev0 commented Nov 18, 2024

I attempted to reproduce this issue by first adding the development organization (where I already have an account and completed the setup) and then adding the local organization, which requires completing the entire setup process, including changing the temporary password, creating a mnemonic, and so on. However, I was unable to replicate the issue. Could you please clarify if there are any specific steps or details I might be missing?

2024-11-18.16-01-34.mp4

@Petyo-Lukanov Petyo-Lukanov added this to the v0.4.3 milestone Nov 20, 2024
@RAMTO RAMTO removed this from the v0.4.3 milestone Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs
Projects
None yet
Development

No branches or pull requests

4 participants