Discordant

That's wild. Perhaps it does have something to do with the language, but I also wonder if there is something different about your 1PF file somehow. What version of 1Password are you using to export? Also, you might want to try just exporting a few items (instead of everything) and see if that works. If it does, perhaps there is something in the export that Enpass doesn't like, like a weirdly encoded item? There's also another possibility. Try importing the 1PF file into something else that Enpass supports like KeePass XC or something like that. Then try exporting from the other program and see if Enpass likes that.

I've done this on 3 different machines, so I can confirm it works if you follow the exact directions I posted (assuming you are using a recent version of 1Password and Enpass). Did you check your export from 1Password to make sure it actually contains anything? If you're sure there is data that was successfully exported, make sure you're pulling out everything inside the .1pf file, this will typically include a data file and 2 folders (though this will vary depending on what you actually exported). The folder you point Enpass at needs to have a data.1pif file and perhaps also folders for certain types of other things you exported. See the attached screenshot as an example. This is all inside a folder I happened to call "Export" and I pointed Enpass at the "Export" folder and told it to import 1pf from 1Password.

Hi, If your reported version number is correct, it looks like you are running a slightly newer version of 6.7 than you can access on the beta page (865). I run 865 on a very similar setup to yours and I have no problems starting, pausing or stopping the WiFi Sync Server. Perhaps the version of the beta that you have has a bug in it? You might want to consider downloading the publicly available beta version and try that and see if the issue is resolved?

This is an issue with the qt framework, I believe. I have a few apps that use it that have this same issue. Supposedly this is fixed, but many developers continue to use older versions of the framework for a variety of reasons. https://bugreports.qt.io/browse/QTBUG-88600

@Gulshan Dogra, 1Password does not export items in 1PF format loose in a folder like you show it (not any more). The Mac will have a single file. Enpass does not recognize this .1pf file by default (although it absolutely should). You can follow my directions above to manually pull out the data Enpass can import, but ideally Enpass should recognize a .1pf file and import it.

Allow me to suggest a work-around that will let you get up and running immediately. I also just recently switched from 1Password to Enpass and had this exact problem, but I found an easy work-around that doesn't require anything more than a 1PF and Enpass and access to the Finder. Save the content to import from 1Password as a 1PF file and make note of the location in the Finder. Create a new empty folder somewhere on your Mac. Call it whatever you want. This is where the files to import into Enpass will go. Keep the folder you just created open in a separate window or tab and in a different window navigate to the 1PF file in the Finder. Right click on the 1PF file and select "Show Package Contents". This will open the 1PF file (which is really just a special kind of folder). Do a "Select All" of the files and folders you see in this package content window (⌘A). Drag and drop the content you just selected into the folder you just created in Step 2. Fire up Enpass and start the import process. Select 1Password and the 1PF file format as the import options. When you are asked to select the folder in which the 1PF file exists, instead select the folder that you created in Step 2 above. Enpass will now find the content to import from 1Password and import all of it. I did these steps myself and I was able to import everything. I'm not sure why Enpass doesn't see or work with the actual packaged 1PF file, but I suspect it might be because very early versions of 1Password a long time ago used to export content into a folder instead of a packaged 1PF file? In any case, until Enpass fixes this, the steps listed above will let you get to work with Enpass.