Can I Now Delete .ws.agile.1Password.settings on Dropbox?

ings
ings
Community Member
edited June 2014 in 1Password 4 for Windows

I run 1Password on IOS, Mac OS, and Windows, sync'd with Dropbox.

I seem to recall a suggestion here that when 1Password 4 finally came out on Windows, users would be able to delete this Dropbox configuration file, as the IOS and Mac OS versions no longer depended on it.

Can I delete it now? Or is my recollection faulty? Thanks.

Dave Ings

Comments

  • svondutch
    svondutch
    1Password Alumni

    In theory, yes you can delete it. But there is no harm in keeping it around. 1Password version 3 for iOS needs it.

  • benfdc
    benfdc
    Community Member
    edited June 2014

    1Password version 3 for iOS needs it.

    ?? Dropbox sync for 1P3/iOS died many months ago. However, your response suggests that 1P3/iOS still has some degree of Dropbox compatibility. Can you please elaborate? Inquiring minds want to know!

  • ings
    ings
    Community Member
    edited June 2014

    So I tried deleting it (I like clean directories) but 1Password4 for Windows thoughtfully (?!) recreates it. So it looks like this file isn't quite yet dead - in fact it seems zombie like! :-)

  • svondutch
    svondutch
    1Password Alumni

    @ings Correct. OPW4 will re-create that file. Because it doesn't do any harm, I'm hesitant to turn that thing off.

  • MikeT
    edited June 2014

    Hi guys,

    1Password 3 for iOS does not support Dropbox sync in any way, the Dropbox API version we were using in 1Password 3 for iOS is permanently dead, and any connections to Dropbox via that outdated API version will be rejected forever.

    However, the file is still being used for 1Password 3 for Mac, 1Password for Windows Phone, and 1Password 1.x for Windows for the Dropbox sync there.

  • benfdc
    benfdc
    Community Member

    Thanks for the clarification, @MikeT.

  • DBrown
    DBrown
    1Password Alumni

    Thanks for catching that error, @MikeT‌! I've deleted my reply.

  • You're welcome!

This discussion has been closed.