You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issues we see with new target SDKs (#396 and #406) are likely related to the fact that we currenlty are forced to stick to gradle 6.9.1 which is rather old in meantime. Along with that we are also forced to stick to older versions of Android libaries.
E.g.:
androidx.fragment:fragment:1.5.7
androidx.recyclerview:recyclerview:1.3.0
androidx.appcompat:appcompat:1.6.1
com.google.android.material:material:1.6.0
One of the reasons for old gradle is the setup with copy of code of mina libraries and having changes to them in app project. It was done like this to be able to more easily update copy of that code. But updating them seems not to be relevant anymore and therefore it would make more sense now to apply changes directly to those projects.
See current gradle targets removeClassesBadForAndroid.
The text was updated successfully, but these errors were encountered:
The issues we see with new target SDKs (#396 and #406) are likely related to the fact that we currenlty are forced to stick to gradle 6.9.1 which is rather old in meantime. Along with that we are also forced to stick to older versions of Android libaries.
E.g.:
One of the reasons for old gradle is the setup with copy of code of mina libraries and having changes to them in app project. It was done like this to be able to more easily update copy of that code. But updating them seems not to be relevant anymore and therefore it would make more sense now to apply changes directly to those projects.
See current gradle targets
removeClassesBadForAndroid
.The text was updated successfully, but these errors were encountered: