-
Notifications
You must be signed in to change notification settings - Fork 598
-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlowManager not initialized while init method called. #1300
Comments
I found the solution!!! it was all about proguard rules. Please, write about it on the main page. It should be more noticable. |
It has its own section on the documentation website....https://agrosner.gitbooks.io/dbflow/content/proguard.html |
I was receiving the throwable The global database holder is not initialized. Ensure you call FlowManager.init() before accessing the database. I added this line
Because I'm using Kotlin I switched |
I am having the same issue: My database: My table: I added the following to proguard: When I try to save any object, it gives me: |
I'm encountering this issue also. LE: It seems I was misusing some proguard files and I wasn't loading the correct rules for this library. |
I was having the same issue, using Kotlin. Finally discovered the reason, and it was due to the annotation processor. I didn't add the
in my It works fine now, if someone wants to get the code, it is here, (note the |
I did everything according to the guide: the libraries, the application onCreate method. I've got this error when running the app:
DBFlow:4.0.2
Gradle:2.3.2
buildToolsVersion:25.0.3
Application class is added to manifest.
The text was updated successfully, but these errors were encountered: