-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Liammeier/fence 1220 flush replays in more sdk lifecycle methods ios #274
Liammeier/fence 1220 flush replays in more sdk lifecycle methods ios #274
Conversation
RadarSDK/RadarAPIClient.m
Outdated
[RadarSettings updateLastTrackedTime]; | ||
} | ||
|
||
[[RadarDelegateHolder sharedInstance] didFailWithStatus:status]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should just need the one didFailWithStatus
from above in if (status != RadarStatusSuccess)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch. we do need just one, but this is the one we should keep actually.
current behavior is that even if RadarStatusSuccess
, we fall through to [[RadarDelegateHolder sharedInstance] didFailWithStatus:status];
when calling /track/replay
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm is that current behavior intentional though? Seemed like that was the "Radar error received" logs even though no error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I actually figured out how to get toolkit working here while making this behave in a more standard manner. a44b46e
…app-opens-by-default CORE-292 log app opens by default
No description provided.