Before 3.1 communication was less problematic for version mismatches between AAPS phone and watch app.
Currently, if the API is mismatching the Watch or Phone app crashes when it tries to deserialize an object. This should be prevented.
Suggestion to introduce an API version, which is communicated beginning of the connection. When it mismatches the API should be halted and the user informed. The alternative is a strict match on the matching AAPS version.
Al least the deserialization error should be caught without crashing the app.
Before 3.1 communication was less problematic for version mismatches between AAPS phone and watch app. Currently, if the API is mismatching the Watch or Phone app crashes when it tries to deserialize an object. This should be prevented.
Suggestion to introduce an API version, which is communicated beginning of the connection. When it mismatches the API should be halted and the user informed. The alternative is a strict match on the matching AAPS version.
Al least the deserialization error should be caught without crashing the app.