Java crash on some devices traced to Google Analytics

One of my apps has been in the Google Play store (and iOS) for a year, and recently I moved from an old google analytics simple lua file to the Coronalabs Google Analytics plugin. It seemed to be going well on all my apps, but then I got a complaint from one user that the app would not install. I don’t know yet the device and details, but I did more thorough testing with Google’s  pre-launch report, and saw that 2/13 devices had crashes. The crash looked like:

java.lang.NoSuchMethodError: No virtual method getLongVersionCode()J in class Landroid/content/pm/PackageInfo; or its super classes (declaration of ‘android.content.pm.PackageInfo’ appears in /system/framework/framework.jar)

So I disabled pieces and parts and retested to see what made the difference, and removing google analytics made those errors disappear in the pre-launch report. 

The two devices were:

Huawei P8 Lite running an old version of Android

Huawei P8 Lite running an old version of Android

Xperia XZ1 Compact running Android 8

 

I have been building with the latest builds to get the 64-bit support, but specifically 3498, 3512 and 3527.

 

I will try earlier builds also, but there does seem to be a real problem there. Should I be using a different analytics?

I think the Google Analytics was a red herring. After much variation and trying the GameAnalytics plugin (same errors on the same devices), I am getting the error frequently without any analytics plugin. The problem is, occasionally the error will not show up on the pre-launch report, making it hard to diagnose.

In case it matters, I am using  Java™ SE Runtime Environment (build 1.8.0_181-b13)

I went back to build 2019.3490 and still getting the errors on the Xperia. Must be something odd in my build, though I usually check the pre-launch reports for each release. 

Any suggestions what to try?

I rolled back to the last full release (2018.3326) and it gets a clean build in the Google pre-launch report, though of course the warnings about 64-bit compatibility problem and the API 27 warning. In addition, a performance warning. But at least it seems to be a clean build and I hope it will work for my (paying) user.