I’m also noticing a lot of bugs/problems with hot code push and running iso-device. Same issues. I typically kill simulator, stop the app in Xcode and hit build again (I keep meteor run iso-device running and don’t have to restart that). Sometimes I need to delete the app in simulator, and rebuild from Xcode.
I noticed on the link just posted this:
If you push a malformed version of your app to the clients, your clients can get stuck in a state where they cannot download a newer (fixed) version. In that case your best bet is to either push a new version through App Store or Play Store, or tell your users to clean the application data (that’s where the malformed version of the app is stored).
I’m wondering if this is possibly related to the post I just made at iOS app randomly not loading
However, I haven’t pushed a “malformed version” of the app to clients. The code pushed up was deployed and verified successful. It almost seems that hot code push potentially triggers the app to update before all of the code updates are completely deployed - could this possibly be the case?
Mark