Googleads-mobile-unity: MobileAds.Initialize does not trigger callback in editor
It just log Dummy Initialize and not triggering callback in editor environment
Using googleads-mobile-unity 4.2.0 and 4.2.1
Thaina
All 5 comments
Hi @Thaina - this is working as expected, we do not emulate SDK behavior in the editor, you need to run on an Android or iOS device.
stowy
on 13 Jan 2020
@stowy While it's true we hadn't considered doing that in the past, I think this is a valid FR. Ads currently don't load in the editor, but app code may depend on those callbacks and it breaks ability to test app code in the editor.
ericleich
on 13 Jan 2020
@ericleich Thanks for your supportive argument. That's exactly why I have open this issue. I have calling Initialize function in the initial state of my app, and then the SDK just interrupt the initialization of whole app in the editor
@stowy I know that the SDK won't work in editor. But while you have dummying the initialization I hope that you would also dummy the callback too
Thaina
on 13 Jan 2020
Ok I'm happy to accept this as a feature request.
Note @Thaina that we do accept pull requests, so you're welcome to open one and we can work to get that submitted.
stowy
on 13 Jan 2020
@stowy Shouldn't this be as easy as just this?
Thaina
on 15 Jan 2020
Related issues
dylsg
路
7Comments
pacoelayudante
路
6Comments
hnim
路
6Comments
YashSOA
路
5Comments
jaceks454
路
5Comments
Most helpful comment
@stowy While it's true we hadn't considered doing that in the past, I think this is a valid FR. Ads currently don't load in the editor, but app code may depend on those callbacks and it breaks ability to test app code in the editor.