Closed passsy closed 6 years ago
The problem could also be a result of the compileOnly
dependency of appcompat
. We could try to use api
.
compileOnly is the wrong way, you are right. But using api is also wrong since we don't share any AppCompat APIs. We should go with implement in anyway...
On Wed, Jul 4, 2018, 6:18 PM Pascal Welsch notifications@github.com wrote:
The problem could also be a result of the compileOnly dependency of appcompat https://github.com/grandcentrix/ThirtyInch/blob/f125b846d733a10cbb74773a08ca625b204c8478/thirtyinch/build.gradle#L35. We could try to use api.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/grandcentrix/ThirtyInch/issues/148#issuecomment-402520243, or mute the thread https://github.com/notifications/unsubscribe-auth/AJwYe5PIDf-fAec9eOhY9WtTAgzniyU3ks5uDOrVgaJpZM4VC0SD .
I think api
is correct because we are extending Fragment
and Activity
and therefore they are part of our public API.
But it turns out AndroidX works with ThirtyInch
(except for #149) and we don't have issues due to the provided
. I made a mistake when setting it up resulting in this strange crash.
fixed in 0.9.0
I tried to convert a project to AndroidX and failed. Most problems are caused because the
TiActivity
extendsandroid.support.v7.app.AppCompatActivity
and not the newandroidx.appcompat.app.AppCompatActivity
resulting in crashes like this:It could be a bug of the
android.enableJetifier
which is not able to convert the packages correctly.Anyhow we should come up with a solution and think about the right time to move to AndroidX.