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

Shared google drive folders not shown #138

Open
2 tasks done
s73fan opened this issue Dec 23, 2021 · 2 comments
Open
2 tasks done

Shared google drive folders not shown #138

s73fan opened this issue Dec 23, 2021 · 2 comments
Labels
state:has-workaround There is a known workaround for the described problem storage:google-drive type:feature-request New feature or request

Comments

@s73fan
Copy link

s73fan commented Dec 23, 2021

Please agree to the following

Summary

(subscribed) shared folder in google drive are not shown when browsing to add a new or existing containers

What software is involved?

  • Operating System: iOS 15.2
  • Cryptomator: 2.0.3
  • Google Drive iOS: 4.2021.48202

Volume Type

No response

Steps to Reproduce

  1. open cryptomator
  2. add a new or existing container in a google drive
  3. Try to open a (subscribed) shared google drive folder … THIS FOLDERS ARE NOT SHOWN

Expected Behavior

Subscribed shared folders in google drive should show up as normale folders

Actual Behavior

Subscribed shared folder in google drive are not visible within cryptomator

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@tobihagemann tobihagemann transferred this issue from cryptomator/cryptomator Dec 23, 2021
@tobihagemann
Copy link
Member

Does this workaround help? cryptomator/cryptomator-ios#136 (comment)

@s73fan
Copy link
Author

s73fan commented Jan 6, 2022

Does this workaround help? cryptomator/cryptomator-ios#136 (comment)

Yes it does ;-) ...

BTW: You do not need to use the keyboard shortcut to "move" the folder. You can also use the "right-click" menue in the google drive webinterface.

BTW: The notation "move" is a little bit miss leading. In fact it will create an shortcut. This was the reason why I did not try this way before.

Greeting from Hamburg ;-)

@tobihagemann tobihagemann added the state:has-workaround There is a known workaround for the described problem label Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:has-workaround There is a known workaround for the described problem storage:google-drive type:feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants