Two iCloud Storage Entries for 1Password

LarryMcJ
LarryMcJ
Community Member

I was upgrading my storage in iCloud today and just happened to notice in iCloud | Preferences | Storage on my Mac that I have two 1Password entries in iCloud Storage. One is 474KB and the other is 4.1MB. Is one of these old and not needed? The only option is to delete either of them, no way I can see to look at what each contains.

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @LarryMcJ: Sorry for the confusion! There is actually nothing to worry about. This is normal, since there will be the original data as well as the new copy that was created when you upgraded to iCloudDrive. It's better to be safe than sorry!

    You can find more information about this in our knowledgebase (as well as detailed instructions on how to go about removing the old data safely, if you so wish). I hope this helps! :)

  • LarryMcJ
    LarryMcJ
    Community Member

    Thanks, brenty...I'll just leave it alone. However, I did want to clip the support article to Evernote so tried to do so in Safari and the Evernote Clipper will not function with your support pages. It's working fine everywhere else. Is this something I should post somewhere else?

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @LarryMcJ,

    When you say not function can you elaborate for us please, this thread will be fine to do so :smile:

  • LarryMcJ
    LarryMcJ
    Community Member
    edited March 2015

    Sorry, should have been more specific. If I am on an support page article, such as the one brenty recommended above, if I click on the Evernote Helper icon in Safari absolutely nothing happens. It should open this - http://take.ms/YNxxP - so I can accept the default Evernote clip or change the option. Simply nothing happens at all, though. This works just fine on all other web pages.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @LarryMcJ: Interesting. Yes, thanks for bringing that to our attention. I was able to check this myself, and both my Evernote and Pocket extensions work on (most) other sites, but not with our support site for some reason. This only happens in Safari, however; in Chrome I didn't have any trouble.

    While it may just be a Safari/extension issue, I will bring this up with the team and see if there is anything we can do on our end to remedy it. :)

  • LarryMcJ
    LarryMcJ
    Community Member

    Thanks, brenty...glad you were able to reproduce it. I'm certainly not moving to Chrome to overcome it :-)

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @LarryMcJ: You're very welcome! I just wanted to add some additional information here in case it might prove helpful to you (or others in the future experiencing similar issues.

    It turns out that this is just Safari enforcing the Content Security Policy. The good news is that this is in place to prevent cross-site scripting exploits (loading content belonging to a site other than the one you are visiting). Interestingly, extensions are supposed to be exempt from this, since they are expressly installed and invoked by the user.

    The bad news is that it seems that Safari has other ideas, and does not actually allow an exemption for extensions (see this post from Evernote on the issue)...which explains why these extensions work on our site in Chrome and Firefox, but not Safari.

    We don't want to change the policies on our site, because that could (theoretically) leave it vulnerable to compromise. I hope this helps shed some light on things! :)

  • LarryMcJ
    LarryMcJ
    Community Member

    It's not the end of the world :-) If the content is important enough for me to save in Evernote, I'll simply open the page in Chrome (even if I don't like it). At least it works for this purpose. Thanks so much for your help!!

  • AGAlumB
    AGAlumB
    1Password Alumni

    @LarryMcJ: Any time! I'm sorry I don't have a better solution to offer you, but that will definitely work in a pinch. Cheers! :chuffed:

This discussion has been closed.