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

Cannot load remote images with tracker protection #598

Closed
technotiger opened this issue Mar 13, 2023 · 5 comments
Closed

Cannot load remote images with tracker protection #598

technotiger opened this issue Mar 13, 2023 · 5 comments

Comments

@technotiger
Copy link

technotiger commented Mar 13, 2023

The error appears for every email containing remote images. The error cross mark is shown in place of all remote images. MacOS x64.

Message "Some images could not be loaded with tracker protection." appears on the top as shown. Pressing the Load button loads the images (without protection).
Screen Shot 2023-03-13 at 6 21 20 PM

Issue first appeared after recent update. I do not remember the previous version on which it worked. Reverting to 5.1.4 and 5.1.3 did not help. If I try to go back further, login no longer works.

Images load fine (with protection) when using ProtonMail in Safari on the same machine.

@vladimiry
Copy link
Owner

vladimiry commented Mar 13, 2023

Confirmed. To fix this, the packaged into the app web client apps stack has to get addition patching. So new app release coming soon. Most likely issue arrived with v5.1.4 app release, due to the updated web client apps stack, but missed patching extending.

@vladimiry
Copy link
Owner

I've got it fixed and running an updated version locally, so a new release is on the way.

The issue generally looks to me as a bug of @ProtonMail as for some reason they don't respect the API_URL const (build-time value defied in src/app/config.ts ) for core/v4/images and core/v4/images/logo API calls. So going to place issue in https://github.com/ProtonMail/WebClients/issues tracker.

@vladimiry
Copy link
Owner

Should be fixed in just released v5.1.6.

@technotiger
Copy link
Author

Issue resolved in v5.1.6. Confirmed. Thank you!

@vladimiry
Copy link
Owner

I patched the web client to resolve the issue, but also placed the issue at the proton side.

@vladimiry vladimiry unpinned this issue Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants