"Layout is Ambiguous" / The purple windows



  • Can still reproduce when I try to Quick Look 1Password documents

  • ag_kevinag_kevin Junior Member

    Team Member

    Hi @gboudreau ,

    Is it all quicklook documents or just a specific type? (e.g. images, PDF, word doc, etc.)


  • Getting this message as well on the latest beta

  • ag_anaag_ana

    Team Member


    Do you get this message all the time or just when you try to quicklook 1Password documents?

  • All the time!

  • ag_anaag_ana

    Team Member

    Thank you for the confirmation :+1: We will continue looking into this.

  • MaForischMaForisch
    edited February 24

    AgileBits Update: Please don't do this. Details on why are outlined in this post. - Thanks.


    TL;DR: Skip to Solution below
    I see this on:
    1Password 7, Version 7.4.4.BETA-0 (70404000) 1Password Beta
    on mac os 10.14.6 on the main 1password window.

    I thought that there may be a way to fix this via the command-line along the lines of this post for Apple Photos

    There the command mentioned there is:
    defaults delete com.apple.Photos NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints

    The help window (ie the ? top right) says something similar
    The domains where this default is set are: NSRegistrationDomain (volatile) defaults delete «domain» NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints

    Dumping all defaults from my user context to a with
    defaults read >alldefaults.out.txt

    shows only one case where "NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints" shows up
    for com.agilebits.onepassword7-updater

    So: Experimenting, quit one password completely, I execute
    defaults delete com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
    defaults read com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
    and a dump defaults read >alldefaults.out.txt confirm the key is gone,
    however not even rebooting it avoids the issue.

    After some head-scratching, i conclude it is set as a debug flag in the app code at runtime in the (volatile==in memory NSRegistrationDomain)
    Further googling reveals this stackoverflow answer:

    1. quit 1Password completely,
    2. execute from a terminal:
    defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NO
    4. Start 1Password
    5. Problem solved.

    From what I understand this sets the flag GLOBALLY for ALL programs, so perhaps not the solution for developers, bc this will suppress it for all users and all programs.

    Better solution perhaps to set it at the app level by using:
    defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NO
    However this might mean it crops up on sub modules, like the Updater?
    Depending on a users tastes the global setting may be preferable.

    Best regards,

    Further experimentation reveals that both
    defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool false
    defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool false
    work just as well, & set the type to the proper boolean value & the help does in the top right does change once the default value is set on the app level.
    defaults read com.agilebits.onepassword7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
    defaults read -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
    So I learned something about the mac today.
    one more item to track this down to the actual code:
    Clicking on the purple frame yields the following entries in Console.app

    The first with the sidebar expanded

    default 22:25:36.630932 +0100 1Password 7 Clicked on visualized constraint: (
    "= 200 (active)> (Actual Distance - pixels):400"

    The second with the sidebar collapsed

    default 22:25:56.322669 +0100 1Password 7 Clicked on visualized constraint: (
    " (Actual Distance - pixels):156"

  • BenBen AWS Team

    Team Member


    We would really prefer people not do that, as then we won't get valuable feedback about UI issues. The reason we publish beta builds is so we can get that kind of feedback. Without that feedback there isn't much incentive to provide betas.


  • I just got this issue

    From the about screen:
    1Password 7
    Version 7.4.4.BETA-0 (70404000)

    1Password Beta

    I have the same issue when I select help from the menu bar.

  • skarchmitskarchmit
    edited March 1

    Although I'm trying to get steps to reproduce it, but so far cannot.
    Here's a better look at the purple window:

  • I found how to reproduce it.
    Open up the help menu and start typing something you are searching for. (1 Character is enough). Then backspace all the way. It will immediately pop up.

  • rudyrudy

    Team Member
    edited March 2


    Thanks for reporting this issue. That one is unfortunately not one that we'll be able to directly solve as that is an issue with Apple's help menu search field.

  • I've got the purple border of doom.
    osx 10.15.4
    1Password 7
    Version 7.6.BETA-0 (70600000)
    1Password Beta
    I'm in safari, using cmd-\ to fill a dialog
    I've gotten it a bunch of times this morning

  • ag_tommyag_tommy

    Team Member


    Hopefully, the developers can get this one fixed up. Thanks for the report.

  • vidgizmovidgizmo Junior Member

    I am getting this now as well with:

    • macOS 10.15.5
    • 1Password 7 Version 7.6.BETA-3 (70600003)

    Any suggestions?

  • BenBen AWS Team

    Team Member

    Hi @vidgizmo

    No suggestions; the "purple windows" are intentional. They're there to help developers identify UI issues. They will only show in beta builds, not stable builds. What part of 1Password are you seeing this particular window in? I.e. What are you trying to do when you see the window? I'll let our development team know to make sure they're aware. Thanks.


  • vidgizmovidgizmo Junior Member

    @Ben I am not doing anything. Just have 1Password running. If I quit and restart 1Password it just pops up. Frequently empty, like this:

    Should I capture and share logs?

  • ag_anaag_ana

    Team Member


    Can you please try quitting 1Password completely (right-click on 1Password mini in the menu bar at the top right of your screen > Quit 1Password Completely), and then relaunch 1Password? Do you see the same behavior?

  • Why have you hidden all the replies on the forum regarding this topic.

  • BenBen AWS Team

    Team Member


    I don't follow. We haven't hidden the replies...


  • In Chrome, the page is without any comments and when loading the direct comment link, I get a blank page. Works in Brave.

  • So yeah, I'm having this problem too. I cannot uncheck "beta" and the fact that I'm seeing developer debugging tools does not instill confidence in terms of security. In general, developer debugging tools equate to verbose logging, which I would not want in a password manager.

  • rudyrudy

    Team Member


    To switch to the release version you will need to install from https://1password.com/downloads

    as for chrome not showing comments, content blocker?

  • I'm seeing this as well on Version 7.7.BETA-9 (70700009) on macOS 10.15.6.

  • ag_anaag_ana

    Team Member


    In what part of the app are you seeing this?

  • It’s at the top behind the main 1Password window. Mission Control allows me to foreground the purple windows but I can’t close/dismiss with cmd+w.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file