Had a weird issue yesterday. A (custom) font file was not found when referring to it by font family name. It worked fine in a normal build so I couldn't see what the problem was. Tried referring to the specific font filename instead in one of my text objects and it worked right away.
Then I changed the code back to the old version (which didn't work at first with a live build), and now the same code did work. So somehow changing the font family name to the literal file name "unlocked", changed or fixed something permanently that was wrong before.
Does anyone have this as well? It might be important because it could be broader than just font assets and is too erratic for decent debugging and developing.