realm-swift: Strange log message: "N5realm10LogicErrorE: Bad version number"
Seeing the following in our logs randomly
uncaught exception in notifier thread: N5realm10LogicErrorE: Bad version number
Unfortunately, don’t have any specific steps to reproduce. Doesn’t seem to be causing any issues but thought I would let you guys know
Realm version: 2.1.1
Xcode version: 8.2 beta 2
iOS/OSX version: 10.1
Dependency manager + version: Carthage 18.1
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 3
- Comments: 25 (11 by maintainers)
Ok, I came across this issue as I was trying to figure out why my Realm file was ballooning to over a gigabyte sometimes.
Here is where I am at:
Realmas a dependency in a Networking framework that I am writing in Swift.Realmto interfere with my frameworks’ usersRealmso I make sure I make and configure my own realm file.I was running into these problems:
realmversions and when I passeddeleteRealmIfMigrationNeeded: trueas a parameter for experimentation.deleteRealmIfMigrationNeeded: trueas a configuration parameter. Since then the error always gets thrown.Here is the stack trace from that exception:
I can’t share my code where this error is currently happening. I did make an example project that uses my Configuration object to make and manage my the
Realm.That project is clonable/downloadable here.
Just run good old
pod installI was not able to get this demo project to throw the “N5realm10LogicErrorE: Bad version number” error. If I do, I will post an edit with my steps.
This project does demonstrate the ballooning of my
Realmfile especially when the version is ticked over and thedeleteRealmIfMigrationNeeded: trueis set.Check out my demo app and let me know if I am using
Realmwrong in any way, I would really appreciate any feedback as I love the software but am concerned about these little/big issues I keep running into.Also, if my ballooning issue warrants its own issue let me know and I will move it/file it appropriately. Hopefully, I am just miss using something or not understanding this.
Hullo Tim and team, I’m seeing this intermittently with the
realm.refresh()in the following code, running Realm 2.1.2 on the simulator:uncaught exception in notifier thread: N5realm10LogicErrorE: Bad version numberIt seems to happen more often if I take out the NSLog statements…
I added the
refresh()because these image URLs are often being set while my UIScrollView is blocking the main runloop. Not sure whether that’s a good solution but it’s introduced this new issue. 😃That code is running on thread 1. The exception is occurring in The
RLMRealm notification listenerthread (thread 8 in my test) with this backtraceHere the exception stack using
All exceptionsbreakpoint:As said in #4428, we don’t have the steps to reproduce it, but once that exception has been fired the interface will freeze (dead lock in the
writeTransaction)I’m having the same issue when launching my app.
uncaught exception in notifier thread: N5realm10LogicErrorE: Bad version numberNo crash and everything is working fine. It seems to only appear once in the log.