You can make an application interceptor that loops!

After updating sqldelight from

1.3.0

to

1.4.3

my tests started throwing:

kotlin.Exception: android/database/sqlite/SQLiteException - no such table: location (code 1): , while compiling: INSERT INTO location VALUES (?, ?, ?, ?, ?, ?)

Have anyone faced problem like this? Also I noticed that now sqldelight auto-generates

data classes

instead of

interfaces

, what’s the reason behind this change?

Less codegen, let’s people use data class semantics on the projections, interfaces were only there to support autovalue back in the java days

I can’t find anything in the documentation of KotlinPoet. If I have a

ClassName

that is i.e.

String

can I somehow use it to create

String::class.java

? The best I found is

("%L::class.java", className.canonicalName)

but I’d like to use a simple name that will be in the import list.

You can use

%T

to get an import along with just passing

className

Oh, that’s simple enough 😅 . Thanks!

Hmm… maybe I’m missing something but this

("%T as %T", sourcedWith, featureType)

generates this

override val sourcedWith: Class<Feature<*>> = <http://com.my|com.my>.CustomFeature as Class<Feature<*>>

And I want

override val sourcedWith: Class<Feature<*>> = CustomFeature::class.java as Class<Feature<*>>

you still have to keep the

::class.java

part after

%T

. I just meant that

%T

will handle importing for you

In retrofit if I have a request annotated with @FormUrlEncoded and @Post are the fields part of the actual Url? i.e. Would something like this be bad?

@Field("password") password: String

I'm using charles to inspect the request, and I don't see it in the URL there, it seems to be part of the request body, but not sure. My backend team says that they see someone sending it in the url as a param.

you can see an example of a form urlencoded request here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST#Example. it does not put data into the URL, it merely uses URL encoding

Thank you. I read the docs from retrofit as well, but I was going crazy since it said "URL" and my team is adamant that it's the Android app. Looks like it's iOS 👀 Thanks @jw

A follow up to that (more for advice than anything related to squarelibraries), but my team is now saying that the form attributes should be encrypted (as in, if you inspected with charles, you shouldn't be able to read the password) I feel like that's kind of crazy because we use TLS, and so it is encrypted. Leads me to my question... do most apps/services just send up the username/password combo in "plaintext"? From what I'm seeing (and inspecting via charles) that seems to be a valid route that teams take.

if you do something like cert pinning where you specify which certs that you only trust then yes, tls is enough

i guess it really comes down to what you're defending against

https://repo1.maven.org/maven2/com/squareup/sqldelight/runtime-iosx64/ It seems like sqldelight 1.4.4 doesn't have native variants of runtime artifact

tracking here

Does anyone as already had an issue with sqldelight encode with adapter? I'm trying to serialize a simple object, it's working fine on android, but crashes on ios....

@Serializable
data class AccessModel(
    val isAccessible: Boolean = false,
    val conditions: List<ConditionModel>? = null
)

@Serializable
data class ConditionModel(
    val id: Int,
    val value: List<String>? = null,
    val min: Float? = null,
    val max: Float? = null
)

It's crashing here:

bindString(1, visibility?.let { database.FieldAdapter.accessModelAdapter.encode(it) })

fun accessModelToString(item: AccessModel): String = Json.encodeToString(AccessModel.serializer(), item)

val accessModelAdapter = object : ColumnAdapter<AccessModel, String> {
    override fun encode(value: AccessModel): String = SharedJSONConverter.accessModelToString(value)
}

Here the object that's crashing.

{"conditions":[{"id":321,"value":["40"]}]}

Thread in Slack Conversation

Was it this: https://youtrack.jetbrains.com/issue/KT-20996 I just bumped into it today, seems to be due to serialization but only happened on ios

does okhttp works on ios with kotlin multiplatform?

Hi! I'm currently integrating Moshi with androidx's new DataStore. Everything was going swimmingly until I tried to make use of Okio's

CipherSource

and

CipherSink

to encrypt the JSON on disk. From what I can tell, it's probably me misusing Okio. I'm attempting to save the Cipher's initialisation vector into a

Sink

before then converting that into a

CipherSink

. This ends up looking like:

fun getEncryptedSink(output: OutputStream): Sink {
  val cipher = getEncryptionCipher()

  return output.sink().buffer().use {
    it.writeInt(cipher.iv.size)
    it.write(cipher.iv)
    it.buffer.cipherSink(cipher)
  }
}

The reason I want to write the IV to disk is so I can use it to construct a decryption cipher on the way back out:

fun getDecryptedSource(input: InputStream): Source {
  return input.source().buffer().use {
    val ivSize = it.readInt().toLong()
    val iv = it.readByteArray(ivSize)
    val cipher = getDecryptionCipher(iv)
    it.cipherSource(cipher)
  }
}

But this approach makes DataStore extremely unhappy, crashing when it attempts to write the data to disk. Specifically, a call to

stream.fd.sync()

fails. Anyone know what's wrong with my approach?

Your

use

use closes the sink before it's returned

similarly on the reading side

you need to do something like

return output.sink().buffer().let {
  // write into the BufferedSink's buffer
  it.buffer.writeInt(cipher.iv.size)
  it.buffer.write(cipher.iv)
  // return a CipherSink around the BufferedSink
  it.cipherSink(cipher)
}

Any advice how to deal with screen configurations with Contour? Trying to use Contour on one of our screen that has different layout and text colors on mobile portrait, landscape mode and TV screens. I created something like to return screen config but it still seems pretty tedius to check the config and return different values in every child layout

class LayoutConfigResolver @Inject constructor(private val context: Context, private val deviceInfo: DeviceInfo) {
    fun currentConfig() = when {
        deviceInfo.isTv -> TV
        else -> if (context.resources.configuration.orientation == Configuration.ORIENTATION_PORTRAIT) PHONE_PORTRAIT else PHONE_LAND
    }
}

yeah you’ll probably want to introduce higher level abstractions and leverage polymorphism instead of doing if else checks in your layouts

maybe for text colors you could introduce semantic naming for your colors that resolve to the correct color depending on your configuration

// In your dependency graph
val colorPalette = if (deviceInfo.isTv) draculaTheme() else solarizedLightTheme()

// In your layouts
textView.setTextColor(colorPalette.heading)

that makes sense. Thanks for the quick response.

Well it was a fun little exercise, but after all that it looks like I can't use

CipherSink

with DataStore. They now explicitly forbid closing the provided

OutputStream

, which I believe

CipherSink

needs to do in order to invoke its

doFinal()

. https://android-review.googlesource.com/c/platform/frameworks/support/+/1464603