Fix device management lifecycle APPS message processing #2780
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed the processing of the APP message from the DeviceLifecycleService.
Related Issue
None
Description of the solution adopted
On the processing of the APPS message from the service, the Device info update was missing and only the lastEvent was updated.
Now the service stores correctly updated device infos from the APPS message.
Screenshots
None
Any side note on the changes made
I've also performed a small improvement of the code