Open ShivamPokhriyal opened 4 years ago
@ShivamPokhriyal Sorry for the late reply, have you gotten a solution yet?
@ekigamba yeah this was due to some weird caching in our build system due to which the libraries were missing in the app bundle. So good to close this issue.
But I still think it'd be a good idea to update the realm-plugin.
@ShivamPokhriyal I'm open to updating the realm plugin or adding a DAO abstraction. I noticed that the realm-plugin adds a couple of MBs to the APK. I believe the extra size can be shed off if the database used on the client app (SQLite, SLQCipher, Realm, Berkeley DB, CouchBase Lite) is reused by the DAO
We just uploaded our app to playstore using App Bundles and within couple hours we started receiving below crashes:
From this issue it looks like simply upgrading the realm-plugin to 6.1 should be enough(Though few comments seem to suggest that the issue is happening even on the latest realm-plugin) But at least we'll be able to get a better error message with the latest version.
Though, one thing that's constantly bothering me is how this
MapboxOfflineDownloaderService
is started. My first thought wasKujakuNetworkChangeReceiver
which can start the service on pre-Nougat devices. And yeah, we're also receivingIllegalStateException: Not allowed to start service Intent, app is in background
crashes in android 7+ devices, but that's a different issue and that's already been filed #326 . But I don't think it's the culprit here since I'm getting the aboveMissingLibraryException
even on android 9 devices. And we don't callKujakuLibrary. setEnableMapDownloadResume
so that receiver shouldn't work at all on android 7+ devices right?That being said, perhaps somebody else is starting this service. And we don't even call
KujakuLibrary.init
until we hit a particular screen, which is not used by any of the users so far. So I'd definitely like to know who's starting this service.