One or more of the following type_info's has hidden visibility


#1

I have an older project that is still using juce 3 that I haven’t had time to upgrade yet. I’m seeing the following error:

2016-11-16 07:52:57.488455 Plugin Host[1477:50003] dynamic_cast error 1: Both of the following type_infos should have public visibility.  At least one of them is hidden. N4juce8TypefaceE, N4juce11OSXTypefaceE.

2016-11-16 07:53:34.784768 Plugin Host[1477:50003] dynamic_cast error 2: One or more of the following type_infos  has hidden visibility.  They should all have public visibility. N4juce9ComponentE, N4juce9PopupMenu13HelperClasses10MenuWindowE, N4juce15ResizableWindowE.

Anybody know what this means and if it’s worth worrying about?


#2

Having the same issue here:

2017-01-31 02:00:31.348396 Plugin Host[23257:7776575] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. N4juce8TypefaceE, N4juce11OSXTypefaceE.
2017-01-31 02:00:31.349850 Plugin Host[23257:7776575] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. N4juce8TypefaceE, N4juce11OSXTypefaceE.
2017-01-31 02:00:31.350219 Plugin Host[23257:7776575] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. N4juce8TypefaceE, N4juce11OSXTypefaceE.

#3

Anyone come up with solutions?

Same problem here. I’m not sure when this really started being an issue within my project, now I can’t run the UI without this error.


#4

This usually comes up when a plug-in throws some kind of Obj-C or C++ exception. I don’t think it’s actually related to OSX type faces. But I’m not entirely sure. Are you seeing this during scanning or plug-in instantiation/deletion?


#5

Turns out I was incorrectly associating this error with the undesired behavior I was experiencing at the time (I’m new to JUCE). When I open the UI in the Plugin Host app, the error is displayed.

I don’t think this error is going to affect me learning how to create plugins for the time being, so I’m not concerned with resolving it :smiley: .