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

Sharing a URL via the sharesheet results in an encryption error since the rust upgrade #7621

Closed
JMoVS opened this issue Jul 12, 2023 · 7 comments
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@JMoVS
Copy link

JMoVS commented Jul 12, 2023

Steps to reproduce

  1. Go to your phone's browser
  2. Share a link via the sharesheet to Element
  3. Then open element and observe an encryption error

Outcome

What did you expect?

No encryption error

What happened instead?

one message stating an encryption error and one that is the real message

Your phone model

No response

Operating system version

iOS 16.5.1a

Application version

No response

Homeserver

No response

Will you send logs?

Yes

@JMoVS JMoVS added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jul 12, 2023
@pixlwave
Copy link
Member

Duplicate of #7499.

@JMoVS
Copy link
Author

JMoVS commented Jul 12, 2023

@pixlwave doesn't seem to be the same as the recipient can decrypt the message

@pixlwave
Copy link
Member

Sadly I believe its all related as the Rust crytpo isn't multi-process safe. We're disabling all extensions that write to the crypto db in #7618.

@JMoVS
Copy link
Author

JMoVS commented Jul 12, 2023

ok, thx

@jacotec
Copy link

jacotec commented Jul 14, 2023

Sadly I believe its all related as the Rust crytpo isn't multi-process safe. We're disabling all extensions that write to the crypto db in #7618.

@pixlwave I believe a better way would be to move back to the old crypto unless Rust is fixed instead of removing elementary features which are part of Element since years (and any other messaging app).

How should we explain to our users that we've chosen the only platform where you can' share from other apps after we hardly worked to get people away from walled garden mainstream?

@pixlwave
Copy link
Member

@jacotec I would suggest taking this to https://github.com/vector-im/element-meta/discussions there's not much I can personally do about the decision.

@jacotec
Copy link

jacotec commented Jul 17, 2023

@pixlwave Is there already a discussion, or should I open a new one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

3 participants