Axure changed all my prototypes’ ‘Rotobo Light’ fonts to ‘Roboto Thin’ and I had to reassign the ‘Roboto Light’ to all my text manually. I also have a case where: even if I changed the font from ‘Roboto Thin’ to ‘Roboto Light’, when I published to the cloud it reverted the font to ‘Roboto Thin’… Any idea?
Same issue, it would be nice if someone would look into it.
After you (Axure) purged the forums of all community content, the one upside was a fast response rate to tickets. Is that no longer the case?
Thank you for posting about this. If you are still seeing this problem where Roboto Light appears as Roboto Thin in Axure RP, can you please try following these steps?
- Can you please confirm that you are running the latest version of Axure RP 9 (184.108.40.20623)? If not, please try updating via Help > Check for Updates in Axure RP.
If you are seeing this occur in the latest version, this problem could be occurring on your machine due to your specific configuration, such as if the font files or Axure RP’s program files have somehow gotten into a bad state. To troubleshoot this, can you please try the following?
Please try un-installing the fonts from your machine and re-install them via this link from Google Fonts:
Please try clearing Axure RP’s cache and temporary files by quitting Axure RP, and then removing the content in these folders, per your machine type.
For Mac, open the Mac Finder, select Go > Go To Folder, submit the following path, and remove the contents of the Axure-9-0 folder.
For Windows, open the Windows File Explorer, highlight all text in the address bar, submit the following path, and remove the contents of the Axure-9-0 folder.
If the previous steps haven’t helped, and if the font is only appearing as Roboto Thin on preview/publish, I would also recommend checking the Font Mappings settings in your project to ensure that you are not mapping the Roboto Light font to Roboto Thin. Here is a link to more info on this:
If none of these steps has corrected the problem, can you please write in to us at email@example.com, and reference this forum post so that we may troubleshoot this problem further?