Closed devssun closed 4 months ago
➤ PM Bot commented:
Jira ticket: RCOCOA-2372
Can you try to explicitly specify the objectTypes
in your realm config? That way you can avoid the costly reflection that's needed to build the default schema.
I already defined. This error does not occur in projects where Tuist is not applied. Could settings in the build settings possibly affect this?
public class History: Object {
@objc public dynamic var _id = ObjectId.generate()
@objc public dynamic var id: String?
@objc public dynamic var date: Date = Date()
@objc public dynamic var read: Bool = false
@objc public dynamic var dataString: String?
}
What do you mean by "I already defined"? The stacktrace seems to indicate that no objectTypes
was specified on the realm configuration, which is why we're trying to use reflection to discover the default schema.
oops I'm sorry. I misunderstand and fix this issue. thank you.
How frequently does the bug occur?
Always
Description
My Test Information iPhone 11, iOS 17.5.1
In our application, we save push information at notification service extension(NSE). I made project using Tuist. After apply Tuist, RealmSwift occured error when I called
tryRealm()
from NSE.the error is
Thread 2: EXC_RESOURCE (RESOURCE_TYPE_MEMORY: high watermark memory limit exceeded) (limit=24 MB)
stacktrace
I don't understand what happened. please help me.
Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
No response
Version
10.7.4
What Atlas Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
iOS 17.5.1
Build environment
Xcode version: 15.2 Dependency manager and version: SPM