@Manoj Technically, yes. #2316 is the same issue.
However, in my opinion, there is an additional aspect: the issue in the bug tracker refers to an application installed from a non-native store (F-Droid). You could claim that in the case of non-native stores, it is the users’ task to check that all prerequisites are fulfilled before updating an application.
In my case, however, it was the native Apps store which lead to an incompatible update. Ideally, there’d be a mechanism which allows for inhibiting inclusion of incompatible updates in the store. For sure, you cannot always check compatibility for each of the apps, but regarding the CCTG app, the incompatibility had apparently already been spotted a while before its inclusion in Apps.
Cheers
Ingolf