-
Notifications
You must be signed in to change notification settings - Fork 128
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
Could not begin read transaction (another read transaction is still active on this thread) #368
Comments
Moved to objectbox-dart repo as this is using Flutter. The underlying issue is that the transaction was not completed because it failed with a crash: "E/Box ( 9986): Storage error (code -30783)". This error is described as How does your WorkManager code look like? Does it maybe close the database when it finished all work? |
@rizkyagungramadhan Are you using multiple isolates? |
No, Im not closing the database either the WorkManager result error or success. |
I am having the same error when trying to open my flutter project with another flutter engine. The reads of object box (on this other flutter engine) throws this error. |
@gcostaapps Thanks, but what do you mean by "open my flutter project with another flutter engine"? Can you share more details about the project? |
New releases have added a Closing this then. Feel free to comment or create a new issue if this is not resolved. |
Hello thanks a lot for making my life easier with ObjectBox.
I faced a problem when I implemented ObjectBox using WorkManager in Flutter.
In the process there are transactions in the form of reads and writes to the database, when the read -> download from Api -> insert process has been completed I get an error "Could not begin read transaction (another read transaction is still active on this thread)" when I retry to read database in the application (the process of inserting into the database all successful).
But when the process in Work Manager is still running, everything works normally for me when I want to access the database directly in the application.
This is my stacktrace :
I am using
objectbox: ^1.3.0
Thank you, very happy if anyone can help me with this problem
The text was updated successfully, but these errors were encountered: