Maya IO in 2016.5 and 2017 Mac Development

[Anonymous]

Hello,

I was wondering if anyone has some experience developing plugins on the Mac OS.  We have been building the same plugins for years and rarely make any changes to the interface side of the code.

Anyways, We inherit from the MPxGeometry object to represent geometry in the scene.  Using this object, we can implement the IO functions to save our data out with the Maya file.

Anyways, I have noticed that with Maya 2016.5 (extension 2) and Maya 2017, something happened which is effecting our ability to write out to the provided std::ostream.  It basically seems like a junk stream.  The internal buffer is NULL which doesn't make any sense.  Making basic calls to the stream cause memory exceptions.

Has anyone seen anything like this?  Has anyone noticed what may have changed?

I'm using Xcode 6.1.1 and targeting the 10.9 base SDK as that is what the Maya Mac API says to do.  When I test against 2016, the stream works as expected and the particular buffer (_M_Streambuf) is not null.  All the stream flags say everything is fine and I have no clue what may be calling this.  If I were to guess, I'd say that we have some kind of linking problem or something about the Object definition changed which we didn't adapt to which causes them to give us an unusable stream.

If anyone has any ideas I'd really appreciate it.