to billj...

You're welcome billj​ 

I just added the --to_format csv extra options when the onepux converter is selected.  It will be in the next update.

Let me know if you'd like some debugging code added to the CSV generator so that we might debug this issue. 

billj​ 

You're welcome.

See if you can learn about shell aliases / functions, as I mentioned earlier.  That will save you from having to paste commands into Terminal.  Also, you can drag your file onto Terminal and it will place the file's path for you.

You are correct - the onepux converter requires the additional --to_format option to be manually added.  This conversion being such a rare usage, I didn't bother updating the helper app.

The error you see indicates that the 1PUX file contains a record with some field that has an empty label.  Another user had seen this error, but there was no resolution, and I was not able to reproduce the circumstances.  I could add some additional debug in the code to help isolate the record or issue, if you're amenable to exploring this.

The Onpux.pm generator produces its CSV - it does not use the Csv.pm converter module.

Thank you so much.

So far, the dev version (2025-12-07-0839) eliminates the slowdowns and beachballs.

Meanwhile, your earlier comment about running directly in Terminal got me to look at the Terminal window that mac-helper opens, and I now have a set of Terminal commands I can paste in at the shell prompt. Nice.

In the process of doing this, I observed that the onepux converter isn't happy if the converter options field is left empty in the Convert File dialog.

The onepux converter can only generate the following format(s):

   csv

Provide the --to_format option to specify a generator.

So I tried entering "--to_format csv" in converter options, and the onepux converter was happy.

Also, after successfully running the the onepux converter in both the 2025-06-06 version and the new Dev version, Terminal includes this:

Use of uninitialized value $field in lc at

/Users/bjustin/Desktop/mrc-converter-suite/./MCS/Generators/CSV.pm line 320 (#1)

    (W uninitialized) An undefined value was used as if it were already defined.  It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables.

As I said, I still get my .csv output. But this also is displayed in Terminal, which I hadn't noticed until today.

One last question, prompted by the "uninitialized value" notification: does Onepux.pm generate the .csv output on its own, or does it call upon Csv.pm?

Again, I so appreciate your help.

Bill

billj​ 

I've posted a development build which recompiles the macOSConvertHelper.  Can you give it a try?

Ok, I'll try the helper in the morning to see if I can reproduce the issue.

The helper just builds the command line for you, opens Terminal, and executes the command (by sending an Enter key).  You can simply use that command line in Terminal instead of the helper.  In fact, you can simplify the long command line by defining an appropriate shell alias or function.  With that, your command could be as simple as something like:

    conv somefile

Your text above revealed the answer I was looking for.  You're using the **onepux** converter module.   I recall our past conversations about using this converter, but wanted to be clear about this issue.

Is the trouble with the macOSConvertHelper ?

It seems to be. I launch macOSConvertHelper.app and get a spinning beach ball. Then I click on "1Password 8 (1PUX to CSV)" and get another lengthy beachball. And so forth at every step, until I get to the dialog box with the "You may enter additional converter options below:" field, At that point, I believe I can click on the button without getting a beach ball, and after that, a Terminal window appears promptly.

If so, have you tried directly using the command line it ultimately issues?

No. But I'd be happy to do that if you tell me how (or point me to the section in the documentation where it's spelled out.)

And what converter are you using?

At the top of Changes.txt is 2025-06-06. The name of the downloaded .zip file I used is "mrc-converter-suite-2025-06-06-0932.zip". Is that what you mean?

billj​ 

That's OK.   You wrote:

I updated my Apple Silicon MacBook Pro to macOS 26 Tahoe; I'm currently running 26.1. Tahoe doesn't exactly kill MrC Converter, but sure slows it to a crawl and puts up a lot of spinning beach balls along the way. I was able to convert my data, but it felt pretty iffy at times. Sigh...

Is this a known issue? Will you be releasing a fix?

Sorry. Forgot to include MrC Converter info: I'm using 2025-06-06 release.

Is the trouble with the macOSConvertHelper ?

If so, have you tried directly using the command line it ultimately issues?

And what converter are you using?

Would you like me to add my Tahoe comments to this thread?