material-dialogs | 😍 A beautiful , fluid , and extensible dialogs API | Android library

Β by Β  afollestad Kotlin Version: 3.3.0 License: Apache-2.0

kandi X-RAY | material-dialogs Summary

kandi X-RAY | material-dialogs Summary

material-dialogs is a Kotlin library typically used in Mobile, Android applications. material-dialogs has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

A beautiful, fluid, and extensible dialogs API for Kotlin & Android.

            kandi-support Support

              material-dialogs has a medium active ecosystem.
              It has 19598 star(s) with 3158 fork(s). There are 561 watchers for this library.
              It had no major release in the last 12 months.
              material-dialogs has no issues reported. On average issues are closed in 45 days. There are 12 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of material-dialogs is 3.3.0

            kandi-Quality Quality

              material-dialogs has 0 bugs and 0 code smells.

            kandi-Security Security

              material-dialogs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              material-dialogs code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              material-dialogs is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              material-dialogs releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              It has 10832 lines of code, 433 functions and 196 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of material-dialogs
            Get all kandi verified functions for this library.

            material-dialogs Key Features

            No Key Features are available at this moment for material-dialogs.

            material-dialogs Examples and Code Snippets

            No Code Snippets are available at this moment for material-dialogs.

            Community Discussions


            android:exported added but still getting error Apps targeting Android 12 and higher are required to specify an explicit value for android:exported
            Asked 2022-Mar-24 at 15:30

            I have added android:exported="true" to my only activity in manifest but still getting below error after updating compile sdk and target sdk version to 31.I also tried rebuilding the project , invalidating cache and restart but that didn't helped

            Error- Apps targeting Android 12 and higher are required to specify an explicit value for android:exported when the corresponding component has an intent filter defined. See for details.

            AndroidManifest File ...


            Answered 2021-Oct-05 at 10:38

            After the build has failed go to AndroidManifest.xml and in the bottom click merged manifest see which activities which have intent-filter but don't have exported=true attribute. Or you can just get the activities which are giving error.

            Add these activities to your App manifest with android:exported="true" and app tools:node="merge" this will add exported attribute to the activities giving error.




            Gradle Failure A problem occurred evaluating project ':app' after update android Studio
            Asked 2022-Jan-21 at 12:38

            I need to update an app that hasn't been updated since 2018.

            I haven't messed with Android for a while, and even after updating all the libraries used, I can't find where the error is. I don't even know how many questions I've read here, and none of them have worked so far. So I decided to open my own question.

            Here is the project build.gradle:



            Answered 2022-Jan-21 at 12:38


            java.lang.NoSuchMethodError after upgrading Jetpack Compose to 1.0.0‑beta07
            Asked 2021-Jun-11 at 13:31

            I'm getting the following error running observeAsState on a LiveData object after I upgraded Jetpack Compose to 1.0.0‑beta07.



            Answered 2021-May-19 at 22:23

            Your runtime-livedata dependency is outdated:



            Failed resolution of: Lcom/google/android/gms/common/internal/zzbq for MiniControllerFragment
            Asked 2020-Nov-11 at 07:21

            I'm getting the following error for MiniControllerFragment, This is a music player app & uses CastOptions, after upgrading to latest gradle, I'm getting this issue. If anybody is facing the same issues earlier & found out any solution then request you to help me as well.



            Answered 2020-Nov-11 at 07:21

            You should upgrade your gms:play-services-cast-framework version.



            Exception when migrating to androidX
            Asked 2020-Nov-05 at 00:31

            I am trying to migrate my current project to android x and this exception shows up



            Answered 2020-Nov-05 at 00:31

            by using gradlew build --debug I was able to get the specific cause which was causing this issue it was caused by

            apply from: '../config/style.gradle'

            which is a tool development tool to help programmers write Java code that adheres to a coding standard.


            I didn't reset it but temporarily disabled it as my requirement was to migrate to android x.



            How can I use androidx libraries with exoplayer libraries?
            Asked 2020-Oct-23 at 09:46

            My build failed after migrating to androidx and cannot find exoplayer dependency. It's not also finding my exoplayer dependency class, I have tried to fix by enabling jetifier true but still, it doesn't work It's syncing properly but cant build Here is my error for the build How can I use androidx libraries with exoplayer libraries? Please help



            Answered 2020-Oct-23 at 09:46

            Change the dependency of exoplayer from 2.6.0 to 2.7.3



            How to fix issues with NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/common/R$string on Android
            Asked 2020-Sep-22 at 17:06

            Recently, I faced an issue that I'm not able to solve for a week, reading different sources with advices. But, nothing helped.

            So, the issues is in NoClassDefFoundError that appeared after upgrading:

            1. Gradle Wrapper from 5.x to 6.x
            2. Gradle Build Tool
            3. Firebase dependencies (which are actually brings these classes I have problems with)

            What I have already tried to fix an issue:

            1. Tried to downgrade Firbase libraries (I have only core, ads and analytic)
            2. Tried to disable transitive basemenet dependency
            3. Tried to apply BOM to sync dependencies
            4. Tried to upgrade/downgrade android build plugin
            5. Tried to find issue with existing green-dao version, but it looks good

            Here are dependencies from my build.gradle file:



            Answered 2020-Sep-22 at 17:06

            So, after few days of digging around I have found a solution. So, to make it work I had to:

            1. Downgrade Android Gradle Plugin to 3.5.3 version
            2. Downgrade Gordon plugin to 1.0.6 version
            3. Migrated fabric-crashlytic to firebase-crashlytic. With adding plugin of the last as well, otherwise, errors occur.

            All other updates could be set, but this 3 items have to be sticked to the versions mentioned.



            android kotlin multiplatform kotlinx.serialization works on debug but does not work on release version
            Asked 2020-Jul-01 at 11:39

            We are making our next project in the company with kotlin multiplatform. Everything worked fine until I tried to create a release version for android to beta test. I got this error in release versions while everything works fine in debug.



            Answered 2020-Jul-01 at 11:39

            If the app works in debug but not in release, it's probably because Proguard minified your classes and deserialization no longer works due to different (shorter) class and property names.

            Make sure you have this in your proguard:



            All my xml files have errors in AndroidStudio Project
            Asked 2020-Jun-24 at 12:40

            looks like all xml files AndroidManifest.xml and res xml files have errors, like "URI is not registered (Settings | Languages & Frameworks | Schemas and DTDs)" and "Attribute android: is not allowed here" errors.

            For example this is my manifest file:



            Answered 2020-Jun-24 at 10:34

            you need to add the schema of tools and android attributes in the top or parent layout of the xml

            like this



            TimePicker accepts values higher than 24h
            Asked 2020-May-25 at 14:54

            I'm using TimePicker and on newer devices, there is an option to set values from the keyboard:

            The problem is that, input accepts values way above 24h. User can put there any 2 digits number (e.g. 82) and still can click "OK".

            Because of obvious reasons, it is not acceptable behavior. Is there any way to restrict what values are accepted or at least block the possibility to use the keyboard to input hours/minutes?

            Ps. I'm using Afollestad's material dialogs, but as far as I know, he is using default TimePicker below, the only differences are styles and few extensions. I tried without this library, just by using TimePickerDialog and it's exactly the same. If a user sets input higher than 23/59 it's just set to 23/59 accordingly.

            Edit: My bad, now I can see that, dialog from this library is not validating the input. With the default implementation, click validates input.



            Answered 2020-May-25 at 14:54

            The problem was with the library I've used. I made a PR that fixes this issue. Hopefully, it will be merged in the close future.


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install material-dialogs

            You can download it from GitHub.


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone afollestad/material-dialogs

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link