新しいBoxサポートサイトへようこそ。 変更点の詳細はこちらをご確認ください .

Box Drive + Monterey OS

新規投稿

コメント

9件のコメント

  • France

    Hi David, 

    Welcome to the Box Community!

    I understand where you are coming from and I really apologize for all the inconvenience.

    At present, custom Mount Location on macOS 11.5 and 12 in FPE mode is no longer supported due to an architectural limitation in Apple File Provider Extensions.

    We will be releasing a new version of Box Drive which will be built on a completely brand new architecture on macOS with Apple File Provider Extensions (FPE). This new version of Box Drive provides more seamless and secure access for Box Drive on Intel and M1 devices and no longer requires use of kernel extensions.

    As part of this change, Box Drive's Custom Mount Location feature will no longer be supported on Apple macOS devices configured using the FPE mode of Box Drive due to architectural limitations in Apple File Provider Extensions. 

    More information can be found in this announcement: https://support.box.com/hc/en-us/articles/4407542896147-Box-Drive-Custom-Mount-Location-Deprecation-on-macOS 

    We appreciate your understanding and please let us know if you have any questions.

    0
    コメントアクション Permalink
  • David Pillen

    Is there a release date for the new version?

    4
    コメントアクション Permalink
  • Johnson, Jessica M.

    So is this saying that Box Sync will no longer be available for Mac users and that if we continue to use Box Drive, everything will have to be downloaded to our local drives?

    0
    コメントアクション Permalink
  • Avi Shaaya

    whats the status for  latest version( 2.24.208 ) does the version support this change?

    0
    コメントアクション Permalink
  • France

    Hi Everyone, 

    This issue with Custom Mount is currently affecting users that are on the following platforms and configurations, and the current version of Box Drive does not have the fix for this issue as of the moment.

    • macOS 11.5 if using FPE mode

    • macOS 12 (this only runs in FPE mode)

    Custom Mount Location will continue to work fine if users are using the legacy kernel-based Box Drive configuration on macOS 11.x and 10.15. Custom Mount Location will also continue to be supported on Windows. The most common use case for Custom Mount Location is to enable support for absolute path linked files (relative paths will still work).

    We'd like to better understand the use and impact of Custom Mount Location on macOS (as this will help us better explore options to meet your users' needs in the future). Please go ahead and fill out this short survey to allow us to better understand your use cases.

    Thanks for reaching out and let us know how else we can help!

    0
    コメントアクション Permalink
  • ddsi_labeling+developer

    So if I understand correct box drive will not work correctly on macOS 12.1 and the "kernel mode" workaround will not work?

    1
    コメントアクション Permalink
  • Jonathan Chipman

    Has there been an update for this fix?

    0
    コメントアクション Permalink
  • France

    Hi Everyone, 

    Box Drive works on macOS 12 and however Custom Mount Location feature will no longer be supported.

    You can check out this article to learn more on the new user experience and how to use Box Drive on macOS FPE mode: https://support.box.com/hc/en-us/articles/4407737091219-Using-Box-Drive-on-macOS-File-Provider-Extension-FPE-mode 

    Best,

     

    1
    コメントアクション Permalink
  • 4 Studio Designer

    As a work around on macOS12 (Monterey) if you navigate to your "Home" folder and then to the "Library > CloudStorage" folder you will find your Box remote directory location. Simply make an alias of this item on your desktop (or anywhere else you would like it) and you will then be able to access Box from a desktop icon just as you were once able to do in older versions of macOS, just without the fancy Box icon (only a default blank folder icon will appear). Also you can add your Box directory to your Finder window sidebar or toolbar areas with a simple click and drag. Hope this is helpful to everyone!

    0
    コメントアクション Permalink

投稿コメントは受け付けていません。