mapView on a Motorola - DROID RAZR - causing some background crashes

Solar2D Android
#1

Hi, 

I have an app that uses mapping and runs ok on my Asus Nexus 7. I just received this logcat from a tester running a Motorola - DROID RAZR on Android 4.1.2. These errors occur right when my app opens the mapView. Seems like there are some background processes which don’t quite run well on this device. In particular please note : 

SQLite database failed to load from /CachedGeoposition.db

SQLite database failed to load from /GeolocationPermissions.db

Can someone from Corona Labs kindly evaluate this situation for us and let us know if the app is still running reliably despite these sqlite files being available on this particular make & model of Android device?

logcat follows. Thanks for your help.

00:35 E/SQLiteLog: (14) cannot open file at line 30174 of [00bb9c9ce4] 00:35 E/SQLiteLog: (14) os\_unix.c:30174: (2) open(/CachedGeoposition.db) - 00:35 D/WebKit: ERROR: 00:35 D/WebKit: SQLite database failed to load from /CachedGeoposition.db 00:35 D/WebKit: Cause - unable to open database file 00:35 D/WebKit: 00:35 D/WebKit: external/webkit/Source/WebCore/platform/sql/SQLiteDatabase.cpp(71) : bool WebCore::SQLiteDatabase::open(const WTF::String&, bool) 00:35 E/SQLiteLog: (14) cannot open file at line 30174 of [00bb9c9ce4] 00:35 E/SQLiteLog: (14) os\_unix.c:30174: (2) open(/GeolocationPermissions.db) - 00:35 D/WebKit: ERROR: 00:35 D/WebKit: SQLite database failed to load from /GeolocationPermissions.db 00:35 D/WebKit: Cause - unable to open database file 00:35 D/WebKit: 00:35 D/WebKit: external/webkit/Source/WebCore/platform/sql/SQLiteDatabase.cpp(71) : bool WebCore::SQLiteDatabase::open(const WTF::String&, bool) 00:36 D/TilesManager: new EGLContext from framework: 50caff38 00:36 D/GLWebViewState: Reinit shader 00:37 D/GLWebViewState: Reinit transferQueue
#2

I’ve seen these error messages before.  It’s not a crash.  What’s happening is that Google’s version of WebKit (the library used to render WebViews on Android) is “catching” this error/exception, handling the error, and printing it to the log.  It’s a harmless error that is correctly caught by Google’s WebKit library that is generating needless noise in the log.  What triggers it is using the JavaScript geolocation APIs in a WebView.

Now, I say it’s harmless because JavaScript is still able to successfully acquire geolocation data from the device.  For example, notice that Corona’s MapView is still able to display your current location on the map (the blinking dot) even when these errors get logged in the background.

#3

Great! Thank you very much for your kind confirmation. Most appreciated. 

#4

I’ve seen these error messages before.  It’s not a crash.  What’s happening is that Google’s version of WebKit (the library used to render WebViews on Android) is “catching” this error/exception, handling the error, and printing it to the log.  It’s a harmless error that is correctly caught by Google’s WebKit library that is generating needless noise in the log.  What triggers it is using the JavaScript geolocation APIs in a WebView.

Now, I say it’s harmless because JavaScript is still able to successfully acquire geolocation data from the device.  For example, notice that Corona’s MapView is still able to display your current location on the map (the blinking dot) even when these errors get logged in the background.

#5

Great! Thank you very much for your kind confirmation. Most appreciated.