Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Notice: Food log ids have exceeded max signed 32 bit integer

The ids of food logs have now exceeded the maximum signed 32 bit integer (2,147,483,647) and are expected to exceed the maximum unsigned 32 bit integer (4,294,967,295) in the next quarter. Application developers are advised to accept 64 bit unsigned integers for food logs.

 

Affected endpoints: Log Food, Get Food Logs, Delete Food Log

 

 

 

Best Answer
0 Votes
5 REPLIES 5
I don't know if this is related, but I can't add items to my food/calorie log today, all of a sudden. Here's a logcat. I add the item and it appears temporarily, and then blinks away. It also doesn't contribute to the sum shown on the dashboard. This is rather frustrating since the UI is a clunky piece of junk to begin with, and the free app I was using a few days ago was much better.

---- Dec 28, 2014 10:20:50 AM ----

12-28 10:20:09.678 969 969 W PackageManager: Failure retrieving resources for com.fitbit.FitbitMobile: Resource ID #0x0

12-28 10:20:11.741 696 720 I BroadcastQueue: Deliver non-order [BG] BR@a0684b4 BF{2e4d9c6 u0 RL{28c053a1 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:11.761 696 1324 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21050: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:11.941 696 727 I WindowManager: SURFACE SHOW layer=21045: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:13.373 696 3096 I ActivityManager: START u0 {cmp=com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_ (has extras)} from uid 10242 on display 0

12-28 10:20:13.459 696 720 I BroadcastQueue: Deliver non-order [BG] BR@13cb4680 BF{2188dbb2 u0 RL{18c4b9bd 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:13.491 696 3260 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21055: Window{17a500fe u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:13.612 696 727 I ActivityManager: Displayed com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_: +204ms

12-28 10:20:13.617 696 727 I WindowManager: SURFACE SHOW layer=22050: Window{17a500fe u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:13.861 696 727 I WindowManager: SURFACE HIDE: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_ EXITING}

12-28 10:20:13.864 696 727 I WindowManager: SURFACE DESTROY: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:17.150 696 1339 I ActivityManager: START u0 {cmp=com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity (has extras)} from uid 10242 on display 0

12-28 10:20:17.239 696 720 I BroadcastQueue: Deliver non-order [BG] BR@2466016b BF{12a013e5 u0 RL{e5fb6dc 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:17.272 696 1233 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21060: Window{1a430961 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:17.354 696 711 I WindowManager: SURFACE CREATE pid=13079 format=-2 layer=21065: Window{1e614947 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:17.479 696 727 I ActivityManager: Displayed com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity: +303ms

12-28 10:20:17.483 696 727 I WindowManager: SURFACE SHOW layer=22055: Window{1a430961 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:17.483 696 727 I WindowManager: SURFACE SHOW layer=22065: Window{1e614947 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:17.719 696 727 I WindowManager: SURFACE HIDE: Window{17a500fe u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_ EXITING}

12-28 10:20:17.720 696 727 I WindowManager: SURFACE HIDE: Window{1e614947 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:17.722 696 727 I WindowManager: SURFACE DESTROY: Window{1e614947 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:17.724 696 727 I WindowManager: SURFACE DESTROY: Window{17a500fe u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:18.070 13079 13131 I FitbitAnalytics: updating context

12-28 10:20:18.078 13079 13131 I FitbitAnalytics: updating context

12-28 10:20:18.078 13079 13131 I FitbitAnalytics: updating context

12-28 10:20:18.078 13079 13131 I FitbitAnalytics: updating context

12-28 10:20:18.505 696 1096 I ActivityManager: START u0 {flg=0x4000000 cmp=com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_ (has extras)} from uid 10242 on display 0

12-28 10:20:18.560 696 720 I BroadcastQueue: Deliver non-order [BG] BR@328968c5 BF{1bc2112f u0 RL{32c5930e 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:18.576 696 919 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21045: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:18.670 696 727 I WindowManager: SURFACE SHOW layer=21045: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:18.943 696 727 I WindowManager: SURFACE HIDE: Window{1a430961 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:18.953 696 727 I WindowManager: SURFACE DESTROY: Window{1a430961 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:20.924 696 3260 I ActivityManager: START u0 {cmp=com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_ (has extras)} from uid 10242 on display 0

12-28 10:20:20.988 696 720 I BroadcastQueue: Deliver non-order [BG] BR@212bf817 BF{2f9047b1 u0 RL{f1c6a58 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:21.021 696 1233 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21055: Window{eb0aded u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:21.129 696 727 I ActivityManager: Displayed com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_: +177ms

12-28 10:20:21.132 696 727 I WindowManager: SURFACE SHOW layer=22050: Window{eb0aded u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:21.377 696 727 I WindowManager: SURFACE HIDE: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_ EXITING}

12-28 10:20:21.381 696 727 I WindowManager: SURFACE DESTROY: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:24.849 696 5665 I ActivityManager: START u0 {cmp=com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity (has extras)} from uid 10242 on display 0

12-28 10:20:24.927 696 720 I BroadcastQueue: Deliver non-order [BG] BR@1ef3faa3 BF{1aa5ec5d u0 RL{151c4634 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:25.001 696 711 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21060: Window{2bd9f159 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:25.070 696 1263 I WindowManager: SURFACE CREATE pid=13079 format=-2 layer=21065: Window{17c19dff u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:25.146 696 727 I WindowManager: SURFACE SHOW layer=22055: Window{2bd9f159 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:25.146 696 727 I WindowManager: SURFACE SHOW layer=22065: Window{17c19dff u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:25.158 696 727 I ActivityManager: Displayed com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity: +285ms

12-28 10:20:25.387 696 727 I WindowManager: SURFACE HIDE: Window{eb0aded u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_ EXITING}

12-28 10:20:25.387 696 727 I WindowManager: SURFACE HIDE: Window{17c19dff u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:25.389 696 727 I WindowManager: SURFACE DESTROY: Window{17c19dff u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:25.389 696 727 I WindowManager: SURFACE DESTROY: Window{eb0aded u0 com.fitbit.FitbitMobile/com.fitbit.ui.choose.food.ChooseFoodActivity_}

12-28 10:20:34.896 696 1339 I ActivityManager: START u0 {flg=0x4000000 cmp=com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_ (has extras)} from uid 10242 on display 0

12-28 10:20:34.948 696 720 I BroadcastQueue: Deliver non-order [BG] BR@1d2313d7 BF{c2d8d71 u0 RL{1ff02f18 13079 com.fitbit.FitbitMobile/10242/u0}}

12-28 10:20:34.962 696 1233 I WindowManager: SURFACE CREATE pid=13079 format=-1 layer=21045: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:35.046 696 727 I WindowManager: SURFACE SHOW layer=21045: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

12-28 10:20:35.326 696 727 I WindowManager: SURFACE HIDE: Window{2bd9f159 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity EXITING}

12-28 10:20:35.342 696 727 I WindowManager: SURFACE DESTROY: Window{2bd9f159 u0 com.fitbit.FitbitMobile/com.fitbit.food.ui.LogFoodActivity}

12-28 10:20:35.415 13079 13139 W SyncManager(31264): at com.fitbit.FitbitMobile.MultiThreadedIntentService$a.handleMessage(SourceFile:71)

12-28 10:20:37.823 969 969 W PackageManager: Failure retrieving resources for com.fitbit.FitbitMobile: Resource ID #0x0

12-28 10:20:37.946 969 969 W PackageManager: Failure retrieving resources for com.fitbit.FitbitMobile: Resource ID #0x0

12-28 10:20:38.414 696 727 I WindowManager: SURFACE HIDE: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_ EXITING}

12-28 10:20:38.420 696 727 I WindowManager: SURFACE DESTROY: Window{21df0918 u0 com.fitbit.FitbitMobile/com.fitbit.home.ui.DetailActivity_}

---- Dec 28, 2014 10:20:50 AM ----

I'll also add some feature requests to food logging,since we're on the subject. "Add Another", "Edit Item: name" in place being that there is no way to do so after having created one. NOTE THAT YOU SHOULD ONLY CONSIDER THESE ADDITIONS AFTER THE BASIC FUNCTIONALITY ISN'T FLAWED.
Best Answer
0 Votes
Additionally a workaround seems to be to add the food from the "My Foods" tab instead of the "Common Foods" tab. God knows why.
Best Answer
0 Votes

Hi Wowie,

 

Where are these logs from? This indeed may be related and we're trying to push out updates to all of our mobile apps.

 


@Wowie wrote:
This is rather frustrating since the UI is a clunky piece of junk to begin with

Ya know, we're real people over here. I'm sorry that you're upset, but please keep your criticism constructive.

Best Answer
0 Votes

The Logcat isn't related, because it happens without the flaw in question expressing itself. This is not an external application's log, if that's what you're interested in. 

 

The line that may be of interest however is near "PackageManager: Failure retrieving resources..." It's a Warning level error. There's strange user-facing issues that are being discussed: https://community.fitbit.com/t5/Android-App/App-not-showing-accurate-info/td-p/580210

 

To be more clear, logging calories is fairly time consuming. The search box isn't very responsive, and it's often difficult to find the food I'm looking for (which is incredible given the quantity of entries). Back a step, the lists (which are effectively duplicates) of "Most Recent" and "Most Often" is completely redundant, and makes the list on that page effectively useless, since scrolling all the way to the top or bottom means basically nothing. By the way, showing the "Most Recent" item first on the list is almost in conflict with your construct of having the users type in the portion that they ate in units of oz / eclairs / etc. And really, every good UI design since the 2000's puts either a very condensed "Most Often," the user's "Favorites", or both front and center. Back another step up, putting the search button behind the "+" button is completely redundant. Really wouldn't it be pretty easy to put a searchbox there, and spare us waiting on whatever database pinging or confirmations the app decides to do at that point? Pane-switching is fairly slow on every cell phone UI. And seriously, I've got a phone that's like 2 years old, and every time I click that "+" button, the screen flicks "No common foods yet."

 

1.) Add an optimized search box to the calories log.

2.) Change "Common Foods, My Foods" to "My Foods, Most Recent, Most Often" or something like that, and probably make it user-customizable.

3.) Fix the search box in the first place. Why is it that when I type in "Mcd" I get a full page of results where that isn't even a substring of any of the results, and one local result that I had to created previously? That's madness!!

Best Answer
0 Votes

Good, still difficult for my tastes though since macros are only found on the web anyway. Good work though. Hopefully the new found quality doesn't overwhelm your servers and inconvenience many lol. 

 

E: I love it! 

Best Answer
0 Votes