Bug Bugs with Unity Ads 4.0.0 in Unity Editor

I found several problems while upgrading from 3.7.5 to 4.0.0. These problems do not occur when running on the Android device, just the Unity Editor (2020.3.25f1 LTS in our case).

1. While testing in the Unity Editor, the [Skip] button on interstitial ads reports UnityAdsShowCompletionState.COMPLETED to the OnUnityAdsShowComplete listener instead of UnityAdsShowCompletionState.SKIPPED.

2. For each ad you show, listener callbacks accumulate and are sent multiple times. Unlike when testing on the device or calling Load(placementId, listener), where listener.OnUnityAdsAdLoaded() is called only for the current load operation, when you call Show(placementId, listener), you get one callback to listener.OnUnityAdsShowComplete() for every ad you ever showed.

3. As mentioned in other forum posts, there's no support yet for Domain Reload disabled, which significantly improves iteration time for in-editor testing. As discussed in the other forum post, the fix would be quite easy for Unity Ad developers to make.

Thank you!

 

Yes, I'm aware these are dummy ads, but the API should still function and be consistent when possible with the operation in a built app (the Unity Player). I do test in both cases but this is just broken and looking at the Unity Ads C# code, an easy fix for most programmers. Also as I said these are new bugs, introduced with the 4.0.0 version, except for the Domain Reload problem which has been around since the feature was introduced in Unity 2019, 2 years ago.

Thank you for passing these bugs on to the development team. I've also submitted a formal bug with these issues.

 

I can verify both these issues. The second is particularly frustrating.

@LIU_Hanyang96 Is there a timeline for the first 4.0.0 bugfix update please?

I've migrated a project from 3.7.5 to 4.0.0 and would rather not revert, given the large amount of breaking interface changes.

 

Just tried upgrading to 4.0.0 to fix an audio issue and encountered the multiple callback firing bug. I'll wait for these issues to be fixed and upgrade when the new release comes out.

 

Hi @LIU_Hanyang96 ,

Have you got any idea when we can expect a release that fixes these issue?

Thank you.

 

Hi @LIU_Hanyang96,

Please could Unity consider issuing a hotfix for the accumulating listener bug on its own? (assuming the next version is weeks away)

It's such a fundamental bug in a key workflow path (for monetisation)

It really is making life very difficult to test any ad related code in the editor. It's resulted in having to debug builds on device which is harder and way more time consuming.

 

Hi @LIU_Hanyang96

I just updated to 4.0.1 and the accumulated listener bug is still occurring. Six weeks and one release later, yet this fundamental and simple to fix bug still exists.

Given that 4.x includes many breaking changes over 3.x, reverting to 3.x is going to be just as painful as living with 4.x

Could you escalate this and ask if a 4.0.2 fix (with only this bug) be released ASAP please?

 

Hi @LIU_Hanyang96

Further to the above, I can also confirm the skip bug is still present.

So skipping the ad results in a status of completed.

 

Hi @LIU_Hanyang96

Any updates on this please?

 

I'm going to reiterate again how essential functional test ads in the editor are. Most development in the real world is done in the Editor, that is a key advantage of Unity over many other engines, on device builds are created much less frequently. If the Editor ads are broken, the game in the Editor (where most of the development work is actually done) will be buggy at best and completely broken at worst for the whole team.

Can the Editor Test Ads be added to the internal Dev/QA sweep sheets you have to ensure that a release never goes out again with these Editor Test Ads broken, please?

With that out of the way and with all due respect @LIU_Hanyang96 , I feel like the level of service we are getting here is not really good enough for an issue like this. If our customers were encountering a blocker, we would try and get a hotfix out in 2-3 days, not 2-3 months.

Given that the packages are standalone and delivered via the Package Manager, the speed at which the devs should be able to update things should really be a lot quicker than this. If QA is the bottleneck because you need to test against so many versions of the engine, you could just roll out unverified packages to speed things up.

 

I just tested the 4.1.0 package that was released yesterday.

Happy to report that both the accumulating callback and skip status issues have now been fixed.

Thank you!

 

I just updated to 4.1.0 aswell, and I definitly keep getting accumulating callback in the editor, so please do not close this issue yet.