Got several Android crash reports with a recent build @network.NetworkRequest$AsyncNetworkRequestRunnable.run

Solar2D Daily Builds and Public Releases
#41

java.lang.NullPointerException
at network.NetworkRequest$AsyncNetworkRequestRunnable.run(NetworkRequest.java:1839)
at java.lang.Thread.run(Thread.java:841)

Last reported

Today, 3:34 PM

Reports this week

7

Reports total

7

Application version

 
1.0.67

Android version

 
Android 4.37

Device

 
Xperia Z1 (C6903)3
2.
 
Galaxy Note3 (hlte)2
3.
 
Xperia Z (C6603)1
4.
 
Galaxy Nexus (maguro)1

 

  1. Yes this crash only occur with 2179 build. Not sure with 2171-2178 builds.

When I switch back to 2170 build. The crash is gone.

Hope that helps!

#42

Wow, Corona

based on the information above,

I really don’t know what else you need to believe something is just off between build 2170~2179

#43

I am going to create a sample app just so I can submit this bug right now so this can get resolved, this is not good.

#44

Please try with 2182.  We’ve fixed a case that could be causing it, and it should produce more useful information in the log files.  If you can try with 2182 and let us know if it fixes it, or more likely the crash will stop but the network error will still be there and info from the logs will be most helpful in helping is make this solid.

Thanks

Rob

#45

@eja are you able to try it with build 2182?

Looks like only you can reproduce it offline.

#46

In response to both yes I was able to test using build 2183 and everything now seems fine. Thanks Rob

#47

@eja Thanks for your testing and it’s a good news.

However, Rob said earlier: “but the network error will still be there and info from the logs will be most helpful in helping is make this solid.”

Do you see any “extra network error” even there is no more crash?

#48

@Corona

Is it possible to tell us a bit more what kind of logs should be expected? and in what condition this bug would be triggered? and what causes the bug and what has been fixed?

I will see if I can play around with the app to hit the conditions that may cause the bug.

#49

I’m not sure.  What I got from engineering what that the exception was in a block of code that was triggered on a network error.  This causes the app to not crash any more, but it doesn’t fix the fact that you got an error from the server side.  You need to make sure you’re trapping your network errors and handling those conditions.

#50

@eja 

Based on Rob last post, there is some extra log when the exception is caught.

Have you seen the “extra log output” while you are trying it?

It can help Corona to make the network handling more solid.

#51

@joe528, I am sorry after this issue was no longer replicated on builds 2182+ I have moved on, but if its any help I have a retry network function in place and the crash was happening when the network would fail and not even run through my “retry” function. Everything is 100% fine now, no more crashes so I didn’t take the time to check the logs since it was fixed.