Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. When trying to do a fresh installation of Enpass to a PC that´s behind a proxy with authentication it wont work because you cannot enter proxy settings when doing the first start wizard. My workaround was either to import a backup file or create a new empty file, change proxy settings and then sync in my real stuff via GDrive or WebDAV. Would be nice to be able to configure network related stuff in the first start wizard.
  3. Database is empty

    great :-) thanks
  4. Database is empty

    Hey @misteurz We are aware of this issue and working for a fix and hopefully that will be available soon. Please bear with us. Cheers!
  5. Delete duplicates

    I just wanted to throw in the desire for a 'Find duplicates' tool again. Aside from the obvious accidental duplication, I think many potential users evaluating Enpass run it side-by-side with their current password manager at least initially. Inevitably, there will be duplicates or additions to Enpass that may not be in the other manager, preventing the user from just deleting the full Enpass DB and starting over. Just an upvote for an option to find duplicates.
  6. Database is empty

    up?
  7. Last week
  8. Enpass can't recognize fingerprint

    Hi my iphone 6 stopped recognizing my master password and now the finger print/ touch ID option is gone. If open enpass the first thing it does is say "touch ID failed". Do you have a fix?
  9. Boot-loop after installation from google play

    Hi, I'm usin Xiaomi Redmi 1S with mokee 60.1 release 170413 The latest in play store Right after the installation. Android show a series of windows that inform of a series of services as crashed then the phone enters the boot-loop. Thanks of your attention
  10. Enpass can't recognize fingerprint

    Hey @warubou Please let me know if you've added new fingerprint(s) to the device settings after you enabled the fingerprint to unlock from the Enpass settings. Also, it'd be a great help if you can share what error are you exactly getting while trying to unlock with the fingerprint. Greetings from India.
  11. Boot-loop after installation from google play

    Hey @silvergeko Sorry to hear about the trouble you're going through. It'd be great if you can answer a few queries for looking into it: Which device are you using? Which version of Enpass are you using? Where does Enpass crash, right after the installation is completed or when you run it? Please share the exact steps that lead to the crash. Awaiting your response.
  12. Tap to fill does nothing. It simply disappears from keyboard after pressed. This is specifically on Android 8.1 Oreo.
  13. Multiple/Many/Duplicate EnpassHelper.exe Processes

    I'm using the Chrome plugin. But you did provide some info on the autolock feature, and if perhaps related to the problem.
  14. Hi, today I have installed Enpass on android marshmallow (6.0, rom mokee) and the phone crashed and reboot in boot-loop. To resolve boot-loop I have delete the app manually from TWRP. Any idea? I'm sorry for my bad english...
  15. I guess that reproducing problem can be: install Enpass Extension for Firefox. Each time you will log-in to some web page, you will get Enpass Pop-Up windows for entering the pin. N-Logins = N-EnpassHelper.exe runnig and eating CPU till the full computer crash.
  16. Enpass can't recognize fingerprint

    hello. I'm using Samsung galaxy 7 and Android 7.0 I already resist my fingerprint on phone but enpass does not recognize fingerprint. How to solve this problem?
  17. Wife using Enpass on Surface Book with 27" external monitor connected through Surface Dock. When opening MS Edge, the Enpass Extension will pop up UNDER the browser window. And then she cannot find the dialog, so she thinks it isn't working. If she turns off Maximize, the browser window covers only about half the screen, and then the Enpass dialog appears "appropriately" next to the browser window. She can then double click the entry to sign in and then maximize the window again. It works but is a nuisance. Maybe you can find a solution in your schedule, or maybe there is a better work around. Thx, Lovin' Enpass.
  18. Enpass has stopped Working Error

    I'm having the same issue no, started a couple days ago. Noticed the error when I turned the computer on from sleep, hibernate or restart. Then noticed it happening when there was any kind of network change, disabling VPN for example. This never happened before a couple days ago.
  19. Hello Akash, thanks for your answer - but this is a no-go. traditional and free bridge design is compared to uwp app extraordinary awful, old fashioned and has nothing to do with usability. cheers too
  20. Desktop client (5.6.2) keeps crashing

    Another crash. Process: Enpass [81782] Path: /Applications/Enpass.app/Contents/MacOS/Enpass Identifier: in.sinew.Enpass-Desktop Version: 5.6.3 (138) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Enpass [81782] User ID: 501 Date/Time: 2018-02-16 17:25:22.138 +0100 OS Version: Mac OS X 10.13.3 (17D47) Report Version: 12 Anonymous UUID: FC4EAF6B-46D4-B1BB-1EF4-ABCAAD17E16A Sleep/Wake UUID: 712CDB09-D4E8-4080-9381-A28A2CE26F1F Time Awake Since Boot: 590000 seconds Time Since Wake: 1200 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 in.sinew.Enpass-Desktop 0x000000010b94eda4 0x10b810000 + 1306020 1 in.sinew.Enpass-Desktop 0x000000010b94a20d 0x10b810000 + 1286669 2 org.qt-project.QtCore 0x000000010d264ebc QMetaObject::activate(QObject*, int, int, void**) + 876 3 org.qt-project.QtCore 0x000000010d25df00 QObject::event(QEvent*) + 48 4 org.qt-project.QtWidgets 0x000000010c38f956 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 294 5 org.qt-project.QtWidgets 0x000000010c392415 QApplication::notify(QObject*, QEvent*) + 5941 6 org.qt-project.QtCore 0x000000010d231c84 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 7 org.qt-project.QtCore 0x000000010d289272 QTimerInfoList::activateTimers() + 1266 8 libqcocoa.dylib 0x000000010fb5f752 0x10fb3e000 + 137042 9 com.apple.CoreFoundation 0x00007fff313b5721 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 10 com.apple.CoreFoundation 0x00007fff3146f0ac __CFRunLoopDoSource0 + 108 11 com.apple.CoreFoundation 0x00007fff31398260 __CFRunLoopDoSources0 + 208 12 com.apple.CoreFoundation 0x00007fff313976dd __CFRunLoopRun + 1293 13 com.apple.CoreFoundation 0x00007fff31396f43 CFRunLoopRunSpecific + 483 14 com.apple.HIToolbox 0x00007fff306aee26 RunCurrentEventLoopInMode + 286 15 com.apple.HIToolbox 0x00007fff306aeb96 ReceiveNextEventCommon + 613 16 com.apple.HIToolbox 0x00007fff306ae914 _BlockUntilNextEventMatchingListInModeWithFilter + 64 17 com.apple.AppKit 0x00007fff2e979f5f _DPSNextEvent + 2085 18 com.apple.AppKit 0x00007fff2f10fb4c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044 19 com.apple.AppKit 0x00007fff2e96ed6d -[NSApplication run] + 764 20 libqcocoa.dylib 0x000000010fb6035f 0x10fb3e000 + 140127 21 org.qt-project.QtCore 0x000000010d22e051 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401 22 org.qt-project.QtCore 0x000000010d2322f5 QCoreApplication::exec() + 341 23 in.sinew.Enpass-Desktop 0x000000010b8c7725 0x10b810000 + 751397 24 libdyld.dylib 0x00007fff58cac115 start + 1
  21. Multiple/Many/Duplicate EnpassHelper.exe Processes

    @Akash Vyas Do you know how to reproduce the problem so we can test the build? If not, how do we know the test build fixes the problem? I can go several weeks without a problem. Is the problem assumed to be resolved after 1 month? 6 weeks? 2 months?
  22. Desktop client (5.6.2) keeps crashing

    I'm seeing the same issue in 5.6.3 on mac. Error report looks the same
  23. Multiple/Many/Duplicate EnpassHelper.exe Processes

    Hey @Guillaume Lannes-Lacrouts Sorry to hear about the trouble you're facing. We have fixed some minor issues that might have been causing this problem. It would be a great help if you can download this test build and let me know if the problem persists. Your co-operation is highly appreciated.
  24. Here is some suggestion of Desktop version

    Hey @Jack TANG Thanks for stopping by and writing to us. This feature is already planned and will be available with the next major release. We've tried integrating Windows Hello in the Store app but it didn't offer enough smooth user experience required for an official release due to the lack of APIs. Although, we are in talks with the Microsoft team to make it better and waiting for their support. Till then we appreciate your patience and understanding in this matter. I've noted it down for discussions. Cheers!
  25. Hey guys, Yes, you can import the data from Pocket to Enpass. For this, you need to export the Pocket data to an XML file and then import it using the free desktop version of the app. Please have a look at the user manual to know the steps involved in importing the data. Hope this helps!
  26. Earlier
  27. Enpass has stopped Working Error

    Just to report that I am seeing the same issue as well. I have the most recent version of everything - that is Windows 10 Pro, the Enpass Password Manager, synced to OneDrive, using the Edge browser extension etc.. I don't use Chrome/Firefox.
  1. Load more activity
×