Users in production were reporting that UnityAds were occasionally not giving rewards. I was able to reproduce and see that the "reward" callback would occasionally come a few milliseconds after the "close" callback. Adding a 250ms to the existing setTimeout in the "close" callback appears to have fixed the issue in production, and doesn't cause any negative effects for other networks.
Users in production were reporting that UnityAds were occasionally not giving rewards. I was able to reproduce and see that the "reward" callback would occasionally come a few milliseconds after the "close" callback. Adding a 250ms to the existing setTimeout in the "close" callback appears to have fixed the issue in production, and doesn't cause any negative effects for other networks.