Is there a non-painful way to migrate to AndroidX? I’m not sure wheteher Android Studio’s

Migrate to AndroidX

is broken in general or just in my project

I just realized that with the latest fragment-ktx updates, we can now have code like this

class MyFragment : Fragment(R.layout.my_fragment_layout)

. But how to initialized our binding (DataBinding) if we use this constructor approach?

Hello everyone, i am new to Kotlin, can anyone point me to the best Kotlin material for me to kick off with? thanks

hey does some one know this error? if I do gradlew assemble I get this, I have databinding enabled in gradle

> Task :myapp:kaptDebugKotlin FAILED
e: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException

Hello guys, I wanted to use moshi to parse object to json string, the example on the lib docs says smth like this along the lines in order to achieve that:

Moshi moshi = new Moshi.Builder().build();
JsonAdapter<BlackjackHand> jsonAdapter = moshi.adapter(BlackjackHand.class);

String json = jsonAdapter.toJson(blackjackHand);

and I've been thinking its a bit of a boiler plate to write it for each class, so I came up with the idea of this:

fun Any.toJson() = Moshi.Builder().build().adapter(Any::class.java).toJson(this)

this way I can simply call

AnyObj.toJson()

, but I wonder if there is any downside of such solution?

have you tried turning off obfuscation first? And check if you can see events when it is disabled?

Why it should not ?

value

is

nullable

Beware that things have changed recently about that and they fixed those issues only recently if you are still using Androidx 1.0 then it's probably why.

Hello, does anybody knows where this "Terminate Application" icon is in new Android Studio? I want to simulate process death

Hello to all. I have a question about the following dependencies:

implementation("org.jetbrains.kotlin:kotlin-stdlib")
implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8")
implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk7")

I recently read the we should use the first one on Android as the latter ones contain it and do not provide any value on Android and the last one also has features that are not supported yet on Android ( at least for

minSdkVersion: 21

) . Is that true? What are your suggestions?

Is there a Kotlin language feature that could reduce the verbosity of accessing views from our classes with Data Binding? According to this (https://android-review.googlesource.com/c/platform/frameworks/support/+/882241) kotlinx.android.synthetic is no longer recommended. And since I use the data binding library already I figured I’d remove all those imports and just use data binding to access the views. However I end up with a lot of calls such as

dataBinding.featureHostBottomNavigationViewFrame.featureHostCustomerAccountPointBalance.text = someNumber

. I don’t know too much about Kotlin yet however I’m curious if there’s some way I can simplify these calls to just

featureHostCustomerAccountPointBalance.text = someNumber

Anyone know the work around for ignoring a val in a `Parcelize`d data class so I can avoid bundling it? My only thought as of right now is to make a separate data class for

UINonBundledState

, but I'd rather just have the annotation working. It gives me this error when trying to use it like I have in the example:

@IgnoredOnParcel is inapplicable to properties declared in the primary constructor

Can anyone help me find a working open source app that uses square's sqldelight? I'm having trouble getting it to work in my project, and I learn best by example, but the toy sample projects I've found seem outdated and don't build

GSearchConfig.INSTANCE.getCONFIG()

-> how to get rid off the INSTANCE when accessing Kotlin class from Java

hi, i have a little problem, i try to use a viewPager with a tabLaout to display an infinite list of data grouped by date so that the title each tab is a date (a month). I know how to use the FragmentPagerAdapter to display a limited number of fragments, but for an infinite list, I learned that we must use the FragmentStatePagerAdapter but I do not know how to use it. Can someone help me please?

Looks like Transformations.map() does not update depending LiveData in any case. What am I doing wrong? This works

val contract: LiveData<Contract?> = MutableLiveData()
    val authState: LiveData<AuthState?> = MutableLiveData()
    init {
        contract.observeForever { contract ->
            (authState as MutableLiveData).value = when {
                tokenRepository.tokens.accessToken.isNullOrEmpty() -> AuthState.ANONYMOUS
                contract != null -> AuthState.LOGGED_IN_WITH_CONTRACT
                else -> AuthState.LOGGED_IN_WITHOUT_CONTRACT
            }.also { authState ->
                Timber.d("Refreshing auth state to $authState after contract live data update")
            }
        }
    }

But this doesn't

val contract: LiveData<Contract?> = MutableLiveData()
    val authState = Transformations.map(contract)
    {
        when {
            tokenRepository.tokens.accessToken.isNullOrEmpty() -> AuthState.ANONYMOUS
            contract != null -> AuthState.LOGGED_IN_WITH_CONTRACT
            else -> AuthState.LOGGED_IN_WITHOUT_CONTRACT
        }.also { authState ->
            Timber.d("Refreshing auth state to $authState after contract live data update")
        }
    }
    init {
        contract.observeForever { Timber.d("Updated contract value to ${it?.contract}")}
    }

I would expect the logs from the observer in init method be followed trom the Transformations observer always. But sometimes I get the init method's only (setting contract.value=null).

is there any option in Android Studio from which, we can customize the default imports ,so we don't have to add the kotlin synthetic library again and again in every activity file.

I’m building an app with minSdk 23 but also have kotlin compile options set to target jvm 1.8. I see now that sdk 23 does not support jvm 1.8, so I’m left with a choice between increasing minSdk to 24 or lowering compile target to 1.6. What are the obvious drawbacks of targeting 1.6 (for a kotlin-only app)? Anything else I should be considering?

java 1.8 comes with

java.time.datetime

Going back means either you need to build your own version of date manipulation or integrate with joda library

Which implementation should we use in gradle, jdk7 or jdk8?

implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"

Is there support for higher versions?

If it needs to be accessed from different Activities/Services/BroadcastRecievers I would move it to the Application object, then inject it all the way down. I like it better than making it an

object

.

What DSLs and whatnot do people like for doing programmatic layouts? Or do most people still like doing the xml layouts? Does anyone know how mature anko is? It hasn't had an update in a while.

I recently started testing the MVVM pattern in android and I've spent a lot of time trying to move the seekbar functionality to my viewmodel. The problem I'm having now is that I need to update more than one value when a MutableLiveData is set, and I'm getting a circular dependency problem. I'm not even sure if this is how you're supposed to do it, but I'm overriding setValue and postValue. seekBarProgress.value cannot be set because it's not initialized.

class AddJobViewModel() : ViewModel() {
    val minPrice = 20
    val maxPrice = 1000
    val step = 10
    var description: MutableLiveData<String> = MutableLiveData("")
    var displayPrice: MutableLiveData<String> = MutableLiveData(String.format("Price: %d Kr", minPrice))
    val seekBarMax: MutableLiveData<Int> = MutableLiveData((maxPrice - minPrice) / step)

    var currentPrice: MutableLiveData<Int>
    var seekBarProgress: MutableLiveData<Int>

    init {
        currentPrice = object: MutableLiveData<Int>(minPrice) {
            override fun setValue(value: Int?) {
                if (this.value == value) {
                    return
                }
                super.setValue(value)
                displayPrice.value = String.format("Price: %d Kr", value)
                seekBarProgress.value = value!! / step - minPrice
            }

            override fun postValue(value: Int?) {
                if (this.value == value) {
                    return
                }
                super.postValue(value)
                displayPrice.postValue(String.format("Price: %d Kr", value))
                seekBarProgress.postValue(value!! / step - minPrice)
            }
        }
        seekBarProgress = object: MutableLiveData<Int>(0) {
            override fun setValue(value: Int?) {
                if (this.value == value) {
                    return
                }
                super.setValue(value)
                currentPrice.value = minPrice + value!! * step
            }

            override fun postValue(value: Int?) {
                if (this.value == value) {
                    return
                }
                super.postValue(value)
                currentPrice.postValue(minPrice + value!! * step)
            }
        }

        currentPrice.value = 200
    }
}

What is the recommended way to turn wifi on/off while running Espresso tests?

Hello anyone of you have a "boilerplate" or a "skeleton" to use with a new project? that are divided by modules like

app

core

core-testing

features

(inside different features as a modules)? I'm about to start a new project and I want to have a "guide". Thank you guys 🙂

Anyone run into Proguard issues using Kotlinx-Serialization? Getting this error which is making me suspicious it's either an issue with Proguard or R8 (or, a serialization issue, which I don't think is actually happening)

j.b.u: Can't locate argument-less serializer for class e.b.b.d.a (Kotlin reflection is not available). For generic classes, such as lists, please provide serializer explicitly.

I thought it’d be fun to take a poll: In production one of my companies server team recently did a release where they broke the contract of an endpoint. One app immediately crashed after login with a JSON serialization exception, and another app caught the exception, ‘gracefully’ failing, showing a blank screen to the user after login. We found the issue and reverted the server changes quickly because we got alerts from crashlytics that we had a crash that an abnormal number of users experienced in a very small time frame. Use the ‘YES’ emote on this post if you think the application should crash, and use the ‘NO’ emote if you think the app should gracefully fail, with a blank screen, or perhaps a dialog or something. Feel free to explain why in the thread, or perhaps offer an alternative solution that you feel is better.

what should I use when I need to work with background in kotlin?

anyone knows an approximate date of jetpack compose release?