i'm having some java interop issues with

@Throws

The API

interface StormcrowBase {
   @get:Throws(Exception::class)
   val featureNames: ArrayList<String>
}

Java call site

try {
                features = stormcrowBase.getFeatureNames();
            } catch (Exception e) {
                e.printStackTrace();
            }

The error I'm getting is

Exception is never thrown in the corresponding block

. Any ideas?

What happens if you don't use

get:@Throws

and use

@Throws

instead?

that’s a compile error

yea, i haven't been able to resolve this. I switched from

val

to

fun

and the Java interop is working.. but the Kotlin API is pretty ugly now.

@Throws(Exception::class)
   fun getFeatureNames(): ArrayList<String>

Funny enough, the java generated decompiled class for both

val

and

fun

look identical

Throwing RuntimeExceptions is the rule for Java in a long long time

i obfuscated some of the code ^^, this is to interop with our existing Java codebase

I understand, but does your Java code base requires you to catch exception always?

this is a pretty large refactor, changing ~100 call sites

But you can still catch an exception, even if it's Unchecked, right?

we're writing all new code in Kotlin, and also this is for Android.. i think generally in Java-Android world, we prefer checked exceptions

As an Android dev myself, my team have always prefered to use unchecked exceptions. The same clean code practices should be applied

thanks for the suggestions

I think there is tho