Looks like there is a difference between having an incorrect session and an inactive / expired session. pydexcom was not catching the latter as a known exception. Will look into adding this to tests, but would have to wait until session expires to catch in test...
Looks like there is a difference between having an incorrect session and an inactive / expired session.
pydexcom
was not catching the latter as a known exception. Will look into adding this to tests, but would have to wait until session expires to catch in test...