Hi,
You can actually. But it involves being aware of the Unity internal optimization when publishing to IOS ( and likely other platforms in the long run).
Basically, if you are using Reflections, which is the case with the actions "get/set property", and "invoke method", then you need to tell Unity which classes you are reflecting, because Unity will not detect it when analyzing your project scripts and it can "strip" a class you use.
this "linker" technic is not inherent to PlayMaker, it's actually something that is done on almost every project using advanced assets, but you are generally not aware of it because the publisher provides this link.xml file already prefilled.
With PlayMaker, you'll have to maintain this list yourself, which is difficult if you don't know how to code, which is why I created this wizard so that you don't have to do this manually.
So nothing scary, just a Unity workflow you need to be understanding when publishing to IOS.
It's "fully" documented on unity doc:
http://docs.unity3d.com/Manual/iphone-playerSizeOptimization.htmlmake sure you read all this page, with great attention, read it again and again until you understand wht it means, and let it sink in your brain.
if there is a concept on this doc page that you don't understand, then making use of Reflection is prone to issues when publishing.
In all cases. I don't recommand using reflections when publishing on mobile, and in general, just because I don't think it's a clean approach, it works and certainly allows non coders to get the job done, but sub optimal, it's like doing surgery and open your belly to feed yourself... just eat normally... that's how I see it

So prefer using a dedicated custom actions accessing in conventional c# your classes and properties. If there is no available custom actions, make one or request one on this forum, and make sure you do a bit of search on both the forum and the
Ecosystem, you might lucky

So to summarize, it's not a problem with PlayMaker, it's a advanced "feature" or Unity that needs to be learned and assimulated to publish on mobile.
Bye,
Jean