After waiting for 2 weeks finally I got the response from the Unity team and they declined my submission. The thing is that in order to the plugin to work it needs to import first Google VR SDK and iTween, I’ve explained that in a video tutorial included in the submission and within the README file, but it seems that the reviewer just imported the package and since it depends from that other libraries obviously there was going to be errors. So my question to you is how you do when your code needs from another plugins? Should you include that plugin within your submission (that doesn’t make sense to me, but if it’s possible I’ll do it)? Is there a way to inform the review team of Unity that your plugin depends on other utilities? Is it possible to tell the team to check the media and README files posted in the submission?
Thanks in advance. I hope that for the next submission review won’t take two more weeks.
Does the Asset Description clearly state the dependency? A lot of times the readme gets overlooked, and tutorial videos aren’t the place to disclose dependencies so it might just be that the asset didn’t seem to clearly indicate that other tools were required.
Also, I think you might be able to include iTween, as many assets already do. Could be the same with GVRSDK?
You can respond to the rejection email directly for clarification or suggested ways to resolve the issue.
Thanks a lot for the reply. I’ll include that dependencies in the description right now.
It was a pity it didn’t get approved because the timing was perfect for a presentation about it I have just today about UX in VR/AR. Oh, well, shit happens specially when you are a tiny fish in the sea.