This is a bug with how Fitbit’s OS handles installation. It should only affect the 1st app launch. It should work fine if you launch it again.
