When trying to import IAP plugin from Service window on 2017.3b8, I always get this contradictory popup:
Anyone else using IAP successfully in 2017.3 beta series?
When trying to import IAP plugin from Service window on 2017.3b8, I always get this contradictory popup:
Anyone else using IAP successfully in 2017.3 beta series?
Gosh, ran into this bug, too, just now. So basically no monetization works in this beta. This has been a really tough one.
Hi @Claytonious
I couldn’t reproduce this Unity IAP issue in 2017.3.0b4.
I’m downloading 2017.3.0b8 and will test it then.
Could you please tell me some steps to reproduce this issue?
Hi @Claytonious
I still couldn’t reproduce it in 2017.3.0b8.
Could you please try it again?
Hi, @unityjingyao - I included more details on bug report #970784, including a simple repro project. But you probably don’t need it because the steps are this simple:
This was with 2017.3b8 on Mac OS X 10.12.6 - maybe this is specific to Mac?
Any help or a workaround that you could provide would be much appreciated! Thanks for looking into it, either way, though.
I also tried manually copying over the IAP plugins folder from an older project from an earlier Unity version - this runs the API updater of course but afterward same result as above - compiler errors due to “broken assemblies”.
I think have found the root cause of the problem and how to “fix” it.
I just updated to 2017.3 beta 10, repeated all steps, and now everything is working. I do NOT believe this is fixed because of any difference between beta 8 and 10, though. The main difference is that while I was on beta 8, I only had the Android build module installed. (I had installed the editor and the Android module - no iOS, no Windows, etc.). When I updated to beta 10, I installed all of these modules this time:
Android, iOS, Windows, Facebook, WebGL.
This time - IAP is working. I think you guys have accidental dependencies in those IAP DLL’s, such that if you install the editor with only the Android module as I had, you will have a bad day.
Thanks for your investigation Claytonious. We will try to reproduce the issue here and see how we can resolve this.