[Bug] - WORKAROUND IN PLACE | Attempting to push an update after a previous push fails

[Crash0v3r1de]

Web request when the fleet push to Balena does not return started = true.

Do not have a capture of the return that's failing currently but it looks like it does not actually add the update to the fleet from the return.

Fixes

• Lazy work around could be forcing app restart upon successful push.
• Correct fix would be to capture until the failed request and break down why it failed - this'll take a while.

https://github.com/Crash0v3r1de/BalenaNebraUpdater/blob/master/Program.cs#L54
^^ Line that fires with the incorrect request return ^^

[Crash0v3r1de]

Workaround Commit: d759b94
Keeping this open as the simple restart is the current work around. I want to get a good capture and reverse the second push web request's to see what changed and then replicate that in this project so it does not need to restart itself at all.

[Crash0v3r1de]

seems the restart code is working better than I thought. I'll keep it as a fix as it seems Balena API is also being quite stable over the last couple months.