Regression: Newly-fetched posts treated as "local" posts

[AngeloStavrow]

This regression seems to be related to the changes made in either #250 or #251 for the 1.0.16 release on iOS.

Two scenarios:

• Install build 703 fresh on a device/Simulator and log in to an existing account. All posts are fetched from the server, but are marked as "local" in the app.
• Update to build 703 from an earlier version on a device/Simulator that was already logged in to an existing account. Create a new post on the web, then tap the refresh button on the app. The new post is fetched and marked as "local" in the app, despite all other previous posts are otherwise marked correctly.

This could be a UI bug where the badge is wrong. The only option available for the post is to publish, and trying to do so doesn't properly update the post status (even though the post is successfully published):

However, on logging out, it doesn't look like the app sees these marked-local posts to be actually local, or it would warn the user about them being deleted:

This is strange, because the actual status is marked as 0 (i.e., "local") in the Core Data store. 🤔