hi , i need one help can anyone tell how to restrict specific characters in searchView

I’m currently organizing all my dependencies in a

Dependencies.kt

file in

buildSrc

. In this file i’ve declared my androidGradlePlugin dependency

const val androidGradlePlugin = "com.android.tools.build:gradle:7.0.0-alpha06"

These values are recognized in my module level build.gradle files but trying to add it to my project level build.gradle.kts file, the import is unresolved. Is it not possible for the project-level gradle file to pull these dependency strings from buildSrc?

project level build.gradle.kts

dependencies {
        classpath(Libs.androidGradlePlugin)
}

Does anyone have any idea why I wouldn’t be able to see logs from OkHttp’s

HttpLoggingInterceptor

on a signed release build? I’ve set debuggable to true, and tried on the emulator and 2 physical devices (OnePlus and Samsung) but no matter what I do I can’t see logs from it, I can see them fine on a debug build Here’s how the logger is being added:

val httpLoggingInterceptor = HttpLoggingInterceptor()
httpLoggingInterceptor.level = HttpLoggingInterceptor.Level.BODY
return OkHttpClient.Builder()
    .addInterceptor(httpLoggingInterceptor)
    .addInterceptor(headerInterceptor)
    .build()

This message was deleted.

My live app is having a crash with this class. I think it has to do with writing to sharedPreference using dataStore. But I need more light on this

I tried proguard optimization / obfuscation back in the day. I ended up getting some strange crashes, and they were really difficult to debug. I haven’t tried obfuscation with r8 yet. Is it worth trying it out? Is r8 better than proguard?

I'm trying to use a buildSrc dir to handle my deps but i keep having issues with gradle not finding my Dependencies.kt objects. I've got in my buildSrc

.
├── build
│  ├── libs
│  │  └── buildSrc.jar
│  ├── source-roots
│  │  └── buildSrc
│  │    └── source-roots.txt
│  └── tmp
│    └── jar
│      └── MANIFEST.MF
├── build.gradel.kts
└── src
  └── main
    └── java
      └── Dependencies.kt

In Dependencies.kt

object Versions {
    val kotlin = "1.2.21"
    const val ktLint = "0.40.0"
}

object Deps {
    const val androidGradlePlugin = "com.android.tools.build:gradle:7.0.0-alpha05"
    const val ktLint = "com.pinterest:ktlint:${Versions.ktLint}"

    object GoogleMaps {
        const val maps = "com.google.android.libraries.maps:maps:3.1.0-beta"
        const val mapsKtx = "com.google.maps.android:maps-v3-ktx:2.2.0"
    }
}

and in my app build.gradle

dependencies {

    implementation 'androidx.core:core-ktx:1.3.2'
    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'com.google.android.material:material:1.3.0'
    implementation "androidx.compose.ui:ui:$compose_version"
    implementation "androidx.compose.material:material:$compose_version"
    implementation "androidx.compose.ui:ui-tooling:$compose_version"
    implementation 'androidx.lifecycle:lifecycle-runtime-ktx:2.3.0'
    implementation Deps.GoogleMaps.maps
    implementation Deps.GoogleMaps.mapsKtx
    testImplementation 'junit:junit:4.+'
    androidTestImplementation 'androidx.test.ext:junit:1.1.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'
}

Android studio auto detects my Google maps objects but I get Build file

'/Users/jasoninbody/AndroidStudioProjects/FinAquaticRentals/app/build.gradle' line: 52A problem occurred evaluating project ':app'.
> Could not get unknown property 'Deps' for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Is there some special button in Android studio i need to hit? I can sync my gradle with out the implementation statements in my app gradle

Hello Is anyone facing an issue with dismissing the dialog with latest version of JetpackCompose Alpha-12 and kotlin v1.4.30

how can I fix this memory leak? :(((((( I have tried

binding = null

binding.recyclerview.adapter = null

adapter  = null

but the leak doesn't fix

does anyone have any suggestions on approaches on how to handle navigation for apps using both phone and tablet layouts?

test

Hi Guys, do you prepare creating another activity for login and registration on navigation components

is there easy way to create a 2x2 grid layout in which am showing 4 video tiles dynamically? There can be only one video, in that case it should take up the whole screen, in case of 2 it should divide the layout into 2 equal parts and so on. Also I need to take care of aspect ratio as video coming from 16:9 camera will be 16:9 and from mobile it can be 3:4 or 4:3 depending on orientation. If you have any suggestion please let me know.

package com.view9.legalremit.ui.login

import androidx.test.core.app.ActivityScenario
import androidx.test.espresso.Espresso.onView
import androidx.test.espresso.assertion.ViewAssertions.matches
import androidx.test.espresso.matcher.ViewMatchers.isDisplayed
import androidx.test.espresso.matcher.ViewMatchers.withId
import androidx.test.ext.junit.runners.AndroidJUnit4
import androidx.test.internal.runner.junit4.AndroidJUnit4ClassRunner
import com.view9.legalremit.R
import org.junit.Test
import org.junit.runner.RunWith


@RunWith(AndroidJUnit4::class)
class LoginActivityUiTest{

    @Test
    fun is_ActivityInView() {
        val activityScenario = ActivityScenario.launch(LoginActivity::class.java)

        onView(withId(R.id.container)).check(matches(isDisplayed()))

    }
}

Above is my first Expresso test to check if an activity is in View. R.id.container here container is the id of the root layout of the Login Xml . But when i test it on my real Android device it fails with error: androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: with id is <com.view9.legalremit:id/container> . What am i doing wrong ?

Will there ever be a

DefaultLifecycleObserver

that can observe the entire Fragment lifecycle and not just the Fragment View Lifecycle? I ask because I want to get my team on-board with using FragmentFactory. Some have pushed back citing that it’s awkward having to remember to set it before calling

onCreate

and unset it in

onDestroy

. I was able to somewhat alleviate the issue by creating a

DefaultLifecycleObserver

that can unset it, and also register a

FragmentLifecycleCallbacks

so in

onFragmentCreated

I can check

savedInstanceState

to determine if recovering from process death where I can set the required Factory again. If I could hook into the Fragment’s

onCreate

from the get-go I think it would be possible to just set the Factory once, like in an

init

block, then the developer doesn’t have to remember to do any more maintenance on it. @Ian Lake?

Does anyone have any problems with google maps when updating fragment to

1.3.0

?

Could anyone help explain why I am getting a lateinit property has not been initialized error here? We have a Kotlin object that holds some dependencies with an initializer function:

object ExampleObjectHolder {
    lateinit var repository: Repository

    fun initialize(client: Client) {
        this.repository = Repository(bffClient)
        this.analytics = analyticsClient
    }
}

We have a top-level function that calls it, and then starts an Activity

fun startFlow(host: Activity) {
    ExampleObjectHolder.initialize(ServiceLocator.instance().client)
    host.startActivityForResult(Flow.packIntent(host), REQUEST_CODE)
}

Then inside our Activity we have a ViewModel which gets the dependency from that object

private val viewModel by viewModels<FlowViewModel> {
    FlowViewModelFactory(repository = ExampleObjectHolder.repository)
}

This is the point where it’s crashing, but I can’t figure out why because it’s initialized immediately before starting the Activity and the ViewModel accessing it. It’s also only crashing for a very small amount of users.

Hey guys, how are you? I'm trying to replace LiveData to use the new Kotlin's Flow features. I am experimenting a bit with States and Events (any link would be appreciated, but it has to contain some documentations about TESTING) Here is a dummy

ViewModel

for UI Events (i.e. show a snackbar or navigate to another screen)

class MyViewModel(
    private val shouldGoToX: ShouldGoToXUseCase
) : ViewModel() {

    private val eventChannel = BroadcastChannel<MyEvent>(Channel.BUFFERED)
    val events = eventChannel.asFlow()

    fun onCreate() = viewModelScope.launch {
        delay(3_000L)
        val navigationEvent = if (shouldGoToX()) {
            MyEvent.NavigateToX
        } else {
            MyEvent.NavigateToY
        }
        eventChannel.offer(navigationEvent)
    }

}

internal sealed class MyEvent {
    object NavigateToX : MyEvent()
    object NavigateToY : MyEvent()
}

And here is my test class

internal class MyViewModelTest {

    @get:Rule
    val testInstantTaskExecutorRule = InstantTaskExecutorRule()

    @get:Rule
    val testCoroutineRule = TestCoroutineRule()

    private val shouldGoToX = mockk<ShouldGoToXUseCase>()
    private val viewModel = MyViewModel(shouldGoToX)

    @Test
    fun `GIVEN the user should go to X WHEN starting the screen THEN the user should see the X Screen`() =
        testCoroutineRule.runBlockingTest {
            //GIVEN
            coEvery { shouldGoToX() } returns false

            //WHEN
            viewModel.onCreate()

            val events = viewModel.events.toList()

            //THEN
            assertEquals(MyEvent.NavigateToX, events.first())
        }
}

Few questions: 1. Any observations about the approach (events sent through a

BroadcastChannel

? 2. I'm currently getting this error in the tests, but I've correctly set the test coroutines stuff

java.lang.IllegalStateException: This job has not completed yet

. Am I doing something wrong there?

Why is it now preferred to do:

var args = GameWonFragmentArgs.fromBundle(requireArguments())

instead of:

var args = GameWonFragmentArgs.fromBundle(arguments!!)

I understand it eliminates the ugly

!!

, but it still will likely lead to an error (

IllegalStateException

rather than

NullPointerException

). This was asked on Stack Overflow but not really answered. ScoreFragmentArgs.fromBundle(requireArguments())

Good day everyone, I am new member here.. I am beginner to kotlin and i want to use kotlin for my mobile automation activities. I am planning to use Appium + kotest but I don't have any idea yet on how to do it. Can someone give me atleast a high level architecture and structure of it for my better understanding. Your responses with my concern is really appreciated and I owe it to you guys. Thank you.

Hi everyone, I just hit a roadblock using SafeArgs + Hilt + LiveData + ViewModel... my use case is: • ParentFragment is a fragment within a Navigation Graph, which has a SharedViewModel with some LiveData, and hosts a ViewPager2 • ChildAFragment is a fragment inserted into the ViewPager, which shows and changes some SharedViewModel's LiveData • ChildBFragment is another fragment inserted into the ViewPager, which shows and changes some SharedViewModel's LiveData So far so good, now the problem is: ParentFragment receives an argument. This argument should be in the ViewModel. Usually I would do:

@HiltViewModel
class SomeViewModel @Inject constructor(
    savedStateHandle: SavedStateHandle,
): ViewModel() {

    val argument: Argument =
        savedStateHandle[ParentFragmentArgs::argument.name]!!
}

However, this does not work with SharedViewModel (

private val viewModel: SomeSharedViewModel by activityViewModels()

) I think I understand why. This ViewModel isn't scoped to the Fragment, but to the Activity, so it probably gets the savedState of the Activity instead of the Fragment's (right?)

Hi Guys, this is Aditya, it's great to be a part of this huge community. May I discuss/ask queries on "compose for desktop" or should it be be purely around kotlin?

Jetpack compose is production ready 🎉

Difference between KOTLIN class and KOTLIN file in android studio ?

Any solution for Android 11 camera getting null

Hi all, looking to get a sanity check on lifecycleScopes… My Fragment is doing a simple network request , and when it’s successful I’m navigating to another Fragment, when it fails I’m displaying an error This works fine with process death, because the scope gets cancelled, but when the user backgrounds the app the coroutine still runs (because the view isn’t destroyed) and if successful it tries to navigate to the Fragment which fails because it’s after onSaveInstanceState() Is this the ‘correct’ approach below, to basically wrap the Fragment transaction in

whenStarted

?

viewLifecycleOwner.lifecycleScope.launch {
    val response = fetchConfig()
    when (response) {
        is ConfigResponse -> {
            whenStarted {
                goToNextScreen()
            }
        }
        Error -> showError()
    }
}

I wrote a Kotlin based library to help reduce the Boilerplate code for ViewBinding in Android to bare necessity, making it easy to use and wrote my first article explaining the same. Give it a read, if the topic interests you. Any feedback is welcome and appreciated. Thanks. Here is the link to the library.

Just trying jetpack compose last night, and was really a great experience in writing application, hope there preview gets stable and faster though