easypermissions

Version 3.0.0 contains a breaking change:

• Move from using Android Support Libraries (com.android.support.*) to AndroidX libraries (androidx.*). If you are using the Android Support Libraries without using Jetifier this is a breaking change for you.

The newly updated transitive dependencies are:

 <dependencies>
    <dependency>
      <groupId>androidx.appcompat</groupId>
      <artifactId>appcompat</artifactId>
      <version>1.0.2</version>
    </dependency>
    <dependency>
      <groupId>androidx.core</groupId>
      <artifactId>core</artifactId>
      <version>1.0.1</version>
    </dependency>
    <dependency>
      <groupId>androidx.fragment</groupId>
      <artifactId>fragment</artifactId>
      <version>1.0.0</version>
    </dependency>
  </dependencies>

Version 2.0.1 contains bug fixes for the following issue:

• Crash when showing rationale in a FragmentActivity that is not an AppCompatActivity (#266)

Version 2.0.0 contains some breaking changes:

• Drop support for android.app.Fragment, which is deprecated in Android 28. Apps that want to use EasyPermissions in a Fragment should use the Fragment class in the Android Support Library (AndroidX).
• Remove all previously @Deprecated methods to clean up the API.

This version also bumps the support library dependency from 27.1.1 to 28.0.0. This will be the last release using the old-style support library before moving to androidx.

Version 1.3.0 contains a new feature:

• New setOpenInNewTask option when building the App Settings Dialog.

This version also bumps the support library dependency from 27.1.0 to 27.1.1.

Thanks to first time contributors @henriquenfaria and @sebkur 🎉

Version 1.2.0 contains a bug fix and a new feature:

• New RationaleDialogCallbacks feature for detecting interactions with the rationale dialog (#208)
• Fix for a bad cast (#201)

This version also bumps the support library dependency from 27.0.2 to 27.1.0.

Thanks to first time contributors @rayevg and @ernestkamara 🎉

Version 1.1.3 contains a bug fix for Issue #198 (via #199). This ensures results are forwarded to Fragments.

This version also bumps the support library dependency from 27.0.1 to 27.0.2.

Version 1.1.2 contains a bug fix for Issue #193 (via #195). This prevents the permission rationale dialog from appearing multiple times in the same Activity.

Version 1.1.1 contains a fix to how EasyPermissions declares dependencies. The support library dependency is now properly declared in the pom.xml file (#187).

Due to the explicit dependency on support library 27.0.1, you must use a compile SDK version of 27 or higher with this version.

All users of EasyPermissions 1.1.0 should upgrade to 1.1.1.

Version 1.1.0 contains bug fixes, API improvements, and some deprecations:

• New PermissionRequest builder API for passing arguments to EasyPermissions.requestPermissions via #180
  • Allows passing of theme argument for the rationale dialog (#174)
  • Replaces some of the requestPermissions overloads that had many arguments.
• Improved Kotlin support with method and parameter annotations (#178)
• Reduce the likelihood of #150 via #170

Special thanks to @SUPERCILEX who spearheaded the new API changes.

This is a bugfix release:

• Fix for an AppCompat incompatibility issue (#160)

Version 1.0.0 is the first major-version release of EasyPermissions! This reflects the overall stability of the API and library internals.

API Changes

• AppSettingsDialog.Builder#Builder([Activity/Fragment/android.app.Fragment], String) constructors removed. Use AppSettingsDialog.Builder#setRationale([String/int]) instead or leave blank to use the default rationale message.
• AppSettingsDialog.Builder#setNegativeButton(String, DialogInterface.OnClickListener) removed. To know if a user cancelled the request, check if your permissions were given with EasyPermissions#hasPermissions(...) in Activity#onActivityResult(...). If you still don't have the right permissions, then the request was cancelled.

New features

• You can now specify a custom theme for AppSettingsDialog via AppSettingsDialog.Builder#setThemeResId(int)
• In addition, if you use AppCompat color theming and have the three basic colors setup (color{Primary,PrimaryDark,Accent}), AppSettingsDialog will automatically use them to correctly style the dialog based on your app's theme instead of using the system defaults.

Bug fixes

• Use support and framework dialog implementations where applicable (#142 and #156)
• appcompat-v7 dependency is no longer leaked to consumers

This version of EasyPermissions has no behavior changes, but contains two developer improvements:

• Consumer proguard rules are added (#137)
• Javadoc JAR included in releases (#123)