addressign comments

src/libs/Navigation/AppNavigator/AuthScreens.js

@@ -131,7 +131,8 @@ class AuthScreens extends React.Component {
         });
 
         // If we are on this screen then we are "logged in", but the user might not have "just logged in". They could be reopening the app
-        // or returning from background. If so, we'll assume they have some app data already and we can call openApp(true) instead of openApp().
+        // or returning from background. If so, we'll assume they have some app data already and we can call
+        // reconnectApp(onyxUpdatesLastUpdateID) instead of openApp().
         // Note: If a Guide has enabled the memory only key mode then we do want to run OpenApp as their app will not be rehydrated with
         // the correct state on refresh. They are explicitly opting out of storing data they would need (i.e. reports_) to take advantage of
         // the optimizations performed during ReconnectApp.

src/libs/actions/User.js

@@ -557,7 +557,7 @@ function subscribeToUserEvents() {
             // Not always we'll have the lastUpdateID and previousUpdateID properties in the pusher update
             // until we finish the migration to reliable updates. So let's check it before actually updating
             // the properties in Onyx
-            if ('lastUpdateID' in pushJSON && 'previousUpdateID' in pushJSON) {
+            if (pushJSON.lastUpdateID && pushJSON.previousUpdateID) {
                 console.debug('[OnyxUpdates] Received lastUpdateID from pusher', pushJSON.lastUpdateID);
                 console.debug('[OnyxUpdates] Received previousUpdateID from pusher', pushJSON.previousUpdateID);
                 // Store these values in Onyx to allow App.reconnectApp() to fetch incremental updates from the server when a previous session is being reconnected to.