Driver shows up Inactive on fleet exception report, but shows active in the portal. Why?

Unlike Android IOS does still reserve the right to kill background apps even for long standing background location apps like LifeSaver, but we employ the techniques to stay awake as long as possible.   So this could be one of those scenarios.

Sometimes by the time this issue comes in the user has already re-opened the app and resolved the problem.

If not then have the user fully ‘swipe close’ the LifeSaver app and reopen it.

Internal technical notes:

For fleet users user history is maintained for the user.   This history is a daily snapshot of the app user and can frequently show when a user dropped off ‘last access’ and when they reopened the app.    If this information is not accessible to you and needed talk to LifeSaver Development.