You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using TURecipientsDisplayController and we believe there may be a retain cycle. The property contentsController is strong and when the view controller creates and holds a TURecipientsDisplayController, it never gets deallocated. I was unable to find a reason for the property to be strong, but I may have missed something.
I have experienced the same issue.
I had set up the recipient library as in the example, and a reference cycle with my View Controller was indeed created.
As a workaround, I broke the reference cycle in my controller by hand (because it is not pushing or presenting anything):
We are using TURecipientsDisplayController and we believe there may be a retain cycle. The property
contentsController
is strong and when the view controller creates and holds aTURecipientsDisplayController
, it never gets deallocated. I was unable to find a reason for the property to be strong, but I may have missed something.TURecipientsDisplayController.h (Line 58)
The text was updated successfully, but these errors were encountered: