EDIT: Okay. It turns out that the following was a false alarm. I don't know what happened behind-the-scenes but I just migrated to a new Mac that came preinstalled with macOS 10.15.1. I fired up Armory, expecting it to complain. It didn't. So, all should be well. However, when you run, you have to stay on the OpenSSL 1.0.x line, due to Python nonsense that doesn't apply to Armory. If you bump into an issue where brew installs OpenSSL 1.1, run the following command from the terminal, as seen here. This should do the trick.

Code:

brew reinstall https://github.com/tebelorg/Tump/releases/download/v1.0.0/openssl.rb

Thanks. I'll leave the directions below in case the migration directions are useful to anyone.

--------------------
Hi. Just wanted to get a message out to everyone. If you're running macOS and Armory is important to you, please don't upgrade to 10.15 just yet. Long story short, due to a library dependency, Armory won't run. I don't think there's a way around this without a library upgrade. Said upgrade will be part of 0.97. As always, this is a work-in-progress. (I had some great momentum a couple of months ago but now life is eating up a lot of my free time.)

If you have already upgraded to 10.15, you have some options.

Option 1: Downgrade back to 10.14. I haven't tried this method. This is very much at your own risk.

Option 2a: Use a virtual machine. This is more involved and requires some technical skills. It's also guaranteed to work (with some minor caveats). The steps are as follows.

- First off, back up both your Armory data and Bitcoin Core data. If you have a paper or digital backup, great! If not, don't fret. You can copy your Armory data folder, although this is very much at your own risk. (If you don't know your way around PCs, just stick to paper or digital backups and wait for the upgrade.)
- You'll need to run either Windows or Linux, or macOS 10.14. If you have a separate PC, you're good to go. If you only have a Mac on 10.15, and you have enough resources (4-core CPU and 8GB RAM minimum, along with at least 40GB of storage), you can run what's called a virtual machine. This is basically a way to run an operating system on top of another operating system. VirtualBox is free but I find it clunky. VMWare Fusion costs US$50 but is easier to use, and arguably a bit more stable (with one caveat listed below).
- For the VM, install your desired OS. I recommend the latest Windows 10, or Ubuntu 18.04 (latest long-term stable release), or macOS 10.14 (will need a free Mac developer account to download the latest image, and then do some black magic to create an ISO that your VM software can handle, so I don't recommend this except to fellow tech nerds). I recommend Ubuntu if at all possible but Windows should work fine, and it's still free.
- Run the VM OS, install the latest security patches, and install Armory and Bitcoin Core on the VM.
- If at all possible, copy over your Bitcoin Core and Armory data, or at least put it somewhere that the VM OS can access it (512GB or larger thumb drive is best). This is the quickest option. Otherwise, you'll have to download the entire blockchain again, restore your wallet from your backup, and wait for Armory to resync.
- Run both Bitcoin Core and Armory from the command line, with the options to read the respective data from appropriate directories. Look here for Armory pathing and here for Bitcoin Core.
- Use Armory as normal.
- Once Armory supports 10.15, you'll either need to stick to using the updated data (e.g., on your thumb drive) or copy the updated data back to your normal Mac directory. That's your call. Either way, be consistent, use only the updated data, and don't try to go back to 0.96.x (unless you use a VM or separate computer).

Please note that VMs can be a little weird at times. They're inherently slower than the OS that they're running on. In addition, strange bugs can affect your experience. While it was a bit of a worst case scenario, a bug in macOS 10.14.6 made my VMs unusable for weeks (which, in turn, helped kill my Armory upgrade momentum). Please be careful if you go down this path.

Option 2b: Use a separate PC. The steps are basically the same as 2a. You'll just be on a physically separate PC. If it already has Windows or Linux on it, there's no need to reinstall, although you should make sure to run with the latest security patches installed.

I believe that covers all the bases. If you have any questions, please don't hesitate to reach out.

Thanks for your patience!

droark

Posts

Merits