For example, if there is a bugfix in plugin X resulting in a new version of it, do I automatically get that new plugin version the next time I build? Or, is the new plugin version only included in the next Corona release/daily build?
You automatically get the new plugin binary when you rebuild. Plugin updates aren’t tied into a daily build. They do have a baseline however, generally the last public release (the one before the latest public release).
Thanks Danny!
Follow-up questions:
-
If I only get the new plugin version when building, how can I test it in the simulator? In other words: say I want to test a bugfix in the new version of plugin X. How can I do that in the simulator without building to device?
-
Since I have no control of the plugin versions (as any new versions are included without notice when I build), how do I know what to test in the “last build” before submitting to e.g. ApStore? I can control the Corona version by testing on the same version as the one I am using when finally submitting, but that does not seem to be the case with plugins.
You automatically get the new plugin binary when you rebuild. Plugin updates aren’t tied into a daily build. They do have a baseline however, generally the last public release (the one before the latest public release).
Thanks Danny!
Follow-up questions:
-
If I only get the new plugin version when building, how can I test it in the simulator? In other words: say I want to test a bugfix in the new version of plugin X. How can I do that in the simulator without building to device?
-
Since I have no control of the plugin versions (as any new versions are included without notice when I build), how do I know what to test in the “last build” before submitting to e.g. ApStore? I can control the Corona version by testing on the same version as the one I am using when finally submitting, but that does not seem to be the case with plugins.