Protect what matters – even after you're gone. Make a plan for your digital legacy today.
windows
3106 Topics1Password 8.11.18: Japanese mistranslation persists
I updated to 1Password for Windows 8.11.18 (81118036), but the Japanese mistranslation that has been present since the previous beta build is still there. The term “助け” is a mistranslation; it should be “ヘルプ” (“Help”). If anyone from the team is reading this, I’d appreciate it if you could forward this thread internally so the translation can be corrected. 1Password for Windows 8.11.18 (81118036) Windows 11 25H2 26200.7171Solved55Views1like4CommentsSupport for Imput's Helium Browser
Hiya! I'm an avid 1Password user and I utilize every possible corner of it. BUT there's a certain issue that I'm facing when I'm using it with unsupported browsers. Mainly, Helium Browser (https://github.com/imputnet/helium) which includes unbiased privacy at no compromise to webpage functionality isn't supported. This is an issue because there's no other browser I'd use. The problems that arise are apparent on all platforms, like: Manual addition in the 1Password app on macOS (which, lately, seems to spaz out when using it with the extension) Inability to use with the system app on Windows which inconveniences users by making them log into their vault twice (which, if I guarantee, many have a complex password for and can't bore themselves typing it out multiple times per session) Broken behaviour on Linux, where even with the custom browser config it still can't unlock the vault if it's unlocked on the system. No, I wasn't running the Flatpak version. IMHO 1Password is better than the competition in terms of UX, but seeing my daily driver struggle with that with no way to fix without resorting to this is awful.9Views0likes0CommentsSupport for Zen browser
Hi! There's this new browser called "Zen browser" It's based on Firefox but the 1password extension doesn't work with the desktop app 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not ProvidedSolved16KViews56likes180CommentsIssues with 1Password on iOS and Windows
New features like unlock with device (iOS, Windows) fail almost all the time (it's not actually unlocking with the device) on Windows it's not possible to start 1Password silent in the background, I needed to implement it myself (simple feature but it seems hard to implement) Just discovered that 1Password supports filters for focuses on iOS but guess: it seems just half implemented and does not show all of my collections and is therefore useless then about collections: I still don't get why collections as a feature is not implemented consequently over all available integrations. in the browsers it's still missing, and you need to fiddle around with single vaults being selected or not usability is sometimes annoying in the browser when the extension is trying to fill in stuff, but you don't want to, even closing the suggestions makes it pop-up in every new field again > not very nice on a small iOS display58Views0likes3CommentsFirst login workflow issue
When setting up 1Password on Windows 11, using 1password.eu domain, it is forwarding to 1password.com for login. When I click on Sign in on 1password.com app opens this page https://start.1password.com/native/signin When I switch 1password.eu at the bottom, page is turning to normal web login page and when I scan that code from my mobile, it opens web vault, nothing happens on Windows app25Views0likes3Commentscrypto.randomUUID is not a function S @ inject-content-scripts.js:5
FYI: I bumped into an error associated with 1Password Beta extension 8.10.56.22 when I was inspecting a site for an unrelated reason. This is not impacting me, just thought you might like to know. Site is http://atecconnectors.com/atec/index.cfm Chrome Dev console says "inject-content-scripts.js:5 Failed to fetch chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/inline/injected.js, Import failed 3 times. Final error: crypto.randomUUID is not a function S @ inject-content-scripts.js:5" The DevTools AI Assistant added this, which I didn't read but looks interesting: "Explanation Okay, let's break down why you're getting the "Failed to fetch ... Import failed 3 times. Final error: crypto.randomUUID is not a function" error and how to fix it. Understanding the Error The error message tells us a few critical things: Failed to Fetch: The browser is trying to load a JavaScript file from a Chrome extension ( chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/inline/injected.js). Import Failed 3 Times: The browser attempted to load the file three times and failed each time. This suggests the issue is not a temporary network hiccup but something fundamental. crypto.randomUUID is not a function: This is the root cause of the failure. The crypto.randomUUID() method is a relatively new web standard (part of the Web Crypto API) that is used to generate cryptographically secure UUIDs. The browser (or, more likely, the context where this code is running) doesn't support it. Where the Problem Likely Lies The problem is most likely in the injected.js file, as the error is complaining about something inside this extension file. Although the error is shown while your web app is working, the problem is not with your app code itself, but rather, the extension injecting this injected.js file. Older Extension Code: The extension is injecting a file that uses crypto.randomUUID(). If the extension was built targeting an older version of Chrome or a different browser that didn't support crypto.randomUUID(), this method may have been added later or not added by the extension authors. Old browser version: An old browser version may not support crypto.randomUUID. Why Your Web App Code is Involved (Indirectly) Your web app's code triggers the extension's injection mechanism. Your code doesn't directly use crypto.randomUUID(). Dissecting the Given Code (and How it Relates) Let's look at the code snippet you provided and see how it contributes to triggering the error, even if it's not causing it: Code (l),i.filter(p).forEach(s=>{let u=b();e.addEventListener("DOMContentLoaded",()=>{l(s).then(u.resolve)},{once:!0}),a=[...a,u.promise]})):(`${n}`,a=[...c,...i].filter(p).map(l)),Promise.all(a)},y=()=>{let e=chrome.runtime.getURL(""),t=new URL(e),r=t.protocol,o=t.host;return`${r}//${o}`},m=(e,t)=>{chrome.runtime.sendMessage({name:"report-error",data:{name:"InjectContentScript",message:e,severity:"error",stack:t}})},S=(e,t)=>{if(!h(e)){console.error(t),m(t);return}let r=`${t}, ${e.message}`;console.error(r),m(r,e.stack)},l=async e=>{if(`${n}${e.label}`,e.world==="ISOLATED")try{await C(e.path)}catch(t){return S(t,`Failed to fetch ${e.path}`),Promise.resolve(void 0)}else{let t="Only isolated script injection has been supported";throw m(t),new Error(t)}},C=async e=>{let t=[];try{await T(e);return}catch(i){t.push(i)}await d(25);try{await import(e);return}catch(i){t.push(i)}await d(50);try{await import(e);return}catch(i){t.push(i)}if(t.length===0)throw new Error("Logic error: unreachable code w Use code snippets with caution Content Script Injection: The code heavily suggests that it's part of a system for dynamically injecting content scripts (scripts that run in the context of a web page) into web pages. This is common for browser extensions. l Function: This is likely the main function for managing the injection of a script. It checks if the target world is "ISOLATED" (a way of running a script in a sandboxed environment). C Function: This is the function that actually attempts to load the script. It tries import() three times, with delays (d(25), d(50)) in between each attempt. The file it tries to import is given in e.path. The error message we are getting is probably coming from this code. chrome.runtime.getURL(): This function is crucial for extensions. It is getting the URL to fetch files from the extension itself. This makes the browser look inside the extension for the injected.js file. Error reporting: The code contains functions m and S which are sending errors to the extension, probably for debug or error tracking purposes. import(e): The repeated import(e) is the exact point where the error happens. When the injected.js is being imported, it uses the crypto.randomUUID, and since it is unsupported, it fails. Solution and Workarounds Since the problem is in an external extension file, you cannot directly modify the injected.js code. Your solutions are more about working around the issue or ensuring the extension is updated: Update the Extension: If the extension is from the Chrome Web Store, check if there's an update available. The extension's developer may have fixed this bug. Contact the extension support and report the issue. Find an Alternative Extension: If updating doesn't work or there's no update, see if there's a different extension that offers similar functionality and doesn't have this problem. Polyfill: If the extension is not maintained, a way to avoid the issue could be to implement a polyfill. This polyfill could be injected before the extension's injected.js and would create the crypto.randomUUID if it doesn't exists. Disable the Extension: If you don't need the extension at all, disable it in your browser's extension settings. Use a different browser: An old browser version could be the cause of the issue. Try using a newer browser version. Important Considerations Security: Be cautious about disabling security-related extensions. Make sure you understand the risks involved. Extension Development: If you are the developer of the extension, replace crypto.randomUUID() by a compatible UUID method or add a polyfill. In Summary The error "crypto.randomUUID is not a function" in your scenario means that the injected.js file within the extension is trying to use a feature that's not available in the execution environment. You can fix this by updating or replacing the extension, or by using a polyfill. You must investigate which extension is injecting this file. Data used to understand this message Use search instead AI tools may generate inaccurate info that doesn't represent Google's views. Data sent to Google may be seen by human reviewers to improve this feature. Open settings or learn more1KViews0likes4CommentsBring 'custom trusted browser' feature to Windows
Following on for the various Opera-related requests that are 'solved' with either 'use a supported browser' or 'solved on mac': please bring this feature to Windows. My personal motivation is Chrome's recent neutering of ad blockers, combined with the excessive use of Windows system notifications for feature advertisement by Firefox and Edge, and the pushing of Web3/crypto nonsense in Brave.Solved92Views1like8Comments1Password desktop app refuses to run/open
My 1Password desktop app v8.11.8 x64 refuses to open on my Windows 11 x64 computer. The app last auto-updated September 11th and it's been an issue since then. I've been able to use the browser agent for most things, thus I didn't realize the extent of the problem until now. I've tried updating the app which fails. I've also tried uninstalling the app through Windows which also fails. Each time I run these processes it seems to start to run and then there is just no response as if nothing has happened. Opening the app itself does nothing, even opening the app executable from the main 1password folder. I've closed any open programs from the Task Manager, reset the computer multiple times and all have had no effect. I am using the downloaded version direct from the 1Password website, not the version from the Microsoft store. The logs show: "ERROR 2025-10-13T15:07:18.427+00:00 ThreadId(1) [1P:foundation\op-log\src\lib.rs:686] tracing WAS NOT installed" "ERROR 2025-10-13T15:07:18.613+00:00 ThreadId(1) [1P:foundation\op-startup\src\windows.rs:90] Error HRESULT(0x00000000): The operation completed successfully." as the errors in the logs each time I try to run the app or uninstall. I can provide the full logs to the support email if necessary. I've read about disabling Hardware Acceleration, however I don't have the ability to change this without the desktop app actually opening. Unless there is a json setting somewhere that I haven't found. Please help me to resolve this issue and get the app back up and running. Thank you 1Password team.Solved237Views0likes8CommentsBug: 1Password Browser Extension and Standalone App connection problem
Hi, I recently noticed that 1Password's Browser Extension (Edge / Brave) have connection problem with the standalone app. Scenario 1: When I unlock the standalone app it does not unlock its browser extension app. And I have to enter the password again to unlock the browser extension's app. Scenario 2: When browser extension is unlocked it does not unlock the standalone app (which I believe was always the case, but I am not sure), but when I manually lock the standalone it does not lock the browser extension's app. Also, I noticed there is a "connection problem" from the browser extension app. I have reinstalled both browser extension as well as standalone but the issue is same, also for both EDGE and Brave browser. My current standalone version 1Password for Windows 8.11.18 (81118036)27Views0likes1Comment