Runtime crash when not running gradle task before using Composable

[tassilo-posegga]

About this issue

Inititalizing the LibrariesContainer() without previously manually creating the the json file crashes the app at runtime.

LibrariesContainer(
            modifier = Modifier
                .padding(paddingValues)
                .fillMaxSize(),
            header = { item { Header() } },
            showVersion = false,
            showAuthor = false,
            showLicenseBadges = false,
            colors = LibraryDefaults.libraryColors(
                backgroundColor = KDSTheme.colors.background.base,
                contentColor = KDSTheme.colors.text.primary
            )
        )

 java.lang.IllegalStateException: Please provide the required library data via the available APIs.
                                                                                                    Depending on the platform this can be done for example via `LibsBuilder().withJson()`.

I didn't apply any options to the aboutLibraries block

I was under the impression that the plugin would take care of creating necessary assets.
Does that mean that I need to recreate the json file with every new build?

EDIT:

I figured the crash is gone when adding the plugin to the app level build.gradle, but the libs stay empty in the UI/while debugging the libs value. When generating the aboutlibraries.json file manually (which is also empty as stated in another issue #800 ) and running the app afterwards it complains about duplicate resources.

Details

- Used library version: 10.6.1

• Android

Checklist

• Searched for similar issues
• Checked out the sample application
• Read the README
• Checked out the CHANGELOG
• Read the MIGRATION GUIDE

[mikepenz]

Thank you. This problem seems to be possibly more related to these issues:

• Architecture change to support configuration cache in a proper way #857
• create .json file without content when use Android Gradle Plugin 7.3.0 #800

Overall having the plugin configured to generate the json and then having it as part of git may be a workaround (e.g. it not being automatically registered as part of the Android build pipelines)

[mikepenz]

@GoldenSoju if you run the gradle task manually https://github.com/mikepenz/AboutLibraries#gradle-api would the exports work?

Possibly the enterprise section could help in the meantime: https://github.com/mikepenz/AboutLibraries#enterprise

[mikepenz]

Closing for inactivity.