Hi guys, after about an hour of debugging, I found the problem causing the issue - and it may prompt a feature request to add some level of validation to the color naming system.
Inspecting it with the Firefox Developer Tools, I saw that all of the elements that I had set to that color were actually set to be color: transparent; and that the styles for the color that I added were not in any loaded stylesheet, and that it looked that only the default settings were loading. This told me that there may have been a user error, so I double checked the color values to see if any of them had extra characters or were missing some. Upon find none, I checked the names of each color and found out that I had a naming problem.
##So to recap what I did to cause this error, and how I fixed it for me:
I created a new global color in Pro and named it. I then clicked the duplicate icon and created 4 more instances of the color (each new color was renamed with “Copy of” prepended to the name), I went through and changed the values of the colors, removed the “Copy of” and then added a number to the end of each to differentiate the colors.
Apparently while I was doing this, I missed one. It was conveniently named the same name as the original color (because I had already removed the “Copy of” text from the beginning of it, making them identical). When this happened, the builder would show the color just fine, but in the front it would not show.
To fix this in my instance, I just made sure that every color (specifically the color that was missing) all had completely unique names, as it appears that the Pro Builder calls the color value by the name that you give it.
##Possible long-term solutions
Because most other people using Pro may not find this forum post, I think that it may be best to either (1) integrate some level of validation when naming the color (ie. “Cannot have the same name as another color”) or (2) first assign a unique ID to each color, and then calling the id to get the data back.