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

Importing from key export file should report success / fail #9445

Closed
jryans opened this issue Apr 12, 2019 · 5 comments
Closed

Importing from key export file should report success / fail #9445

jryans opened this issue Apr 12, 2019 · 5 comments
Labels
A-E2EE O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Design X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@jryans
Copy link
Collaborator

jryans commented Apr 12, 2019

When you import from a key export, it seems to just close the dialog without saying whether it worked or not, which is not very reassuring for such an important workflow.

We should clearly communicate the outcome (success / failure) to the user.

@xloem
Copy link

xloem commented Apr 12, 2019

It would also be great if there were some way to discern this, until such a feature is implemented, like some textual debug output. Key import doesn't appear to be working for me right now.

@jryans jryans changed the title Importing from key export file should report sucess / fail Importing from key export file should report success / fail Apr 15, 2019
@jryans jryans removed the Z-UI/UX label Mar 9, 2021
@ShadowJonathan
Copy link
Contributor

This is still applicable, however, it does tell you if you entered the wrong passphrase.

@andybalaam andybalaam added S-Minor Impairs non-critical functionality or suitable workarounds exist O-Occasional Affects or can be seen by some users regularly or most users rarely and removed P1 labels Apr 26, 2022
@daniellekirkwood
Copy link
Contributor

Are we referencing this screen?

Screenshot 2022-04-27 at 12 33 31

@daniellekirkwood daniellekirkwood added the X-Needs-Info This issue is blocked awaiting information from the reporter label Apr 28, 2022
@t3chguy
Copy link
Member

t3chguy commented Jan 31, 2024

Hi, I'm going to close this issue for now as there is not enough info here for us to be able to action it. Please feel welcome to reopen or ask me to reopen the issue if you update the description with steps/screenshots/video/more details so our developers can have a look at it.

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
@xloem
Copy link

xloem commented Jan 31, 2024

I had basically stopped using element years ago because of issues like these — I couldn’t retain encrypted conversations from use to use, and didn’t find channels to address this. Sorry the connection didn’t form.

If key exchange is working for devs, it’s possible people complaining of issues are using compromised devices. More debug output, and/or clear information on what the correctly functioning flow is, could make that easier to discern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Design X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

9 participants