Logging backend type ANDROID is not available on the classpath

[AndreyFetisov]

Hello!

some users of my app, have hot this error when app try to init GeoPackageFactory:

Caused by java.lang.IllegalArgumentException
Logging backend type ANDROID is not available on the classpath
com.j256.ormlite.logger.LoggerFactory.setLogBackendType (LoggerFactory.java:67)
mil.nga.geopackage.GeoPackageFactory. (GeoPackageFactory.java:23)
mil.nga.geopackage.GeoPackageFactory.getManager (GeoPackageFactory.java:2)

How i can deal with this issue?

[bosborn]

I can't figure out why AndroidLogBackendFactory would fail to load in OrmLite for some Android users.

I can add an availability check first before setting it. When it is not available, a default available logger should be found.

[AndreyFetisov]

Thanks a lot! Tell me how can I update this in my app? Or I shall wait for the new version of your library to be released?

[bosborn]

I'll try to release patch versions early next week.

[bosborn]

@AndreyFetisov

Released 6.0.1 with the availability check. Let me know if that resolves the issue.

[AndreyFetisov]

Thank you! I updated the library and asked the user to check. This error went away, but another error appeared:
Caused by java.sql.SQLException
Could not find public constructor with ConnectionSource and optional Class parameters class ce.b. Missing static on class?
com.j256.ormlite.dao.DaoManager.createDao (DaoManager.java:87)
mil.nga.geopackage.db.GeoPackageDao.createDao (GeoPackageDao.java:202)
mil.nga.geopackage.srs.SpatialReferenceSystemDao.create (SpatialReferenceSystemDao.java:59)
mil.nga.geopackage.db.GeoPackageTableCreator.createRequired (GeoPackageTableCreator.java:527)
mil.nga.geopackage.GeoPackageManagerImpl.createAndCloseGeoPackage (GeoPackageManagerImpl.java:535)
mil.nga.geopackage.GeoPackageManagerImpl.create (GeoPackageManagerImpl.java:501)

[bosborn]

That error is occurring when ORMLite is attempting to create a SpatialReferenceSystemDao for the SpatialReferenceSystem DAO class. The daoClass in that error message should be "mil.nga.geopackage.srs.SpatialReferenceSystemDao", but is "ce.b" for some reason.

Are they using some sort of obfuscater or app changing securing app?
Do you know the phone model and OS version?
Had they successfully used a version running geopackage-android-map 5.1.0 or earlier? (ORMLite was upgraded from 5.3 to 5.6 in version 6.0.0)

[AndreyFetisov]

Yes, my app uses P8 obfuscation. May be I need to add some rules to proguard-rules.pro?
This error is now reproduced in two users of my app (Honor 8A Android 9 and Galaxy A31 Android 11). On my device error is not reproducible.
I just recently added the geopackage-android-map library to my app, so my users have no any experience with older versions.

[bosborn]

Yeah that does seem like the case. Probably why the Android logging as not working as well.

This seems like a good starting point:
https://proguard-rules.blogspot.com/2017/05/ormlite-proguard-rules.html

Maybe some other useful issues/links that I briefly looked at:
j256/ormlite-android#44
j256/ormlite-android#84
https://stackoverflow.com/questions/25138874/how-to-use-proguard-with-ormlite-in-android
https://gist.github.com/chris-carneiro/e183bb1f2390231356d95c791d76f3a3

Any renamed ORMLite DAO implementation could cause an issue due to how ORMLite loads by reflection.

[AndreyFetisov]

Many thanks for your help!
Adding the following rules helped me solve the problem:
-keep class mil.nga.**
-keepclassmembers class mil.nga.** { *; }