realm

I've got a Realm results change listener that isn't being triggered, here's the code: final RealmResults<LogEntry> entries = realm.where(LogEntry.class).findAll(); entries.addChangeListener(new RealmChangeListener<RealmResults<LogEntry>>() { @Override public void onChange(RealmResults<LogEntry> results) { Log.v("Testing", "The size is: " + results.size()); } }); There is definitely new stuff being added, I have a log on the realm insertion printing out the new size of the table, yet for some reason the change listener does nothing? Am I missing something here, it seems identical to the docs.

At the top of my UITableViewController is the following: let queue = DispatchQueue(label: "background") When a task is deleted, the following executes: self.queue.async { autoreleasepool { let realm = try! Realm() realm.beginWrite() realm.delete(task) do { try realm.commitWrite() } catch let error { self.presentError() } } } And then I receive the error terminating with uncaught exception of type realm::IncorrectThreadException: Realm accessed from incorrect thread. How could I fix this? Samantha It seems like the write is happening on a different thread than the object was originally accessed

I'm using Alamofire, Objectmapper, Realm and everything is working beside one thing: I can't map nested objects. class Voting: Object, Mappable { dynamic var votingID: String = "" dynamic var question: String = "" var votingOptions = List<VotingOption>() required convenience init?(_ map: Map) { self.init() } func mapping(map: Map) { votingID <- map["id"] question <- map["question"] votingOptions <- map["votingOptions"] } override class func primaryKey() -> String { return "votingID" } } class VotingOption: Object, Mappable{ dynamic var optionID: String = "" dynamic var text: String = ""

In my project I want to use one Realm Database with my iOS 10 application and my watchOs 3 application at the same time. So what I did was adding the frameworks to the embedded binaries for the three different targets. This happened to work very well but the watchKit extension doesn't seem to recognize the objects that I created within the iOS environment. How is it possible to have a shared Realm Database between those two devices? TiM Update: Okay, thanks to chrisamanse 's heads-up, I did some more research on this. It turns out that App Groups are no longer possible on watchOS 2. Watch apps

I am trying to get Realm to work in my project. I have Kotlin with version 1.2.51 and Instant Run disabled. In my project build.gradle file I added the following dependency: classpath "io.realm:realm-gradle-plugin:5.4.0" In my App build.gradle file I applied the Realm plugin as explained in the tutorial: apply plugin: 'com.android.application' apply plugin: 'kotlin-android' apply plugin: 'kotlin-android-extensions' apply plugin: 'kotlin-kapt' apply plugin: 'realm-android' When I am trying to build the project, I get the following error: org.gradle.api.ProjectConfigurationException: A problem

I have a realm object that is created in my activity. I need to be able to access this object within a service that I created. However I'm getting the error when creating the Realm object within the service mRealm = Realm.getInstance(getApplicationContext()); java.lang.IllegalStateException: Realm access from incorrect thread. Realm objects can only be accessed on the thread they were created Now I understand this means that because the realm object was created on my activity, I cannot access it from a background thread. However, I'm not finding an easy way around this other than creating my

I'm new to Realm, I'm wondering whether it's good practice to just have one Realm instance in Application object, use it across all cases needed in the app, and only close it in onDestroy of the Application class. Thanks There is nothing inherently wrong with keeping the Realm on the UI thread open and not closing it (note there is no OnDestroy on Application ) However you should keep the following in mind: 1) Realm can handle the process getting killed just fine, which means that forgetting to close Realm is not dangerous to your data. 2) Not closing Realm when the app goes in the background