Hello,
Michael here from Mobile Ads SDK Support team. Thank you for reaching out to us.
For us to investigate further on our end, kindly provide the below information:
You may provide the requested details privately via "Reply To Author" button or with the below process.
If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
Regards,
|
||||||
Hello,
Confirming that we have received the information you sent. However, we cannot extract the app that was in rar file. Would you be able to send this again privately via "Reply To Author" button or with the same process below and make it a zip file instead?
Hello ph1823,
Can you confirm if you were able to replicate the crash while using the sample app you provided? We were unable to replicate the error you encountered using the sample app you gave (See attached). We will need a screen recording of the replication so we can properly test this on our end and confirm if the sample project is indeed where the crashes happen.
Regards,
|
||||||
|
||||||
Hi,
Thank you for your response.
I've tried again your sample app project, and was able to encounter an error for your implementation in "Wannads". When I tried to comment it, I was able to encounter the crashes that is happening in your provided screen recording when other mediation are enable, but unable to replicate when only inMobi is enable. With that, let me share this to the wider team to further check the crashes from your sample app project provided. We will update you once we have more information on this.
Regards,
|
||||||
Hi,
Thank you for patiently waiting.
We are unable to provide timeline on where this will be fixed. But, rest assured that our team is actively investigating this. We will update you as soon as we have more information on this.
Hi,
Thank you for patiently waiting.
I got an update from our team, and they mentioned that they seen that the "`countDownTimer.cancel()` is called in onPause() method even though the `countDownTimer` is not initialized yet that's why it causes the app to crash.". They also tried your sample app project provided, and added a null checker for the mean time to test the ads, and so far, they haven't encountered any crash while loading and showing the rewarded ads in the app. They also mentioned that they tested them with other networks enabled, and no crash so far on their end.
|
||||||
Hello,
We hope you're doing well. The team has an update for the issue you're experiencing. Would you kindly do a test on your end using the Rewarded Video example with the following dependencies if you still experience the crash:
|
||||||
![]() |
Mobile Ads SDK Team |
Hi,
We do manage Mediation adapter, however, if the crashes are specific to the adapter we recommend to reach out to the respective support team. In your concern, for the file "full_error.txt" file that you've provided to us previously, the error message of "The requested banner size: 412x90_as is not supported by InMobi SDK.", is specific to InMobi SDK. In addition to that, our team has found out that the crash is happening in the InMobi SDK and suggested that you reach out to the InMobi support team with regard to this.
Regards,
Hi Ph1823,
I hope you're doing well.
I just want to circle back with regard to your concern for the error "java.lang.IncompatibleClassChangeError: Found interface com.google.android.gms.location.FusedLocationProviderClient, but class was expected (declaration of'com.google.android.gms.location.FusedLocationProviderClient' appears in /data/app/~~ObvY3oIiyQJUm8_RFkIKGg==/fr.ph1823.datahosting-48w233OsQj3UI7p1u5UwYQ==/base.apk!classes13.dex)" that you're encountering in your end, our team mentioned that as per checking in this log, there is no indication that this is caused by our SDK.