Checked, but should not have to. This is the sample from the math2d documentation site, so I assume it is good to go. The other plugin I added synced, just not math2d.
According to the docs for the plugin, you do have to. I don’t know to which plugin you refer that works without updating the build.settings file, but one would presume it was a free plugin.
To confirm, you have added the correct entry to the build.settings file for math2d, correct?
I tried the app on a PC and it works perfectly. On the Mac I am still getting the same error, however if I delete the existing plugins I then get the following message when I run the code.
I found the problem. For some reason, the .lua version is being used instead of the .dylib version.
This is probably being caused by the fact that the original version of math2d was a Lua only library, but when I updated I moved to a binary version. I don’t think many plugin developers have done this, so I got to uncover this issue on OS X.
TL;DR In short, if you previously used the Lua-only version of this plugin on OS X and then switch to the native (binary) version, the simulator will (wrongly) use the Lua version of the plugin instead.
Fix
Open this folder on OS X: ~/Library/Application\ Support/Corona/Simulator/Plugins/plugin
Originally thought the problem was bigger and impacting on other plugins, once I realized it was limited to math2d I did try to edit the title but couldn’t.
Anyway. Seemed to fix the problem in the simulator, however I have another issue (not sure if I should start another thread?). When I install your samples (tried “math2d_01_basics” and “math2d_03_segmentCircle”) I get an error.