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
I'm getting a lot of crashes in [LMAlertView show] with the following message:
A view can only be associated with at most one view controller at a time! View < UIView: 0x14e94050; frame = (0 0; 320 480); autoresize = W+H; layer = < CALayer: 0x14ef3880 > > is associated with < LMEmbeddedViewController: 0x14ee1950 >. Clear this association before associating this view with < LMEmbeddedViewController: 0x14dc7890 >.
-[LMAlertView show]
in LMAlertView.m on Line 442
is there a fix for this?
thanks.
The text was updated successfully, but these errors were encountered:
I'm in no way an expert in LMAlertView, but my guess from the message is
that a previous use of LMAlertView is still hanging around. Did you define
your instance of LMAlertView as global to your view controllers class, as
in through a property? Maybe before you alloc another instance you could
put a breakpoint and check if it is still allocated?
I'm getting a lot of crashes in [LMAlertView show] with the following
message:
A view can only be associated with at most one view controller at a time!
View > is associated with . Clear this association before associating this
view with .
[LMAlertView show]
in LMAlertView.m on Line 442
is there a fix for this?
thanks.
Reply to this email directly or view it on GitHubhttps://github.com//issues/38
.
I'm getting a lot of crashes in [LMAlertView show] with the following message:
A view can only be associated with at most one view controller at a time! View < UIView: 0x14e94050; frame = (0 0; 320 480); autoresize = W+H; layer = < CALayer: 0x14ef3880 > > is associated with < LMEmbeddedViewController: 0x14ee1950 >. Clear this association before associating this view with < LMEmbeddedViewController: 0x14dc7890 >.
-[LMAlertView show]
in LMAlertView.m on Line 442
is there a fix for this?
thanks.
The text was updated successfully, but these errors were encountered: