When I export to HTML and open in Chrome, console complains that it can't find data/fonts.css
and everything displays in Arial. A code comment says this CSS is auto-generated. Is it? If this CSS was present, would it display the fonts correctly?

When I export to HTML and open in Chrome, console complains that it can't find data/fonts.css
and everything displays in Arial. A code comment says this CSS is auto-generated. Is it? If this CSS was present, would it display the fonts correctly?
In UXPin you can ask and answer questions and share your experience with others!
Hey Eric,
Thanks for letting us know! We had a closer look into this, and we're happy to say that this should be fixed now. Just make sure to export the prototype one more time.
Nothing seems to have changed for me. I exported again and it's still missing that CSS file. Tried reloading UXPin. Tried closing/reopening UXPin. Still the same.
On a hunch, I tried to export a brand new prototype and the data/fonts.css file was there. That doesn't really help me much with my existing prototypes. But may give you some insight.
In that prototype, I used an uploaded font and a TypeKit font. The uploaded font displays just fine. The typekit font does not. However, I think that's a known thing and I can work around that.
Any way we can extend this fix to existing prototypes?
It seems that the data stored in the app might be causing this issue for the prototypes you have previously exported. In that case, I would suggest clearing cache and cookies to see if that fixes things.
For TypeKit fonts, since exporting designs takes place on the UXPin servers, there is no access to them, and indeed they will be converted to Arial in Exports. The same when it comes to Local Fonts.
See info on this here: Adobe Fonts; Local Fonts.
Let me know if the above troubleshooting helps. If the issue still persists, could you send us the preview link to that prototype at hello@uxpin.com? We will investigate it further then.