It's being reported that the first time an app is opened with checkAuthentication the lack of a device secret at first call causes a killswitch to fire.
Originally this was supposed to be handled by checking if the token was current, but that wasn't working. Now we're checking for the null.
It's being reported that the first time an app is opened with checkAuthentication the lack of a device secret at first call causes a killswitch to fire. Originally this was supposed to be handled by checking if the token was current, but that wasn't working. Now we're checking for the null.