Pushwoosh/pushwoosh-unity

A lot of crashes

Closed this issue · 2 comments

Hello.
Unity 2020.3.29f1 (pushwoosh-unity version 6.0.11 )
Our published application has a lot of crashes with an error:

java.lang.RuntimeException: at android.os.AsyncTask$4.done (AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383) at java.util.concurrent.FutureTask.setException (FutureTask.java:252) at java.util.concurrent.FutureTask.run (FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run (AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641) at java.lang.Thread.run (Thread.java:923) Caused by: java.lang.NullPointerException: at com.pushwoosh.repository.y.a (Unknown Source:29) at com.pushwoosh.repository.RepositoryModule$a.a (Unknown Source:12) at com.pushwoosh.repository.RepositoryModule$a.doInBackground (Unknown Source:2) at android.os.AsyncTask$3.call (AsyncTask.java:394) at java.util.concurrent.FutureTask.run (FutureTask.java:266)

I saw that a similar problem was solved in Pushwoosh/pushwoosh-inbox-ui-android-sdk#7
where it was said that the problem is in Pushwoosh SDK 6.4.1.
In the commits, I see that pushwoosh-unity version 6.0.11 depends on Pushwoosh SDK 6.4.1
But the problem persists. I also see that your other SDKs already have dependencies on Pushwoosh SDK 6.4.2

Tell me, will the release of pushwoosh-unity with a dependency on Pushwoosh SDK 6.4.2 solve our problem?
Thank you in advance for your reply.

wfhm commented

@programmervasily hi,

The issue actually appeared with the 6.4.0 release, and the 6.4.1 patch addressed it shortly after. The 6.0.11 release was rolled out specifically to fix this issue, so this is quite strange. Could you please double-check that Pushwoosh dependencies were resolved to the 6.4.1 version? Also, were you able to reproduce the issue locally or do you get it from analytics only?

Thank you for your responsiveness. Indeed, the problem was in Pushwoosh dependencies.