-
Notifications
You must be signed in to change notification settings - Fork 168
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
'Assertion failed' - Fatal crash when initialising Realm #5707
Comments
Good call. I suspect this is the same issue that causes hot-reloads to crash (see realm/realm-dart#728). Could you try to use: final User currentUser = app.currentUser ?? await app.logIn(anonCredentials); |
Thanks for the quick response! Unfortunately, this change results in the same crash. |
Could you try running it with Dart 2.18+, ie. Flutter beta channel? |
The issue still persists with SDK version 2.18.0-271.4. The app ran fine the first time I ran it this morning. Subsequent runs suffer the same crash in the original post. |
@n-doton Thank you for trying it out with dart 2.18, but we believe it is an issue in |
Hi, @n-doton, yes I think this is a bug in realm-core. I think there's an exception integrating state from the server that's getting applied before the sync client is able to connect to the server and the logic for handling disconnects due to an error is not being called appropriately. If you turn on trace level logging in the sync client, you may be able to see what the error while applying state is. I'm working on a fix for how errors are handled while not yet connected and will keep you posted. |
@nielsenko After some trial and error, I managed to get the following in the console:
Please let me know if there is anything else I can do to help. |
Hmm.. it looks as if your are subscribed 6 times to the logger. Could you structure your code, so that the listen call is not called repeatedly? Also, could you increase the log level to Can you confirm that it dies immediately after:
or did you omit some trace? |
It was firing 6 times in my previous post, sorry about that! That was the last trace before the app exited. I'm unable to get the logger to log anymore after several attempts. The app exists with nothing in the stacktrace other than the stack in the original post. Please could you confirm that the logger in the correct place, as shown in this example?
Thanks in advance. Update: I got it to log again, the content is the exact same as my previous log. |
Hi, I'm guessing this fix will be available in the next release. Is it possible to get an ETA on when this might be live? Thanks in advance. |
We normally don't give ETAs, but the release of realm-core version 12.6.0 (which includes this fix) is tentatively scheduled for Monday. For you to benefit we need to roll a release of the Flutter SDK as well, which I guess will happen Wednesday. But remember, these are not promises, more like wishful thinking on a Friday afternoon. |
When initialising flexibleSync with a realm schema object, our app crashes unexpectedly with the following stacktrace:
We're initialising Realm using the following:
The crash seems to occur after the first run of the app from a restart or sleep cycle of my machine. No logs are displayed in the App Services logs section. I understand that the stacktrace instructed us to post the report on the
realm-core
issues page however, as realm-dart is in beta we are assuming it'll be an issue with this repository.Thanks in advance.
The text was updated successfully, but these errors were encountered: