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

ProtonDrive unavailable #377

Closed
shdwchn10 opened this issue Feb 27, 2021 · 12 comments
Closed

ProtonDrive unavailable #377

shdwchn10 opened this issue Feb 27, 2021 · 12 comments

Comments

@shdwchn10
Copy link

When I open ProtonDrive I get this error:
screenshot

ProtonDrive in Firefox works.
I tried to remove all ElectronMail data (rm -rf ~/.var/app/com.github.vladimiry.ElectronMail) and login again but it didn't help.

Proton Subscription: Visionary
ElectronMail version: v4.10.2 (Flatpak)
OS: Fedora Silverblue 33

@vladimiry
Copy link
Owner

There is not a lot I can do about ProtonDrive since I don't have accounts with enabled access to this service. What at the moment is done regarding ProtonDrive is just packing the respective @ProtonMail web client into the app.

@vladimiry
Copy link
Owner

vladimiry commented Feb 27, 2021

When I open ProtonDrive I get this error:

That doesn't look like an error but a custom warning setup by @ProtonMail saying that your account doens't have the access to the service yet.

@BenMMcLean
Copy link

BenMMcLean commented Mar 1, 2021

I also experience the error, but my account does have access to ProtonDrive through the browser

@vladimiry
Copy link
Owner

vladimiry commented Mar 1, 2021

Marking the issue as a bug then but won't be doing anything to fix it until I my account gets access to the ProtonDrive service.

@vladimiry
Copy link
Owner

vladimiry commented Mar 3, 2021

I did a brief debugging and have noticed that there is no is-paid-user=1 cookie set in the app when the /api/drive/shares API gets requested. The call to this API depending on the outcome triggers the demonstrated warning displaying. The reason of cookie issue is that @electron doesn't work well with the JS-based cookies on the pages loaded on file:// or custom schemes. Not saying yet that this is the issue cause but this is a clear difference in comparison with a regular browser use.

@vladimiry
Copy link
Owner

vladimiry commented Jul 9, 2021

Another possible reason aside from the above-named cookies stuff is that in the browser you signing via @ProtonMail SSO but in the app that SSO thing is not used by design. I've approached @ProtonMail regarding the issue but they were not very helpful so far (the specific "plus" user case was listed but not resolved yet).

@xyz-nobody
Copy link

I have exactly the same problem but with a different error message.

However, if I connect directly without going through electron-mail I have full access to protondrive.

bug

@vladimiry vladimiry pinned this issue Sep 28, 2021
@iam-cult
Copy link

Same issue here, says I need to upgrade, while I already own a visionary account.

@vladimiry
Copy link
Owner

I assumed in #377 (comment) that Drive service is designed to be only available for users who have signed in into the account via the SSO login scenario. @mmso can you or someone on the team confirm or deny this assumption? СС @bartbutler.

@Jvlsc
Copy link

Jvlsc commented Mar 23, 2022

I received a mail confirming Proton Drive is already available in beta for free users (maybe just a soft release at this moment). Could you please check it out again? I would love to have Proton Drive in my desktop.

Cheers.

Edit: it's working fine in web.

@Jvlsc
Copy link

Jvlsc commented Apr 12, 2022

I'm back to confirm that Protondrive is working for me. It seems they have fixed the login process for this service!

Thanks to @vladimiry for all the work he is doing with this app.

Cheers.

@vladimiry
Copy link
Owner

vladimiry commented Apr 12, 2022

@Dvlnst thanks for observing the Protondrive availability in the app and putting the update here. So apparently @ProtonMail has finally fixed the above-mentioned "access scope"-related issue at their backend. Closing the issue as resolved.

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

6 participants