predrag karic
07/06/2021, 10:00 AMEXC_BAD_ACCESS
when calling some use case. We are using clean arch and everything from domain layer is written in kotlin. We are manually freezing use case objects exposed to iOS.
I noticed this in log
/Users/teamcity/buildAgent/work/f01984a9f5203417/runtime/src/main/cpp/Memory.cpp:1581: runtime assert: add ref for reclaimed object
and this is in Xcode:
Thread 47: EXC_BAD_ACCESS (code=1, address=0x4aa017e2280)
Every use case have a callback and the only difference with other calls to common (kotlin) code is that in this situation I am calling another use case from that callback… not sure if that can be a root cause of this issue… Really appreciate if someone can help me how to figure out why is this happening and how to resolve it. Thx in advanceexc_bad_access
didn’t point me in right direction