Unable to Create New, Edit Existing Foods/Meals/Recipes, Quick Add, Sync, and/or Login - Resolved

Our apologies for the trouble creating and managing food related items and data sync right now. We saw this issue arise around 10am PST on Friday, April 22nd.

Current symptoms include, but are not limited to the following:

• Web
• inability to create a new food item or edit an existing food item in our database
• inability to create or edit a My Meal, My Food, or Recipe
• inability to add to diary via the Quick Add feature
• inability to complete diary
• iOS/Android
• inability to create or edit Recipes
• recipes, foods, meals, and other account data not visible in app after a reinstall
• syncing trouble - members may experience issues with data sync.
• If members create new food, a meal, or use quick add on their account, these newly created items will be stored locally on their device, and will not sync to other platforms (like the website), until this issue is resolved.
• while the services that support syncing data to partners are not affected, the sync issues affecting the app are affecting data syncing from the app to our backend servers. This in turn may result in data not reaching linked partners (e.g. Fitbit, Garmin, etc) & vice versa.
• inability to complete diary
• inability to login - these members can still access their account via the website
• iOS - some members receiving a server error. this seems to manifest after experiencing a crash when editing/creating a recipe, or after one logs out or reinstalls the app. We released a fix to prevent users from getting into this state, but accounts already in this corrupt state prior to the fix who haven't yet logged out/reinstalled may still experience this issue.
• Android - some members receiving a ""Registration of new MyFitnessPal accounts is not available in your location" error when trying to log in, and their account may show as a local account.

There is no workaround at this time to get these food items created or edited. We do not recommend resintalling the app at this time, as it will not resolve the issues mentioned above, and may result in additional issues due to the trouble with sync.

Our team identified the cause Friday afternoon and worked through out Friday and Saturday to get the necessary migration work in place to address to start addressing the root cause. This migration has made a lot of progress throughout sunday and monday, and finished Tuesday afternoon. Our team spent Tuesday updating our services to support the database changes that have been made after the completion of the migration. We completed what we could that would have no additional user impact during the day when the majority of our members are online and logging. Tuesday evening, from roughly 8pm-12am PST, we upgraded the rest of the services, which resulted in MFP being mostly unavailable both in the apps and on the website during this window. We had one outlying update that caused a small subset of users to experience downtime symptoms until the update fully completed at 2:15am PST.

Now that this work from the downtime is completed, and the updates to our services have finished, members will still be experiencing the known symptoms in the bulleted list at the top of this article. Throughout today, our team is working on and planning to deploy the necessary code changes to start resolving these symptoms our members are experiencing. We anticipate to be doing this throughout the entire day Wednesday.

We will continue to update this article as more information becomes available. Please check back for further updates.