I'm not sure if this goes here, but whenever I try and publish a multiplatform library, gradle fails at the task

:generateMetadataFileForKotlinMultiplatformPublication

with the error

Invalid publication "kotlinMultiplatform"

while using the

maven-publish

plugin. Is this something that there's a fix for or should I be doing something else to publish my library?

What warning do you have to suppress to still use a deprecated symbol with level

HIDDEN

? for

WARNING

and

ERROR

you can do this:

@Deprecated("w", level = DeprecationLevel.WARNING)
val w = "w"

@Deprecated("e", level = DeprecationLevel.ERROR)
val e = "e"

@Deprecated("h", level = DeprecationLevel.HIDDEN)
val h = "h"

println(@Suppress("DEPRECATION") w)
println(@Suppress("DEPRECATION_ERROR") e)
println(@Suppress("?? what goes here ??") h)

We have two different kinds of

@RequiresOptIn

annotations in our library. 1. Experimental annotations for some new API that might change.

We have two different kinds of

@RequiresOptIn

annotations in our library. 1. Annotations for new experimental API that might change. 2. Annotations for API that is easy to use incorrectly. Which

AnnotationRetention

should be used in each case? (

BINARY

or

RUNTIME

,

SOURCE

isn't allowed)

Hello folks, Im trying to publish a kotlin-jvm-only library which is dependent to an internally library of mine. When i publish it, i try to consume it in my demo-project but it asks for the jar of the internal module of mine. What are my options if lets say i cant publish directly at least the internal lib? Thanks in advance for any answers or help.

Check it out and hit star this repo. https://github.com/SimformSolutionsPvtLtd/SSComposeCookBook Awesome Mobile Libraries. Check it out and hit star this repo. https://github.com/SimformSolutionsPvtLtd/Awesome-Mobile-Libraries

Open for feedback 🙂 https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1662937749366859

Hi folks, i am developing an SDK for my application's APIs and i have come across a dilemma, in requests like

getAccount(): Accounts

do you prefix your entities or not? Thanks in advance for any answer !

Can somebody tell me how to update the artifact IDs of the different components? My shared module is named "mobileSdk", but I prefer it to be deployed as "mobile-sdk". I'm calling setArtifactId() in " publications.withType<MavenPublication> {", but it only applies to the root artifact.

Can someone confirm to me that we cannot publish to maven central from a private GitHub repository? I have a use case at work where I'd like to do that, but all I read talks about public GitHub repositories 🤔

Hi all, I would like to create a library for my mobile app, having a common logic + specific custom components per platform (android and iOS). I've created a common base code in the commonMain, I've also created a CustomButton in the AndroidMain that can be use by my android app. Now the question is, is it possible to create custom components on the iOSMain and use it specifically in my iOS app, I checked and couldn't find any example (except for KMM App but I'm doing a KMM lib). Thanks in advance

Hey guys! Maybe someone has gone through a similar thing.. How bad is this? I mean.. it feels pretty hacky, but it's just sooo much more convenient to make users of my library able to write unit tests with no additional setup 😛

@SuppressLint("NewApi", "ObsoleteSdkInt")
internal fun ByteArray.toBase64Str(): String {
    // Both these methods (from java util and android util) seem to
    // do exactly the same.
    // The second doesn't work on Unit tests and the first doesn't work
    // on older devices.
    // Also, on unit tests SDK_INT is 0, but we're running on the developer's machine
    // So we can still use java.util in that case

    return if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O || Build.VERSION.SDK_INT == 0) {
        java.util.Base64.getUrlEncoder().encodeToString(this)
    } else {
        android.util.Base64.encodeToString(this, Base64.URL_SAFE or Base64.NO_WRAP)
    }
}

:kotlin-intensifies-purple: Kotlin 1.8.0-Beta brings the following updates: • Gradle 7.3 compatibility • Recursive

Path

utility functions in the stdlib • Support for Xcode 14 in Kotlin/Native • Discontinuation of support for the old JVM backend Try it out and share your feedback! 👉 https://kotlinlang.org/docs/whatsnew-eap.html Why install Beta? If you’re a library author, working with EAP versions allows you to support the latest Kotlin versions in your library almost immediately with the Stable release, which makes your users happier and your library more popular.

In java, one can build a library with the Latest possibpe version, but targets lower versions (mostly 1.8) during compilations. So yoy tend to use late technology, but keep users of the old ones happy. Do we have something similar for kotlin??

cross-post: https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1669283560214619

continuation of this discussion

Hi there, when building a library, how could I flag certain functions as being used externally (by the users of the library) (without always writing a dummy test)? Or do I simply need to disable the inspection for these functions? Example

Hi everyone! I was looking for a way to be able to change KDocs at compile-time such that changes appear in the sources.jar as well as potentially a javadoc.jar or HTML Dokka site. Existing solutions only worked for the latter and since there exists no such thing as a kdoc.jar, changed documentation doesn't always (correctly) show up when a user is working with your open source library. Introducing my KDoc / JavaDoc Preprocessor Gradle Plugin! This plugin acts as a preprocessor on your sources, allowing you to create new sources from your own with modified KDoc/JavaDocs. The plugin contains a couple of default processors, but is also extensible to include your own! Examples include: •

@include

tag to include other comments into your KDoc / JavaDoc, see @include Processor (

INCLUDE_DOC_PROCESSOR

) •

@sample

/

@sampleNoComments

tag to include code samples into your KDoc / JavaDoc (

SAMPLE_DOC_PROCESSOR

) • A processor that removes all KDoc / JavaDoc comments (

NO_DOC_PROCESSOR

) • A processor that adds a

/** TODO */

comment wherever there is no KDoc / JavaDoc comment (

TODO_DOC_PROCESSOR

) • A processor that makes all KDoc / JavaDoc comments uppercase (try and make this for fun!) • The sky is the limit :) Note that this first release is still an early Alpha, but I'm welcome to feedback, bugs, your own processors and whatnot :)

Hi folks, after reading this Programming with assertions it got me thinking if i should also program like that my library. What's your input/review/pov on this? Side note: From the official libraries kotlin-team provides kotlinx.coroutines seems to follow this technique but not kotlinx.serialization. Wondering what was the decisions behind this to include or not assertions.

📣 Hi everyone! We’re conducting our regular survey on library authors’ experience. If you’re an author of a published Kotlin library or working on one now, please share your feedback. Take the survey: https://surveys.jetbrains.com/s3/kotlin-libs-authors-survey 🎁 You will also have the chance to win 1 out of 5 one-year JetBrains All Products Pack subscription or a $100 Amazon certificate.

Hello. Does anyone (especially Mr. @udalov) know what I should implement to access

org.jetbrains.kotlin.metadata.deserialization

? I am developing a project to rewrite `jackson-module-kotlin` with `kotlinx-metadata-jvm` and I noticed that the initialization process of

KmClass

is slow. It can't simply compare them because the processes are different, but a benchmark on initialization shows that the content under development takes about 1.2 times longer than the original (comparison on

o.w.ser.T_20Props.call

). https://github.com/ProjectMapK/jackson-module-kogera/pull/63 I looked at the profile of this process and found that most of it was the initialization process of

KmClass

. I think this difference is caused by

KmClass

reading all the information at once during initialization. The

KClassImpl

seems to lazily initialize only the information it needs. So I tried to create a

LazyKmClass

that lazily initializes only the necessary information, referring to

kotlinx.metadata.internal.ProtoBuf.Class.accept

. However, I am currently stuck because I can't figure out how to access

org.jetbrains.kotlin.metadata.data.deserialization.protoTypeTableUtil

. Any help would be greatly appreciated.

Hi all, does anyone know where I can find official documentation for Kotlin's public API mode? There's various unofficial guides, a KEEP and it is referenced in some release notes, but I can't seem to find a official documentation page.

📣 Call to Action. Hi everyone! The survey is still ongoing and your feedback will help us advance the support initiatives of our library authors. If you haven’t already done so, please complete the survey. https://kotlinlang.slack.com/archives/C8C4JTXR7/p1675931708670469

I have explicitApi mode enabled in my multiplatform library. It correctly enforces the visibility modifiers and return types for the common and ios sourcesets, but for the android sourceset it does not work, neither in the IDE and during compilation. Any ideas?

Does anyone have a take on what are good practices while writing an SDK in Kotlin? My SDK will need to work great with Java and this is my first time writing one so just if you have some points that I need to consider while writing it. Have someone done that from this channel?

Maybe someone here can shed more light on this? https://kotlinlang.slack.com/archives/C7L3JB43G/p1678126163957399

If I have one project with the structure as following:

org.myorg.sdk.http

And then I have another project that have:

org.myorg.api

Could there be some conflict if I import that first one as

implementation("org.myorg.sdk:http:0.1.0")

I believe there might be something like that since when I implement it, I can't import it since it probably thinks it's in the same project but on a different path? I get the error: "Unresolved reference: sdk" How can fix this?

Hey , what are some good techniques to avoid Binary Compatibility issues