HSBuddy arm64 System.DllNotFoundException: e_sqlite3

[dev120v]

Hello,

I had HSBuddy working great under HS4 linux ubuntu on a laptop . I have since moved to a raspberry pi 4 running ubuntu mate

Only plugin that is failing to load is HSBuddy

I am getting the following error

ERROR] FATAL UNHANDLED EXCEPTION: Autofac.Core.DependencyResolutionException: An exception was thrown while activating λ:HSPI_HSBuddy.WebPages.IWebPage[] -> HSPI_HSBuddy.WebPages.FencesPage -> HSPI_HSBuddy.Clients.ClientManager -> HSPI_HSBuddy.Data.Database. ---> Autofac.Core.DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(HSPI_HSBuddy.Native.IHomeSeer)' on type 'Database'. ---> System.TypeInitializationException: The type initializer for 'SQLite.SQLiteConnection' threw an exception. ---> System.DllNotFoundException: e_sqlite3 assembly:<unknown assembly> type:<unknown type> membernull)


when i look at that error it has System.DllNotFoundException: e_sqlite3


not sure if this has anything to do with it but I am using arm64

sqlite3 and all the DLLs seem to be there except for the libsqlite3.so.0

Thanks

[dev120v]

### Found the issue ####

For anyone using arm64 you are going to want to change this file to have the following contents

File: SQLitePCLRaw.provider.e_sqlite3.dll.config


<configuration>
<dllmap os="linux" dll="e_sqlite3" target="/usr/lib/aarch64-linux-gnu/libsqlite3.so.0" />
</configuration>


HSBuddy is now working on 64 bit ubuntu mate on raspberry pi 4

[Sphinx918]

### Found the issue ####

For anyone using arm64 you are going to want to change this file to have the following contents

File: SQLitePCLRaw.provider.e_sqlite3.dll.config


<configuration>
<dllmap os="linux" dll="e_sqlite3" target="/usr/lib/aarch64-linux-gnu/libsqlite3.so.0" />
</configuration>


HSBuddy is now working on 64 bit ubuntu mate on raspberry pi 4

I Dont know what else to say, but a BIIIIIIIG THANK YOU!

Working now

[dev120v]

I Dont know what else to say, but a BIIIIIIIG THANK YOU!

Working now

glad I could help. the developer contacted me and a similar fix will be in the next version