<@U04616UPXV4> did you manage to fix it? I have th...
# room
g
@Cristhian Escobar did you manage to fix it? I have the exact same problem. The code is being created in the build folder:
Copy code
internal fun KClass<MagicDatabase>.instantiateImpl(): MagicDatabase =
    core.database.MagicDatabase_Impl()
But i cannot reference it 🤷
c
I haven't had time to look into the issue anymore, but I did leave the branch up to continue the investigation. I am not sure of the class is being generated for me at all.
Yup I am seeing the same thing. Are you able to build android just fine?
The code that is generated is supposed to be used for the iOS implementation but the generated code that you mentioned above is under android generated files
g
Android has no problem (but i cannot run it until all targets have their DI setup right), only iOS targets. Each target has this code generated correctly. My problem is that for some reason the files are not “seen” and thus i cannot import them.
instantiateImpl()
is internal but for instance
MagicDatabase_Impl()
is public, I should be able to call it
Well, I will use SQLDelight 🤷
c
Hold on there, I just heard word that the version coming up next week fixes this problem. I have currently use SQLDelight and it works wonders, however you need to be more careful when migrating users from version to version, that is why I wanted to move over to room. At the moment I have the implementation under a toggle. Hope the next version does actually fix this problem, will be waiting for it. I think the dev version is available for test, and it includes the fix.
👍 1
g
I have used both, and I like both. This is the first time using Room in KMP but it's for a POC project so no big deal. But if I had to use one for production I still would be prefering SQLDelight since it is more mature in the KMP world.
Curious about your migration experience, never had to handle such situations. Square says is "automatic" were Room is not. Can you share your thoughts on this? Thanks for all your responses Christian 😉