crash on API22 upon opening

[Osanosa]

java.lang.ClassNotFoundException: javax.net.ssl.SNIServerName

Added in API level 24
SNIHostName

seems to be coming from
Security.insertProviderAt(Conscrypt.newProvider(), 1)
but i'm not sure yet

[Osanosa]

But conscrypt itself should be 19+, at least it says so on the GitHub page

[Osanosa]

Try running it on the emulator with devices set to pause on the exceptions

[Osanosa]

*debugger

[Osanosa]

Oh wait I can edit messages

[Osanosa]

Oh, whatever

[Osanosa]

Potentially this will never and has never worked on anything below A7

[Osanosa]

Do you have something like Crashlytics set up?

[Osanosa]

And also 🤓☝️ why still not on the play store?

[Osanosa]

Oh, i didn't notice in readme about A6 being minsdk
maybe change it in build.gradle?

[yuroyami]

@Osanosa The issue seems to be in the SDKs themselves, and we can't fix it without disabling Conscrypt. We have two options:

1. Keep pre-24 Android support and disable Conscrypt on those devices.
2. Drop support for pre-24 Android versions.

Since I want to keep compatibility, we'll go with the first option. Any TLS/SSL-related method should be wrapped in an SDK version check and a try/catch block for extra safety.

It should look like this:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) { // API 24 (Nougat)
   runCatching {
        Security.insertProviderAt(Conscrypt.newProvider(), 1)
   }
}

why still not on the play store?

The app was there twice, on two different accounts but my credit card seems to be permanently flagged on their system so I can't set up any more accounts for some reason. Google being Google I guess.

[Osanosa]

The app was there twice, on two different accounts but my credit card seems to be permanently flagged on their system so I can't set up any more accounts for some reason. Google being Google I guess.

Oh yeah they're funny guys
Wanna me try to publish it?

Since I want to keep compatibility, we'll go with the first option. Any TLS/SSL-related method should be wrapped in an SDK version check and a try/catch block for extra safety.

This won't be fixed with desugaring, ye?
I'm not exactly PhD level of development knowledge so I'm not that experienced

[yuroyami]

Wanna me try to publish it?

The only issue is that Google might target you like they did me if they think you're me for reuploading the app. I'll get a new credit card soon and try again, no worries.

This won't be fixed with desugaring, ye? I'm not exactly PhD level of development knowledge so I'm not that experienced

I'm honestly surprised you got through the messy codebase so quickly—kudos! I'll release a new APK with the changes soon and make sure to fix this issue as well while I'm at it. i got it

[Osanosa]

I'm honestly surprised you got through the messy codebase so quickly—kudos!

well I just open layout inspector and click on element I need to change

[Osanosa]

I think you should add Crashlytics while you're at it
And also maybe look up kotzilla, I still don't fully understand how to use it