Bug: Unable to apply text style to component text

Discovered the problem. If a variable string for a font family isnt valid, styles applied with that variable in it cannot be changed or applied to layers. If it is already applied to a layer, it is locked and cannot be changed. Only way to resolve is to fix variable reference to font family. No error or feedback message communicates this.

Hi ​@James_Hines1, thanks for flagging this and following up sharing what you discovered! 
 

Just to make sure we fully understand what happened on your end:

• Was the font family variable pointing to a font that isn't available in your org's font library, or was it a typo/broken reference?
• Were all affected text layers using that same variable, or did some unrelated layers get locked too?
• Are things working as expected now that the variable reference is corrected, or are you still seeing any layers that remain stuck?

For anyone landing on this thread with a similar issue, here's what James discovered:

If a string variable bound to a font family is invalid (for example, it references a font that isn't installed or available in your org), any text style using that variable will become locked. You won't be able to change or apply it to other layers. There's currently no error message that flags this; the style just silently stops working.

The fix: Update the font family variable to point to a valid, accessible font. Once corrected, the text style should become editable again.
 

With these additional details, we can flag the lack of error feedback to our team, as that's clearly a pain point, you shouldn't have to guess why a style suddenly stops applying. Appreciate you digging into this!

• Was the font family variable pointing to a font that isn't available in your org's font library, or was it a typo/broken reference?
  • It was a typo
• Were all affected text layers using that same variable, or did some unrelated layers get locked too?
  • Only layers with the same text style containing the broken variable was effected.
• Are things working as expected now that the variable reference is corrected, or are you still seeing any layers that remain stuck?
  • Things are working as expected, so as feedback I think it would be good if an error message or toast clarifying why it couldn't be applied or changed would improve the experience.

Thanks for the additional context, ​@James_Hines1! 

I’ve passed this onto the team to ensure we add a toast notification/error message.