1Password Unable to establish connection to App under MacOS 10.15?

ekohnekohn Junior Member

Just wondering if this is supported, as it's not working?


1Password Version: 7.3.1B-4
Extension Version: 1.16.4
OS Version: 10.15B2
Sync Type: Not Provided

Comments

  • kaitlynkaitlyn

    Team Member

    Hey @ekohn! It looks like you have both the 1Password for Mac beta and the 1Password X beta installed according to the version numbers you mentioned, so Desktop App Integration is indeed possible. I haven't tried it out on macOS Catalina yet myself, but I don't believe that'd be an issue. If you wouldn't mind, could you grab your logs for me and post them here? That should give us some more information. We've got a handy guide that explains how to obtain your logs here.

  • ekohnekohn Junior Member

    Hey @Kaitlyn attached is the logs. The guide needs to be updated for MacOS Edge, but I got them anyway.

    14:29:44.473 background.js:31 Initializing 1Password X...
    14:29:44.490 background.js:31 Initializing Desktop App Integration. Attempting to connect to native app. 💌
    14:29:44.496 background.js:31 Finished initializing beta 1Password X 1.16.4 in chrome (20073)
    14:29:44.501 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    14:29:44.593 background.js:31 Preparing hello payload for device sv2hodyxg4u5wfdc6wkgjv2jnm:
    14:29:44.593 background.js:31 (accountUUID, userUUID, server) => (KPVNBASKFBABBJXEQZ35KQLUEE, 36ZMESDTBRGY5HARCB4D3FXYLY, 1password.com)
    14:29:44.595 background.js:31 Native app port disconnected. Error: Specified native messaging host not found.
    14:29:44.597 background.js:1 crypto tests: 103.0068359375ms
    14:29:44.598 background.js:31 Signing payload for account KPVNBASKFBABBJXEQZ35KQLUEE with kid xb42k2kso4kg45qat2rlhwldqe
    14:29:44.600 background.js:31 🌈 Sending message to native app
    14:29:44.600 background.js:31 💥 Failed to send because our port was disconnected. Browser code signature became invalid?
    14:29:44.600 background.js:31 🧠 Initializing filling data from cache.
    14:29:47.097 background.js:31 Attempt #1 to reconnect to the native app
    14:29:47.097 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    14:29:47.170 background.js:31 Preparing hello payload for device sv2hodyxg4u5wfdc6wkgjv2jnm:
    14:29:47.170 background.js:31 (accountUUID, userUUID, server) => (KPVNBASKFBABBJXEQZ35KQLUEE, 36ZMESDTBRGY5HARCB4D3FXYLY, 1password.com)
    14:29:47.171 background.js:31 Native app port disconnected. Error: Specified native messaging host not found.
    14:29:47.171 background.js:31 Signing payload for account KPVNBASKFBABBJXEQZ35KQLUEE with kid xb42k2kso4kg45qat2rlhwldqe
    14:29:47.172 background.js:31 🌈 Sending message to native app
    14:29:47.172 background.js:31 💥 Failed to send because our port was disconnected. Browser code signature became invalid?
    14:29:52.174 background.js:31 Attempt #2 to reconnect to the native app
    14:29:52.175 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    14:29:52.243 background.js:31 Preparing hello payload for device sv2hodyxg4u5wfdc6wkgjv2jnm:
    14:29:52.243 background.js:31 (accountUUID, userUUID, server) => (KPVNBASKFBABBJXEQZ35KQLUEE, 36ZMESDTBRGY5HARCB4D3FXYLY, 1password.com)
    14:29:52.243 background.js:31 Native app port disconnected. Error: Specified native messaging host not found.
    14:29:52.244 background.js:31 Signing payload for account KPVNBASKFBABBJXEQZ35KQLUEE with kid xb42k2kso4kg45qat2rlhwldqe
    14:29:52.249 background.js:31 🌈 Sending message to native app
    14:29:52.249 background.js:31 💥 Failed to send because our port was disconnected. Browser code signature became invalid?
    14:30:02.244 background.js:31 Attempt #3 to reconnect to the native app
    14:30:02.244 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    14:30:02.314 background.js:31 Preparing hello payload for device sv2hodyxg4u5wfdc6wkgjv2jnm:
    14:30:02.314 background.js:31 (accountUUID, userUUID, server) => (KPVNBASKFBABBJXEQZ35KQLUEE, 36ZMESDTBRGY5HARCB4D3FXYLY, 1password.com)
    14:30:02.314 background.js:31 Native app port disconnected. Error: Specified native messaging host not found.
    14:30:02.314 background.js:31 Signing payload for account KPVNBASKFBABBJXEQZ35KQLUEE with kid xb42k2kso4kg45qat2rlhwldqe
    14:30:02.320 background.js:31 🌈 Sending message to native app
    14:30:02.320 background.js:31 💥 Failed to send because our port was disconnected. Browser code signature became invalid?

  • kaitlynkaitlyn

    Team Member

    @ekohn – I didn't realize you were using macOS Edge. I should have asked from the beginning; sorry about that! 1Password for Mac won't be able to verify the code signature of the new Edge for macOS, so that's the only place where Desktop App Integration won't work at the moment. If you were to install the 1Password X beta in Chrome, then you should see it working correctly, though.

  • ekohnekohn Junior Member

    @Kaitlyn no worries. I look forward to the macOS Edge version.

  • brentybrenty

    Team Member

    :) :+1:

  • cryptochromecryptochrome Junior Member

    I am going to hijack this thread as I have the exact same problem, but with Chrome. It appears as if every other 1P update breaks app integration. It is very inconsistent and happens frequently with updates. It doesn't happen with every update, but it did with the current one.

  • kaitlynkaitlyn

    Team Member

    Hey @cryptochrome! Thanks for letting us know you're having trouble after 1Password for Mac updates. I've run into it myself in the past, and a restart of Chrome has solved the issue for me. Would you mind restarting Chrome and seeing if you still see the same "Unable to establish connection" message? I'm curious if that's all it takes to resolve things or if there's something deeper going on.

    If you're still having trouble even after restarting Chrome, I'd like you to post your 1Password X logs here so my team and I can take a look. Here's our guide on how to save those logs. Let me know how it goes.

    ref: x/b5x#1146

  • cryptochromecryptochrome Junior Member

    Hey @kaitlyn - unfortunately the issue is not resolved by restarting Chrome.

    Here are the logs:

    (Note I have removed the (accountUUID, userUUID, server) parts as I don't want them on the internet)

    17:40:25.665 background.js:31 @hangUp.
    17:40:27.368 background.js:31 Initializing Desktop App Integration. Attempting to connect to native app. 💌
    17:40:27.373 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    17:40:27.446 background.js:31 Preparing hello payload for device jci3estunvmqdqalcqlmpqqbom:)
    17:40:27.448 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    17:40:27.452 background.js:31 🌈 Sending <hello> message to native app
    17:40:27.453 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    17:40:29.954 background.js:31 Attempt #1 to reconnect to the native app
    [...things repeat from here...]
    

    Thanks

  • kaitlynkaitlyn

    Team Member

    Thank you, @cryptochrome. What version of Google Chrome are you using?

  • cryptochromecryptochrome Junior Member

    @kaitlyn that would be Version 76.0.3809.36 (Official Build) beta (64-bit) on macOS 10.14

  • cryptochromecryptochrome Junior Member

    Also, I just realized that 1P and 1PX are not syncing again with this release. This was a bug before and now it seems to have returned.

  • awineckiawinecki
    edited June 26

    @kaitlyn I think I'm having the same issue as @cryptochrome.

    My system:

    macOS Mojave 10.14.5
    Google Chrome Version 75.0.3770.100 (Official Build) (64-bit)
    1Password X Beta Chrome Extension - Version 1.16.4
    1Password Desktop - Version 7.3.1

    Any ideas how to make it work? I've tried restarting Chrome, 1P, computer.

    I can't use Touch ID on ma Macbook with 1Password X because of this, and also I've saved some logins with the Chrome extension and they don't seem to have synced over to the desktop app. The 1P app on the iPhone has the new passwords though.

    Here's my log:

    23:09:14.959 background.js:31 [LM] Updated autolock settings: minutes=90, lock on sleep=false
    23:09:14.959 background.js:31 @hangUp.
    23:09:22.191 background.js:31 [LM] Updated autolock settings: minutes=90, lock on sleep=false
    23:09:22.200 background.js:31 Initializing Desktop App Integration. Attempting to connect to native app. 💌
    23:09:22.209 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    23:09:22.318 background.js:31 Preparing hello payload for device afji2ifisj7lbotuc5pp6drs3u:
    23:09:22.319 background.js:31   (accountUUID, userUUID, server) => (EQGA3HQA7BGSPBWLGHJVO7LPHQ, UVJBVTCPLBGIBKVPD3RRTGLQHE, 1password.com)
    23:09:22.321 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    23:09:22.326 background.js:31 Signing payload for account EQGA3HQA7BGSPBWLGHJVO7LPHQ with kid dhaonx3pdrfgdmederuec4wlf4
    23:09:22.329 background.js:31 🌈 Sending <hello> message to native app
    23:09:22.330 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    23:09:24.824 background.js:31 Attempt #1 to reconnect to the native app
    23:09:24.825 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    23:09:24.920 background.js:31 Preparing hello payload for device afji2ifisj7lbotuc5pp6drs3u:
    23:09:24.920 background.js:31   (accountUUID, userUUID, server) => (EQGA3HQA7BGSPBWLGHJVO7LPHQ, UVJBVTCPLBGIBKVPD3RRTGLQHE, 1password.com)
    23:09:24.921 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    23:09:24.922 background.js:31 Signing payload for account EQGA3HQA7BGSPBWLGHJVO7LPHQ with kid dhaonx3pdrfgdmederuec4wlf4
    23:09:24.925 background.js:31 🌈 Sending <hello> message to native app
    23:09:24.925 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    23:09:29.922 background.js:31 Attempt #2 to reconnect to the native app
    23:09:29.922 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    23:09:30.016 background.js:31 Preparing hello payload for device afji2ifisj7lbotuc5pp6drs3u:
    23:09:30.016 background.js:31   (accountUUID, userUUID, server) => (EQGA3HQA7BGSPBWLGHJVO7LPHQ, UVJBVTCPLBGIBKVPD3RRTGLQHE, 1password.com)
    23:09:30.024 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    23:09:30.024 background.js:31 Signing payload for account EQGA3HQA7BGSPBWLGHJVO7LPHQ with kid dhaonx3pdrfgdmederuec4wlf4
    23:09:30.027 background.js:31 🌈 Sending <hello> message to native app
    23:09:30.027 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    23:09:40.026 background.js:31 Attempt #3 to reconnect to the native app
    23:09:40.027 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    23:09:40.127 background.js:31 Preparing hello payload for device afji2ifisj7lbotuc5pp6drs3u:
    23:09:40.127 background.js:31   (accountUUID, userUUID, server) => (EQGA3HQA7BGSPBWLGHJVO7LPHQ, UVJBVTCPLBGIBKVPD3RRTGLQHE, 1password.com)
    23:09:40.135 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    23:09:40.135 background.js:31 Signing payload for account EQGA3HQA7BGSPBWLGHJVO7LPHQ with kid dhaonx3pdrfgdmederuec4wlf4
    23:09:40.140 background.js:31 🌈 Sending <hello> message to native app
    23:09:40.140 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    
  • kaitlynkaitlyn

    Team Member

    Thanks for chiming in, @awinecki. I'm getting in touch with our Mac developers now, and I'll update you here once I have more info. That goes for you as well, @cryptochrome. I appreciate the reports!

  • same issue here on mac os and chrome

    Initializing 1Password X...
    07:20:19.583 background.js:31 Initializing Desktop App Integration. Attempting to connect to native app. 💌
    07:20:19.590 background.js:31 Finished initializing beta 1Password X 1.16.4 in chrome (20073)
    07:20:19.591 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    07:20:19.692 background.js:31 Preparing hello payload for device n2eupv5qe3vmwrwej67gfi2cn4:
    07:20:19.692 background.js:31   (accountUUID, userUUID, server) => (GBONMZKMGNABBMUI46NN3X3YAM, 5KLWIAPVIJDQJEDB3SFDAIVBW4, 1password.com)
    07:20:19.698 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    07:20:19.711 background.js:1 crypto tests: 122.985107421875ms
    07:20:19.711 background.js:31 Signing payload for account GBONMZKMGNABBMUI46NN3X3YAM with kid kzg2a2gnflfdqd66hp3hsy3bce
    07:20:19.713 background.js:31 🧠 Initializing filling data from cache.
    07:20:20.542 background.js:31 🌈 Sending <hello> message to native app
    07:20:20.542 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    07:20:22.200 background.js:31 Attempt #1 to reconnect to the native app
    07:20:22.200 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    07:20:22.291 background.js:31 Preparing hello payload for device n2eupv5qe3vmwrwej67gfi2cn4:
    07:20:22.291 background.js:31   (accountUUID, userUUID, server) => (GBONMZKMGNABBMUI46NN3X3YAM, 5KLWIAPVIJDQJEDB3SFDAIVBW4, 1password.com)
    07:20:22.292 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    07:20:22.293 background.js:31 Signing payload for account GBONMZKMGNABBMUI46NN3X3YAM with kid kzg2a2gnflfdqd66hp3hsy3bce
    07:20:22.293 background.js:31 🌈 Sending <hello> message to native app
    07:20:22.294 background.js:31 💥 Failed to send <hello> because our port was disconnected. Browser code signature became invalid?
    07:20:26.708 background.js:16 PBES2g-HS256(100000): 43.544189453125ms
    
  • kaitlynkaitlyn

    Team Member

    Thanks again for getting this on our radar @cryptochrome, @awinecki, and @raphaelhaohao! We released a stable build of 1Password for Mac today that was a higher version than our latest beta, which temporarily removed the beta build. Since Desktop App Integration requires you to have the beta installed, it disabled the feature. We're publishing a new beta as we speak, so keep an eye out for an update shortly.

  • ceceliacecelia

    Team Member

    Update: 1Password for Mac 7.3.2.BETA-0 has been released. Desktop App Integration should be back online once you update your desktop app. :)

  • cryptochromecryptochrome Junior Member

    I can confirm that with the new beta, app integration is working like a champ. Thanks guys.

  • @cecelia Thank you very much! It's working properly now after upgrading the desktop app.

    🙌

  • It still doesn't work for me (actually it never did so far). I have Chrome 76.0.3809.36 (Beta), 1Password 7.3.2 Beta 0 and 1Password X 1.16.4.

    Here is the log:

    20:12:53.352 background.js:31 Native app port disconnected. Error: Native host has exited.
    20:12:55.867 background.js:31 Attempt #1 to reconnect to the native app
    20:12:55.868 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    20:12:56.251 background.js:31 Preparing hello payload for device xxx:
    20:12:56.252 background.js:31   (accountUUID, userUUID, server) => (XXX undefined, 1password.eu)
    21:28:12.384 background.js:31 Native app port disconnected. Error: Native host has exited.
    21:28:17.422 background.js:31 Attempt #2 to reconnect to the native app
    21:28:17.424 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    21:28:17.870 background.js:31 Preparing hello payload for device xxx:
    21:28:17.870 background.js:31   (accountUUID, userUUID, server) => (XXX, undefined, 1password.eu)
    16:54:03.411 background.js:31 Native app port disconnected. Error: Native host has exited.
    16:54:13.441 background.js:31 Attempt #3 to reconnect to the native app
    16:54:13.442 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    16:54:13.608 background.js:31 Preparing hello payload for device xxx:
    16:54:13.608 background.js:31   (accountUUID, userUUID, server) => (XXX, undefined, 1password.eu)
    16:54:13.613 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    
  • It still doesn't work for me. I have Chrome 76.0.3809.36 (Beta), 1Password 7.3.2 Beta 0 and 1Password X 1.16.4.

    Here is the log:

    20:12:53.352 background.js:31 Native app port disconnected. Error: Native host has exited.
    20:12:55.867 background.js:31 Attempt #1 to reconnect to the native app
    20:12:55.868 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    20:12:56.251 background.js:31 Preparing hello payload for device xxx:
    20:12:56.252 background.js:31   (accountUUID, userUUID, server) => (XXX undefined, 1password.eu)
    21:28:12.384 background.js:31 Native app port disconnected. Error: Native host has exited.
    21:28:17.422 background.js:31 Attempt #2 to reconnect to the native app
    21:28:17.424 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    21:28:17.870 background.js:31 Preparing hello payload for device xxx:
    21:28:17.870 background.js:31   (accountUUID, userUUID, server) => (XXX, undefined, 1password.eu)
    16:54:03.411 background.js:31 Native app port disconnected. Error: Native host has exited.
    16:54:13.441 background.js:31 Attempt #3 to reconnect to the native app
    16:54:13.442 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    16:54:13.608 background.js:31 Preparing hello payload for device xxx:
    16:54:13.608 background.js:31   (accountUUID, userUUID, server) => (XXX, undefined, 1password.eu)
    16:54:13.613 background.js:31 Native app port disconnected. Error: Access to the specified native messaging host is forbidden.
    
  • kaitlynkaitlyn

    Team Member

    @cryptochrome @awinecki – I'm glad to hear that! Thanks for keeping us posted. :)

  • kaitlynkaitlyn

    Team Member

    Hey @revanmj! The timing on the log you posted is throwing me off. It seems to start at 20:12:53, then go up to 21:28:17, then back down to 16:54:13. Would you mind restarting your computer and seeing if that resolves things? If it doesn't, go ahead and post your logs again and I'll take a look.

  • Still the same - after I open 1Password X settings, login page automatically opens, but once I log in nothing happens and desktop integration still does not work.

    20:28:57.670 background.js:31 Initializing 1Password X...
    20:28:57.752 background.js:31 Initializing Desktop App Integration. Attempting to connect to native app. 💌
    20:28:57.797 background.js:31 Finished initializing beta 1Password X 1.16.4 in chrome (20073)
    20:28:57.803 background.js:31 Connecting to native app 2bua8c4s2c.com.agilebits.1password
    20:28:58.126 background.js:31 Preparing hello payload for device xxx:
    20:28:58.126 background.js:31   (accountUUID, userUUID, server) => (XXX, undefined, 1password.eu)
    20:28:58.139 background.js:1 crypto tests: 363.887939453125ms
    20:28:58.142 background.js:31 Uncaught (in promise) Error: Missing local signing key pair for account XXX. 1Password X must be unlocked once before being able to connect to the 1Password app.
        at yt (background.js:31)
        at async dt.sendHello (background.js:31)
    20:28:58.144 background.js:31 🧠 Initializing filling data from cache.
    20:29:06.166 _generated_background_page.html:1 Unchecked runtime.lastError: The message port closed before a response was received.
    20:29:20.816 background.js:16 PBES2g-HS256(100000): 256.934814453125ms
    20:29:21.525 background.js:31 [LM] Started (minutes=3, lock on sleep=true).
    20:30:21.218 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    (...)
    20:30:21.218 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    20:29:23.435 background.js:1 [action/Session#verify] ClientError: Please authenticate with MFA
        at new t (chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:5996)
        at chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:301174
    (anonymous) @ background.js:1
    20:29:23.436 background.js:1 [action/auth#signInWithMpAndSk] ClientError: Please authenticate with MFA
        at new t (chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:5996)
        at chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:301174
    (anonymous) @ background.js:1
    20:29:23.436 background.js:1 [action/auth#signIn] ClientError: Please authenticate with MFA
        at new t (chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:5996)
        at chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:1:301174
    (anonymous) @ background.js:1
    20:29:23.437 background.js:31 🌈 Sending <requestDsecretHmac> message to native app
    20:29:28.441 background.js:31 Sync error 109
    Ge.handleSyncError @ background.js:31
    20:29:28.444 background.js:31 Ensuring device keys are available for 1 accounts now that we are unlocked.
    20:29:28.457 background.js:31 Generating new DeviceKeys for XXX and uploading the public keys.
    20:29:29.984 background.js:31 Uncaught (in promise) Error: Attempted to upload device key for falsey client
        at Ge.uploadDeviceKey (background.js:31)
        at Ge.createDeviceKeysIfNeeded (background.js:31)
        at async Ge.setupDeviceKeys (background.js:31)
        at async Promise.all (index 0)
        at async chrome-extension:/khgocmkkpikpnmmkgmdnfckapcdkgfaf/background/background.js:31
    20:29:50.380 _generated_background_page.html:1 Unchecked runtime.lastError: The message port closed before a response was received.
    
    
  • kaitlynkaitlyn

    Team Member

    @revanmj – Thanks so much. It looks like we're making some progress since this log contains some new errors. I'd like to have you try the following:

    1. With 1Password 7 open, click Help in the macOS menu bar.
    2. Hover over Troubleshooting, and select Reset 1Password X Device Keys
    3. Restart Chrome
    4. Unlock 1Password X
    5. Manually lock 1Password X
    6. Unlock 1Password X again

    If Desktop App Integration still isn't behaving for you, I'd like to move our conversation over to email so I can grab some more reports from you and get this on my team's radar. Just let me know how this goes, and we'll go from there!

  • Unfortunately it still didn't work :( Should I sent an email to a generic support one?

  • brentybrenty

    Team Member

    @revanmj: If you did it already, that's totally fine. We'll get it. But if you send it to [email protected] that will end up in the right inbox faster. :)

  • Just sent it to the email you provided :)

  • brentybrenty

    Team Member

    Thanks! We'll take a look at continue the conversation there. :)

    ref: ZAF-65464-199

Leave a Comment

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