Jay-Bob

It is possible to disable all shortcuts for Clipper for your browser in Settings > Shortcuts > uncheck Enable keyboard shortcuts If you use some shortcuts but not others, you could assign the ones you don't want to an unlikely to be used combination. Or are you requesting a more granular ability beyond that to keep global shortcuts on but disable certain shortcuts and not others without manually reassigning the ones you don't use?

Hi@fr0zensphere, @MikeP, @PinkElephant @Paul A., thank you all for your input and for calling out the issue as well as possible workarounds in the meantime. We now have a report filed with this helpful information (I can also reproduce it) and the development team will take a look, but there's currently no ETA on when to expect a fix. Thanks again.

Thank you @Zec for the additional details, we've intermittently been able to reproduce similar behavior as well. Our development team is aware of this and will be investigating, but I don't have an estimate yet on when to expect this to be fixed.

Hi @CausticChemist, thanks for reporting this. What version were you on with the log snippet you shared? 7.18 is currently the latest. Also, I see you mention it happens every time regardless of clip style - but is this error happening for you on all sites as well or just some? Do you remember any specific or general steps to reproduce when this happens by chance?

Thanks for reporting this. If you're comfortable sharing, could you add the PDF url here? If not, please feel free to get in touch with our support team.

@Paul A.Amazon fix is ready and released in 7.15; Gmail fix will not be in 7.15 or 7.16. The Gmail fix is still in development but will be coming asap, but no eta at the moment. Possible workarounds to consider in the meantime, hopefully the Evernote for Gmail add-on or forwarding to the incoming Evernote email address can fill in until then.

Hi @Reuven, this should be fixed on version 7.15. Can you please double check and see if your extension has updated? If the issue is still happening for you on 7.15 please do get in touch with our support team.

I'm glad to hear it! This does seem to be an intermittent issue though, so be aware it may return at some point (hopefully not). Our developers are working on resolving this in all scenarios, but no eta at the moment.

Hi @EricBen, thanks for mentioning this. We're aware of an intermittent issue where this may occur but it doesn't seem to be consistent. I've been trying to reproduce as you mention but have been unable to on my end on 7.14 so far. Anything change in your setup or the type of email where this happens most consistently or did it simply just start happening across the board for you this week? We don't have an estimate on when to expect a fix at this time, but any details you may have are welcome. @gazumped's suggestion could be a good possible workaround in the meantime to give you greater Gmail clipping consistency.

This issue has been resolved and the fix will be included in the next web clipper release. There's still other fixes also being prepared for the release so no eta yet. We do understand Amazon is a very popular page and are working to get it to you all as soon as possible.

@NWEvernNo update yet, but developers are actively working on this.

@Roxie68that is definitely not expected for all web pages. SSome sources may be more likely to trigger that message than others, but it shouldn't be all pages. Please first make sure your app is updated and then get in touch with our support team to investigate what you're encountering in more detail.

@Allan Bogildit sounds like you may be encountering a different issue than the one mentioned in this thread, but defiintely still an issue. Is it a specific source you are sharing when this happens? Is it all webpages from Safari or just certain ones? If you force quit (don't reinstall) Evernote and reopen the app, do the prior shares start to show up?

@Roxie68the issue you're encountering should hopefully be resolved in an upcoming update. If you still see this happening in the coming weeks, please mark down the source content you were sharing so we can try to reproduce the issue, and get in touch with our support team.

Thanks for reporting this @dbareis, our developers will have a look.