I’m not sure since I don’t work directly with Android, but that seems like a mistake in paths by the vendor’s OS. It is only searching in ‘arm’ and ‘armeabi’ for native libraries, but it should be also searching in ‘armeabi-v7a’ and ‘arm64-v8a’. @pasin Do you know what Android developers are supposed to do in this situation?
The same issue is popping up for CouchbaseLite 2.5.0 on a device which supports armeabi-v7a and armeabi. It’s also giving out an error
Hi, do we have the fix for the specified issue?