Setup the project with Travis CI.

Currently ContactManager only adds Contacts from the master table who only have Phone numbers. While this is required for RandomContact, this is causing issues in other applications that reference this feature.

Caused issue midhunhk/trip-o-meter#16

Move a few utility methods from dependent projects so that they could be reused by other applications,

Issue: If there are multiple permissions requested, if the first permission is granted but the rest are denied, handlePermissionsResult() invoked the onPermissionsGranted() callback.

Expected: Only if all permissions are granted, should the onPermissionsGranted() be called

Update Android Gradle Plugin Version

https://developer.android.com/build/agp-upgrade-assistant

Provide a reusable component that lets users select multiple contacts.

Reference
https://www.javatpoint.com/android-startactivityforresult-example
https://stackoverflow.com/questions/920306/sending-data-back-to-the-main-activity-in-android

Problem Description

Since the number of custom components provided by the library has increased and they are organized into packages by the type of the class, it is messy. Also applications that may need only one or two features need to include the whole library,

Solution

Refactor all the classes to packages by feature and split into multiple modules, so only required components would need to be added as dependency.

Proposing the following module structure:

• core
  • Custom Views
  • Common Models
  • SMS Manager
• billing-client
• contacts-api
• sms-api
• utilities
• multi-contact
• database-helpers
• mocks
• runtime-permissions

Other Tasks

• Distribute via JitPack.io
• Distribute via jCenter
• Generate javadoc for all modules
• Generate landing page with more information
• Remove deprecated code and resources
• Create Migration Guide
• Revisit implementation of complex components

Note: This is an API breaking change, hence we will have a major version release.

Looks like a never version of the com.android.billingclient:billing is available now.

https://developer.android.com/google/play/billing/billing_library_overview

deprecate the constructor and provide a newInstance() method for RuntimePermissionChecker

It would be a good idea to migrate to Kotlin DSL as in a multi module project like this, it will be easy to maintain dependencies and share common configuration among all modules.

https://developer.android.com/build/migrate-to-kotlin-dsl

Additional References:

• https://medium.com/codex/clean-dependency-management-in-multi-module-android-projects-49f2a0df8d2f
• https://docs.gradle.org/current/userguide/migrating_from_groovy_to_kotlin_dsl.html

Upon adding the library to an Android application, the java classes are inaccessible

To Reproduce
Steps to reproduce the behavior:

1. Use the latest version of the library (https://jitpack.io/com/github/midhunhk/lib-aeapps/v4.0.4/)
   implementation 'com.github.midhunhk.lib-aeapps:core:v4.0.4'
2. Sync the gradle file
3. e.g; 'EmptyRecyclerView' is inaccessible

Expected behavior
Class files should be available to use

Thanks to the community for not checking or reporting this issue.

Starting on August 2, 2023, all new apps must use Billing Library version 5 or newer. By November 1, 2023, all updates to existing apps must use Billing Library version 5 or newer.

https://developer.android.com/google/play/billing/integrate

https://developer.android.com/google/play/billing/deprecation-faq

https://developer.android.com/google/play/billing/release-notes

https://developer.android.com/google/play/billing/migrate-gpblv6

It would be nice to have a search filter in the ContactPicker.

Possible solutions to implement this feature:
https://android.jlelse.eu/search-on-recycler-view-android-e7661479481
https://stackoverflow.com/a/37735562/592025

Deploy the lib-ae-apps to jcenter so people/projects that require the library need not download the source and add as a dependency.

Reference
https://inthecheesefactory.com/blog/how-to-upload-library-to-jcenter-maven-central-as-dependency/en

Create a BaseDonationsFragment in addition to the BaseDonationsActivity already provided

Create a Base implementation for PermissionsAwareComponent, as there seems to be a lot of boiler plate code for an existing implementation.

Lets have the java doc for the library generated and published as app page.

Expose public methods to fetch contacts or fetch asynchronously instead of initializing in Constructor.

• Refactor ContactManager class
  • Extract an Interface with common methods from ContactManager
  • Create an abstract class with default implementation
• Use a Builder to make an instance of ContactManager
  • Make the constructor private to force the use of Builder
• Add an async method to read contacts
  • Testing async implementation
• Unit Tests for ContactManager
• Refactor Contacts database access to a separate class - ContactService (Separation of Concerns)

As per information here :https://github.com/dcendents/android-maven-gradle-plugin

Need to migrate off from that plugin

https://developer.android.com/build/publish-library

Problem

Currently the library is released via JCenter. Each build should be manually created and uploaded to bintray, this process is tedious and time consuming. This is a proposal to provide an alternate distribution option.
.

Solution

There is a free service called JitPack that supports library projects to be served primarily from each release, but also from branch or even commit