so if this isn't immediately solvable, I'll move on from it (and hopefully not encounter a similar issue with Aurora 0.16.0)