A confirmed transaction showing as 0 confirmations in Armory 0.96.0.2 on macOS

[pf]

I did a transaction through Armory. Fully online wallet.

The transaction went through. It's got > 10 confirmations (as seen on blockchain.info)

Yet in Armory it's still at 0 confirmations.

I tried relaunching Armory, but no success. Bitcoin Core is fully synced with the blockchain.

What gives?

[goatpig]

It's failing to see new blocks. You need 0.96.0.4 for the fix. Otherwise, rebuild & rescan.

[pf]

It's failing to see new blocks. You need 0.96.0.4 for the fix. Otherwise, rebuild & rescan.

I was unable to properly build 0.96.0.4 using exactly the same methods outlined here for 0.96.0.2 (except for checking out the different git tag): https://bitcointalk.org/index.php?topic=1964192.msg19524336#msg19524336

In spite of running "git submodule init" and "git submodule update" before compiling, I still end up with

Code:

$ /Applications/Armory.app/Contents/MacOS/Armory
/Applications/Armory.app/Contents/MacOS/Python: can't open file '/Applications/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py':
[Errno 2] No such file or directory

I also tried this alternative approach you suggested back then:

Code:

git submodule init
git submodule update
make clean
make distclean
sh autogen.sh
./configure
make -j8

Unlike back then, at least the commands are doing something. However, when doing "./configure" I get this error:

Code:

checking python module: psutil... no
configure: error: failed to find required python module: psutil

How to rectify this on macOS? I'm using exactly the install recommended in the macOS build notes: Clean virtual machine with macOS 10.11.6 and Xcode 7.3.1.

[pf]

Update. After running

Code:

easy_install pip
pip install psutil
brew install pyqt

and then doing "./configure", it goes further but still stops at another error:

Code:

checking for pyrcc4... no
configure: error: missing pyrcc4 in path, make sure pyqt4-dev-tools is installed

Not sure how to proceed.

[goatpig]

First of all, 0.96.0.4 does not build on OSX cause of some 1 line of code issue. That's been fixed in testing, but testing doesn't build atm cause reasons.

As for getting through autoconf, right now it's laying out the stuff packages you are missing. You may want to check with other OSX users how to deal with those. These checks should pass on OSX.

[droark]

First of all, 0.96.0.4 does not build on OSX cause of some 1 line of code issue. That's been fixed in testing, but testing doesn't build atm cause reasons.

It doesn't? Just built for me. (That said, this was just building from the command line, not doing a proper build.)

As for getting through autoconf, right now it's laying out the stuff packages you are missing. You may want to check with other OSX users how to deal with those. These checks should pass on OSX.

This file breaks down what's needed to get through autoconf. Nothing has changed on my end.

[goatpig]

It doesn't? Just built for me. (That said, this was just building from the command line, not doing a proper build.)

The tag doesn't, the current state of testing should.

[droark]

It doesn't? Just built for me. (That said, this was just building from the command line, not doing a proper build.)

The tag doesn't, the current state of testing should.

Derp. Sorry. Was talking about the latest code, not the tag, which is broken.