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
When sending a track, we don't know if an error occurs, it goes to reportInternalError(). Adding an optional method with a result would be welcome.
Why? We are using track to send user feedback. We like the freedom of Segment to push to any destination. Even if we persist the data in the app, we are still guessing if the track event succeeded.
The text was updated successfully, but these errors were encountered:
Events are buffered, and track is an event. If you want to see if the events make it to Segment, call flush() with a completion block and you'll know if it was successful or not. The use-case you describe is pretty non-standard and not really what Segment is for. There's other services that specialize in what it sounds like you're doing.
When sending a track, we don't know if an error occurs, it goes to reportInternalError(). Adding an optional method with a result would be welcome.
Why? We are using track to send user feedback. We like the freedom of Segment to push to any destination. Even if we persist the data in the app, we are still guessing if the track event succeeded.
The text was updated successfully, but these errors were encountered: