Karumi/Dexter — 5.2k★ on GitHub (Java). Android library that simplifies the process of requesting permissions at runtime.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This project is no longer under active development. If you are looking for an Android library to be able to request Android permissions in runtime take a look here
Dexter is an Android library that simplifies the process of requesting permissions at runtime.
Android Marshmallow includes a new functionality to let users grant or deny permissions when running an app instead of granting them all when installing it. This approach gives the user more control over applications but requires developers to add lots of code to support it.
Dexter frees your permission code from your activities and lets you write that logic anywhere you want.
To make your life easier we offer some PermissionListener implementations to perform recurrent actions:
BasePermissionListener to make it easier to implement only the methods you want. Keep in mind that you should not call super methods when overriding them.
DialogOnDeniedPermissionListener to show a configurable dialog whenever the user rejects a permission request:
PermissionListener dialogPermissionListener =
DialogOnDeniedPermissionListener.Builder
.withContext(context)
.withTitle("Camera permission")
.withMessage("Camera permission is needed to take pictures of your cat")
.withButtonText(android.R.string.ok)
.withIcon(R.mipmap.my_icon)
.build();
SnackbarOnDeniedPermissionListener to show a snackbar message whenever the user rejects a permission request:
PermissionListener snackbarPermissionListener =
SnackbarOnDeniedPermissionListener.Builder
.with(view, "Camera access is needed to take pictures of your dog")
.withOpenSettingsButton("Settings")
.withCallback(new Snackbar.Callback() {
@Override
public void onShown(Snackbar snackbar) {
// Event handler for when the given Snackbar is visible
}
@Override
public void onDismissed(Snackbar snackbar, int event) {
// Event handler for when the given Snackbar has been dismissed
}
}).build();
CompositePermissionListener to compound multiple listeners into one:
The MultiplePermissionsReport contains all the details of the permission request like the list of denied/granted permissions or utility methods like areAllPermissionsGranted and isAnyPermissionPermanentlyDenied.
As with the single permission listener, there are also some useful implementations for recurring patterns:
BaseMultiplePermissionsListener to make it easier to implement only the methods you want. Keep in mind that you should not call super methods when overriding them.
DialogOnAnyDeniedMultiplePermissionsListener to show a configurable dialog whenever the user rejects at least one permission:
MultiplePermissionsListener dialogMultiplePermissionsListener =
DialogOnAnyDeniedMultiplePermissionsListener.Builder
.withContext(context)
.withTitle("Camera & audio permission")
.withMessage("Both camera and audio permission are needed to take pictures of your cat")
.withButtonText(android.R.string.ok)
.withIcon(R.mipmap.my_icon)
.build();
SnackbarOnAnyDeniedMultiplePermissionsListener to show a snackbar message whenever the user rejects any of the requested permissions:
MultiplePermissionsListener snackbarMultiplePermissionsListener =
SnackbarOnAnyDeniedMultiplePermissionsListener.Builder
.with(view, "Camera and audio access is needed to take pictures of your dog")
.withOpenSettingsButton("Settings")
.withCallback(new Snackbar.Callback() {
@Override
public void onShown(Snackbar snackbar) {
// Event handler for when the given Snackbar is visible
}
@Override
public void onDismissed(Snackbar snackbar, int event) {
// Event handler for when the given Snackbar has been dismissed
}
})
.build();
CompositePermissionListener to compound multiple listeners into one:
If you want to receive permission listener callbacks on the same thread that fired the permission request, you just need to call onSameThread before checking for permissions:
Android will notify you when you are requesting a permission that needs an additional explanation for its usage, either because it is considered dangerous, or because the user has already declined that permission once.
Dexter will call the method onPermissionRationaleShouldBeShown implemented in your listener with a PermissionToken. It's important to keep in mind that the request process will pause until the token is used, therefore, you won't be able to call Dexter again or request any other permissions if the token has not been used.
The most simple implementation of your onPermissionRationaleShouldBeShown method could be:
@Override public void onPermissionRationaleShouldBeShown(PermissionRequest permission, PermissionToken token) {
token.continuePermissionRequest();
}
Error handling
If you think there is an error in your Dexter integration, just register a PermissionRequestErrorListener when calling Dexter:
Dexter.withContext(context)
.withPermission(permission)
.withListener(listener)
.withErrorListener(new PermissionRequestErrorListener() {
@Override public void onError(DexterError error) {
Log.e("Dexter", "There was an error: " + error.toString());
}
}).check();
The library will notify you when something bad happens. In general, it is a good practice to, at least, log every error Dexter may throw but is up to you, the developer, to do that.
IMPORTANT: Remember to follow the Google design guidelines to make your application as user-friendly as possible.
Permission dialog not being shown
If you are using the MultiplePermissionsListener and you don't see the permission dialog the second time the permission is checked review your configuration. Keep in mind you need to let Dexter know the rationale you can show was closed or not by calling token?.continuePermissionRequest(). If you don't do this, the next time the permission is requested, the OS dialog asking for this permission won't be shown. You can find more information about this in here. This is an example of how a multiple permission request should be implemented:
button.setOnClickListener {
Dexter.withContext(this@MainActivity)
.withPermissions(
Manifest.permission.ACCESS_COARSE_LOCATION
,Manifest.permission.ACCESS_FINE_LOCATION)
.withListener(object: MultiplePermissionsListener {
override fun onPermissionsChecked(report: MultiplePermissionsReport?) {
report?.let {
if(report.areAllPermissionsGranted()){
toast("OK")
}
}
}
override fun onPermissionRationaleShouldBeShown(
permissions: MutableList<PermissionRequest>?,
token: PermissionToken?
) {
// Remember to invoke this method when the custom rationale is closed
// or just by default if you don't want to use any custom rationale.
token?.continuePermissionRequest()
}
})
.withErrorListener {
toast(it.name)
}
.check()
}
Caveats
For permissions that did not exist before API Level 16, you should check the OS version and use ContextCompat.checkSelfPermission. See You Cannot Hold Non-Existent Permissions.
Don't call Dexter from an Activity with the flag noHistory enabled. When a permission is requested, Dexter creates its own Activity internally and pushes it into the stack causing the original Activity to be dismissed.
Permissions SYSTEM_ALERT_WINDOW and WRITE_SETTINGS are considered special by Android. Dexter doesn't handle those and you'll need to request them in the old fashioned way.
Contributors
Thank you all for your work!
Carlos Morera de la Chica
Alex Florescu
Pedro Veloso
Dion Segijn
Christian Panadero
Vignesh
Andy French
Bernat Borrás Paronella
Bastien Paul
Bas Broek
Bartek Lipinski
emmano
Konrad Morawski
Hrant Alaverdyan
Carla
Pavel Stepanov
Emmett Wilson
Max
Al B.
Vladislav Bauer
Jc Miñarro
handrenliang
jcruzsousa
lzdon
Do you want to contribute?
Feel free to add any useful feature to the library, we will be glad to improve it with your help.
Keep in mind that your PRs must be validated by Travis-CI. Please, run a local build with ./gradlew checkstyle build test before submiting your code.
Libraries used in this project
Butterknife
JUnit
Mockito
License
Copyright 2015 Karumi
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
The most recent commit recorded on Karumi/Dexter was 5.1 years ago, based on the GitHub push timestamp. The repository has 675 forks — one of the better signals of community interest.
How does Karumi/Dexter compare to other Mobile projects?
Karumi/Dexter is tracked by TopGit in the Mobile category, with 5.2k GitHub stars and written in Java. Browse the Mobile topic page on TopGit to compare it against similar projects by stars and activity.
How many stars does Karumi/Dexter have?
Karumi/Dexter has 5.2k GitHub stars — refresh the page for the live number, or check github.com/Karumi/Dexter. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is Karumi/Dexter open source?
Yes — Karumi/Dexter ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/Karumi/Dexter.
What is Karumi/Dexter?
Karumi/Dexter (Karumi/Dexter) is a Java project on GitHub. From the project's own README: Android library that simplifies the process of requesting permissions at runtime.
Where do I read more about Karumi/Dexter?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/Karumi/Dexter is the definitive source.
Read full README in the tab above.
Still deciding about Dexter?
One click hands the question to an AI along with this page — see what it says about Dexter.
/Dexter
Dexter 
