Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
SSH bookmarks broken since updating
Hi there, I've today updated to 1Password for Windows 8.10.68 (81068012) and this update seems to have broken SSH bookmarks. I do have more than 6 SSH keys enabled that's why I'm using SSH bookmarks. However they don't work anymore, i.e. when I click "Connect" for a bookmark, I still get the dreaded "Too many authenticaton failures" error.
Edit link is not working with Firefox on macOS
Hi ! clicking on the edit button in the firefox extension window does not launch 1PW 8. I tried to quit and relaunch everything but it does not work Firefox version : 91 / macOS 11.5.2 Cheers. 1Password Version: 8.2.0-44BETA Extension Version: 2.0.5 OS Version: macos 11.5.2Experiment #7 - Anti-Peek Mode
Hello 1Password Community! At 1Password, we are constantly looking for new and innovative ways to help you use 1Password with confidence - even when you are out in the world and uncertain of how secure your surroundings are. This is why we’ve introduced Anti-Peek Mode, a new 1Password Labs feature for our Android and iOS applications that provides additional protection from unwanted shoulder surfing when using 1Password in unsecured, public environments. How does it work? When you enable Anti-Peek Mode in the 1Password app on your Android or iOS device, the following protections are applied making it harder for those around you to peek at your data: Items on the Home screen are blurred and require a long press to reveal Usernames, in addition to passwords, are also concealed by default on item detail screens and must be revealed to see Usernames are no longer displayed as subtitles for items on the Home or Search screens Quick actions when tapping on an item field are disabled and any actions (such as Reveal) must be invoked via the item’s overflow menu Recent search results are hidden. The “Always show passwords and full credit card numbers” option is disabled. Screenshots and screen recording are disabled (Android only) How to try Anti-Peek Mode To try out Anti-Peek mode, first, make sure that you are on the latest version of 1Password (8.10.62) on your iOS or Android device. Then, go to Settings > Labs > Anti-Peek Mode and simply enable the feature. We would love to hear what you think of Anti-Peek Mode as we work to make this feature even better! Once you’ve had a chance to try it out, make sure to share your feedback via this survey or by simply posting a comment below. 📣This feature will only be available in Labs until May 31, 2025 so try it out today!
crypto.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 moreWe're the team behind 1Password’s latest product enhancements. Ask us anything! (Wednesday, February 12th)
Hey everyone! 👋 We're the team behind 1Password’s latest product enhancements. Ask us anything! We’ll be hosting an AMA right here on February 12th at 9AM PT / 12AM ET with 1P_MattG - 1Password’s Senior Director of Product, End User Experience. This round of product enhancements includes exciting updates like a smoother mobile experience, better item creation and navigation, new ways to stay secure, and much more. Starting today, you can RSVP to the AMA and drop your questions here in this thread, and then we’ll answer them live during the AMA on February 12th at 9AM PT / 12PM ET! We can’t wait to chat with you and kick off our first AMA in the new 1Password Community! Check out our blog to find out more about our new and improved features. EDIT: The AMA has now officially concluded. Thank you to everyone for taking the time to chat with us! If you have any follow-up questions or feedback, feel free to drop them here. This thread will remain open until February 14th, 2025, at 5:00 PM ET, so you still have time to continue the discussion. Thanks again for making our first AMA in the 1Password Community a great one! 💙 Our AMA Host Matt Grimes Senior Director of Product, End User Experience, 1Password
