Is this any reason to use

return suspendCoroutine{
   continuation -> usecase.invoke{result -> continuation.resumeWith(Result.success(result)}
}

Is there any difference between suspendCancellableCoroutine? Becuase I know I've been using this for instance for firebase sign in

suspendCancellableCoroutine supports cancellation, and it’s very good idea to support it if API supports it

Nono I mean the example in code is not about firebase it's another example that I have, but wondering if I do not want to cancell it that's why this code has the suspendCoroutine right?

I use cancellable version everywhere

Could you give me a reason to cancel it? I mean, for instance if the activity/fragment gets destroyed?

Any reason, bind it to lifecycle is one of them

There are two reasons to support cancellation in suspend functions you provide to others: 1) to let your callers signal your code to stop doing work, and 2) to let your callers stop waiting for your code to complete because they no longer care and need to run their own cleanup code, e.g. finally blocks. You might not care about (1) but your callers always care about (2).