This would happen if you do a new build after adding a module, made a change to a strings.xml file or something else caused the app to be outdated, needing a fresh build.
1. Use a fairly big Alloy app, e.g.: git clone https://github.com/aaronksaunders/alloy_fugitive.git
2. Build it (in Simulator) with LiveView: ti build -p ios --liveview
3. Open a new terminal window
4. Build it with or without LiveView: ti build -p ios --liveview
5. Notice the existing app in Simulator reloading constantly.
6. Notice the console showing the Alloy compile of our second build triggering a lot of reloads (see attachment).
Killing the active session in our first terminal window doesn't help. This doesn't kill the actual LiveView server. Killing the iOS Simulator or the app running in it does work, but it would be good to not require this extra step and prevent users to see all the flickering and console horror going on.