API change in 5.1 breaks my asset (for 5.0) that is in review - what should I do?

My asset is up for review. The 5.1 build introduces a small API change (rename of EventTrigger.delegates to EventTrigger.triggers) that will cause compiler errors in my package. If the asset goes through review and people with 5.1 downloads it, they will get compiler errors. If i fix my package and upload it as 5.1 only people with 5.1 will be able to download it (when the 5.0 version in review works fine)…

Ideally I need to packages for both 5.0 and 5.1 available before they are downloadable on the asset store, or at the very least I need it so users with 5.1 can’t download the 5.0 package… is this possible?

Use conditional compilation, and re-submit (using Unity 5.0).

–Eric

1 Like