Cristian

^ that. What I usually do, and it might not work for all use cases, is to always start the server with a random port. I can do this because...

Try excluding the model classes from the proguard obfuscation.

Did you also exclude the classes you are persisting?

Duped of https://github.com/ollama/ollama/issues/1669

This one is weird. What multidex does is just spliting your dex file in multiple dex files, but it should not mess with your resources. Can you confirm that once...

Don't trust R.java since it's automatically generated. Make sure that the resource (follow the stacktrace) which is being loaded exists in the resources of the APK.

It's perfectly normal that Resources.java shows you incoherent stuff (sad but true). You should be looking at `Crouton.java:817` instead.

ROFLMAO! Ok... so if you want to contribute with the community and/or help me help you, I'd create an example problem were I can reproduce and debug this.

Actually, I just updated the README encouraging all people to witch to buildToolsVersion 21.1.0, since multidexing is officially supported now. So, you might try using that and keep the conversation...

Make sure there's no redis process running, bound to the same port. Also, make sure to kill the redis processes once you are done with them. See https://github.com/kstyrc/embedded-redis/issues/51