"Received from the native core" since most recent Update

Hello @Trminator,

Thank you for message. Our teams are aware aware of a memory usage problem in a recent version of 1Password for Windows. This issue led to problems with instability with the 1Password application, and integration with our browser extension in particular, for some users.

This issue has now been resolved. To fix the issue, please check for updates and ensure you're using the latest version of 1Password for Windows: How to keep 1Password up to date

While testing, if you disabled integration between the browser extension and the app you can re-enable that after updating:
1. Open the 1Password desktop app.
2. Click your account name in the upper left and select "Settings".
3. In the Browser section, turn on "Connect with 1Password in the browser".
4. Open your web browser.
5. Right click on the 1Password icon in your browser's toolbar and select Settings.
6. Under the General section turn on the option "Integrate with 1Password app".
7. Re-launch the 1Password for Windows app.

If you have any further questions or are still seeing some issues, please let us know so we can help look in to this further.

I managed to get around the issue by downgrading my Desktop-App to 8.10.8 (build 81008047). I just tried going back onto the Beta Branch with the newest release being 8.10.9-12, though, and still experience the issue there, that the Chrome Portable Stable 64bit Extension is not able to connect, while the Chrome Stable 64bit Extension works fine. So, sadly, not related to the mentioned memory issue, and still a problem on the latest Version on Beta channel. I'll stick with 8.10.8 for now, until you guys can figure out what broke on 8.10.9 and following. :)

Hello again @Trminator,

I'm glad to hear that you were able to resolve this issue by moving over to the latest stable version of 1Password for Windows and the browser extension.

In the meantime, I'd like to ask you to recreate the issue and provide a couple of pieces of information that may help with the investigation:
* Save a console log for 1Password in your browser
* How to send a 1Password diagnostics report

Attach the diagnostics to an email message addressed to support+forum@1password.com.

With your email please include:
* A link to this thread: https://1password.community/discussion/141142/received-from-the-native-core-since-most-recent-update
* Your forum username: Trminator

You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thanks!

Hey @ag_mike_d , the Support ID is [#NVC-84559-122]

@Trminator - Thanks for letting us know. Your message is with the team and we'll be in touch as soon as possible.

@ag_mike_d
Just for the record: The newest (stable) release (8.10.9) ALSO breaks this way... so, I am now locked to 8.10.8 or older, until this bug gets fixed...

Hello @Trminator - Sorry for the continued issues. I see that the previous support ticket was reopened with your reply. The issue filed with the team continues to be investigated. The team will be in contact with you as soon as possible.

Your patience is appreciated.

ref: dev/core/core#23060

Any news on this?

Hello @Trminator,

Thanks for getting back to us.

After looking back to this issue, it was discussed that we verify where the browser is located on the drive. So in this use case it won't work out of the box when running Chrome portable.

It is possible that the upcoming custom browser verification may help with this. Initially this is only available for 1Password for Mac, and hope to see this in the future for other platforms.

You can read more about it in this thread here!

Hi @ag_mike_d , so, what you're saying is, I'm stuck on this by now nearly a year old version of 1Password, until MAYBE a feature currently only available on MAC gets ported to Windows? All because you're unable to fix what ever broke the access from the Portable Chrome? (It was working fine, on 8.10.8, after all ...??) ... Kind of disappointing, not gonna lie...