-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not support multi process #136
Comments
@NiaNingXue, could you try using this MaxNativeAdLoader(final String adUnitId, final AppLovinSdk sdk, final Context context) Vu Chau |
Do I need to call the initializeSdk in every process? when I do this, it crash
the crash stack in process "com.alpha.demo:one" :
|
@NiaNingXue, you should not have to initialize us in every process. You should be able to pass the SDK instance around. Let us know if there are any issues doing that. |
I test the constructor but it has the same error and crash stack.
From the stack it shows that you make a activity weakReference, and the weakReference is null? |
Hi @NiaNingXue - The crash will be resolved in the next SDK release, I'll notify this thread when that happens. Is there anyway you can pass in an Activity to your |
@thomasmso I think it is better not to pass a activity when loading a ad, because it may lead to memory leak |
We will only hold a |
I am used to cache the loaded MaxAd, I don`t know if it affects something |
@thomasmso Hi, I also test the MaxInterstitialAd in multi process, it will crash too
The full stack:
|
^We just released v11.1.1 with the fix, thanks once again for the valuable feedback! |
Hi, just test the version 11.1.1 and the MaxNativeAdLoader now works. but MaxInterstitialAd still has a problem. MaxInterstitialAd can load , but when I call showAd(), it only show a black screen, please confirm @thomasmso |
Can you send over a video recording of the issue, and our SDK's verbose logs? |
Do you have an email for receiving video? |
@NiaNingXue just curious) what is your use case? Am I right, that in case AppLovin crash, you main app still working? |
@NiaNingXue, one way to determine if that is related to the multi-process use case you were trying to achieve is to request that ad from our sample app and see if you get a similar issue (black screen). This is because such issues tend to be due to specific ads and not necessarily because of your architecture. Another way is to check how consistently you get that issue. If you always get a black screen in your multi-process architecture and never get it otherwise, then it can help us narrow down on the causes. Thank you. |
Thanks @chauduyphanvu , I am sure it is because of the multi-process. I fix it by adding the "multiprocess="true""
|
@NiaNingXue - ah, that's great news. Thanks for the update! |
My app have three process, the AppLovinSdk can initialize in the main process, in other process, it can initialize , but when I use MaxNativeAdLoader to load ad, it throws the NPE.
the sdk I am using:
implementation 'com.applovin:applovin-sdk:11.1.0'
implementation 'com.facebook.android:audience-network-sdk:6.8.0'
implementation 'com.applovin.mediation:facebook-adapter:6.8.0.8'
the full stack:
W/System.err: java.lang.NullPointerException: Attempt to invoke virtual method 'android.app.Activity com.applovin.impl.sdk.a.a()' on a null object reference
W/System.err: at com.applovin.impl.sdk.m.ao(Unknown Source:4)
W/System.err: at com.applovin.impl.sdk.o.C(Unknown Source:10)
W/System.err: at com.applovin.impl.sdk.o.a(Unknown Source:181)
W/System.err: at com.applovin.impl.sdk.o.s(Unknown Source:394)
W/System.err: at com.applovin.impl.sdk.o.(Unknown Source:33)
W/System.err: at com.applovin.impl.sdk.m.a(Unknown Source:148)
W/System.err: at com.applovin.sdk.AppLovinSdk.a(Unknown Source:153)
W/System.err: at com.applovin.sdk.AppLovinSdk.getInstance(Unknown Source:0)
W/System.err: at com.applovin.sdk.AppLovinSdk.getInstance(Unknown Source:14)
W/System.err: at com.applovin.sdk.AppLovinSdk.getInstance(Unknown Source:5)
W/System.err: at com.applovin.mediation.nativeAds.MaxNativeAdLoader.(Unknown Source:0)
W/System.err: at com.demo.app.ad.max.MaxAdCacheManager.createAndLoadNativeAd(MaxAdCacheManager.java:79)
W/System.err: at com.demo.app.ad.max.MaxAdCacheManager.getNativeAd(MaxAdCacheManager.java:71)
W/System.err: at com.demo.app.ui.HomeActivity.onResume(VaultHomeActivity.java:212)
W/System.err: at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1456)
W/System.err: at android.app.Activity.performResume(Activity.java:8135)
W/System.err: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4434)
W/System.err: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4476)
W/System.err: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
W/System.err: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
W/System.err: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
W/System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
W/System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
W/System.err: at android.os.Looper.loop(Looper.java:223)
W/System.err: at com.demo.app.Application$5.run(LockApp.java:199)
W/System.err: at android.os.Handler.handleCallback(Handler.java:938)
W/System.err: at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err: at android.os.Looper.loop(Looper.java:223)
W/System.err: at android.app.ActivityThread.main(ActivityThread.java:7656)
W/System.err: at java.lang.reflect.Method.invoke(Native Method)
W/System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
The text was updated successfully, but these errors were encountered: