Some android devices not receiving callback to indicate "start" completion

[UKCoder]

Expected Behavior

Calling Leanplum.Start should always result in receiving a NativeCallback with the "start:" message.

Actual Behavior

We've noticed on our Unity project that some android devices never receive a unity NativeCallback indicating that start has completed. This seems to cause leanplum to then never invoke the VariablesChanged callback, resulting in our game never receiving variables. iOS works fine in this regard and does not have the same issue.

I am currently speculating that in Request/RequestOld.java, there is a try/catch block around the HttpURLConnection. This could potentially be throwing a SocketTimeoutException, but when this occurs, so far as I can tell, there seems to be no handling in Util.handleException to retry the request. As this could potentially be happening on the start request, I think there are no further sendRequest calls being made to re-attempt the request.

Alternatively, I note that release 4.2.1 makes mention of fixing a "start" race condition and I am wondering if this could be our problem.

Steps to Reproduce the Problem

Unable to reproduce, but have captured the problem via logging on a production build of our game.

Specifications

• Version: 4.0.3
• Platform: Android
• Subsystem: