- Home /
SQLite problem after updating to 2018.2.17f1
I have always used SQLite without a problem on my Android games.
Today I updated to 2018.2.17f1 (was using 2018.2.16f1 without a problem), and now my game wont build on Android, giving me a conflict between my project's System.Data.DLL and MonoBleedingEdge's System.Data.DLL.
Anyone knows why? What changed that may have caused this?
Here is the error message during build:
error CS1703: An assembly `System.Data' with the same identity has already been imported. Consider removing one of the references Assets/Plugins/sqlite/System.Data.dll (Location of the symbol related to previous error) /Applications/Unity/Unity.app/Contents/$$anonymous$$onoBleedingEdge/lib/mono/4.7.1-api/System.Data.dll (Location of the symbol related to previous error)
Well, since I really need to build my game I am reverting back to 2018.2.16f1, but something is off on this .17 version. Beware if you use SQLite
Answer by mkneib · Dec 03, 2018 at 02:25 PM
i had the same problem in several windows standalone projects.
i deleted a System.Data.dll in the folder Assets/Plugins/SQLite/ in my project. that solved it for me.
Your answer
Follow this Question
Related Questions
Linear Color Space washed out in android URP build. 2 Answers
Always ask to updating android SDK 4 Answers
One Signal dependecies issue 0 Answers
CommandInvokationFailure: Failed to re-package resources. 2 Answers