@JuanFitbit While tagging your request for information as Best Answer allows everyone to see your request, it also makes it appear to your customers and to your management, that the problem is solved, which it is clearly not. A bit deceptive on your part.
Also, given the problem occurs as stated by many of the posters on this forum (simply adding food multiple times to today's food consumption, the "happy path" of the food logging functionality), there is no reason to delay the start of debugging while gathering information.
Clearly your test engineering team did not prepare an adequate test case, which would select foods and add multiple items to the list for several meals, then check to see if they appear in the food list for the day, and the daily nutrition info was computed correctly. This ideally would be repeated for each entry type (+ from recent, + from frequent, + from search (a food not previously used in the test), + from custom, and from bar-code scan, and per another poster, from the API. Automated UI test tools for Android and iOS can avoid having to have humans manually perform the test. But your test team knows that.
