We encountered the problem that we needed to start new visit while the tracker was already initialized, so the newVisit parameter in the initialize method wasn't sufficient anymore.
The solution is now to add a newVisit parameter to (nearly) every track... method to make that action the start of a new visit. Out of convenience for most users (which I imagine to only ever start a new visit on app launch), the newVisit in initialize is still there.
The additional documentation (hopefully) decribes the relationship between the initialize and the track...newVisit parameters.
We encountered the problem that we needed to start new visit while the tracker was already initialized, so the
newVisitparameter in theinitializemethod wasn't sufficient anymore.The solution is now to add a
newVisitparameter to (nearly) everytrack...method to make that action the start of a new visit. Out of convenience for most users (which I imagine to only ever start a new visit on app launch), thenewVisitininitializeis still there.The additional documentation (hopefully) decribes the relationship between the
initializeand thetrack...newVisitparameters.