PiracyChecker | Android library that prevents your app from being pirated / | Android library

by javiersantos Java Version: 1.2.8 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | PiracyChecker Summary

PiracyChecker is a Java library typically used in Mobile, Android, Gradle applications. PiracyChecker has build file available, it has a Permissive License and it has medium support. However PiracyChecker has 17 bugs and it has 2 vulnerabilities. You can download it from GitHub.

An Android library that prevents your app from being pirated / cracked using Google Play Licensing (LVL), APK signature protection and more.

Support

Quality

Security

License

Reuse

Support

PiracyChecker has a medium active ecosystem.

It has 1521 star(s) with 178 fork(s). There are 57 watchers for this library.

It had no major release in the last 12 months.

There are 23 open issues and 59 have been closed. On average issues are closed in 46 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of PiracyChecker is 1.2.8

Quality

PiracyChecker has 17 bugs (1 blocker, 0 critical, 0 major, 16 minor) and 132 code smells.

Security

PiracyChecker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

PiracyChecker code analysis shows 2 unresolved vulnerabilities (2 blocker, 0 critical, 0 major, 0 minor).

There are 0 security hotspots that need review.

License

PiracyChecker 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.

Reuse

PiracyChecker releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

PiracyChecker saves you 1719 person hours of effort in developing the same functionality from scratch.

It has 3807 lines of code, 199 functions and 55 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed PiracyChecker and discovered the below as its top functions. This is intended to give you an instant insight into PiracyChecker implemented functionality, and help decide if they suit your requirements.

Process a new response from the license server
Set the max retries value
Set the retry timestamp
Set the last valid license timestamp
Decodes the extras from the server
Obfuscate a string
Decode a base64 encoded data
Returns the number of bytes in the source array
Verifies the signed response from server
Parse response string into ResponseData object
Reset policy
Returns whether the client is allowed or not
Show APK signatures dialog
Generates a public key from a string representation
Retrieve a string value from the preferences
Set up the radio buttons
Check if the user has access to the application
Returns the value of the accessed response

Get all kandi verified functions for this library.

PiracyChecker Key Features

No Key Features are available at this moment for PiracyChecker.

PiracyChecker Examples and Code Snippets

No Code Snippets are available at this moment for PiracyChecker.

Community Discussions

Trending Discussions on PiracyChecker

Android App Bundle kills Google Play Games integration - Working with plain old APK - How can I fix this?

QUESTION

Android App Bundle kills Google Play Games integration - Working with plain old APK - How can I fix this?

Asked 2020-Jun-06 at 08:23

Here are the facts:

My game app is 100% working with debug keystore signed apk using Google Play Games, can sign in, unlock achievements.
My game app is 100% working with release keystore signed apk using Google Play Games, can sign in, unlock achievements.
Whenever I try to sign in to Google Play Games with my app using app bundle instead of apk, I get SIGN_IN_REQUIRED error, which is stupid on its own, considering I literally want to sign in.

I only found one guy who found the same issue but he is developing his game in Unity, and my app is a native Android app made with Android SDK, so I don't really get his solution.

I won't input screenshots about console settings and SHA1 keys and linked apps and all about those things because as I said, the only difference between the working versions and the not working version is that the not working version has been made to an android app bundle, instead of an apk, so the integrations is correct.

The sad thing is that my apk is more than 100 MB so Google Play doesn't let me upload it anymore, I have to app bundle.

The process of making my app into an app bundle somehow make Google Play Games integration broken.

Any ideas?

E D I T:

As requested, here is the gradle.properties file:

...

ANSWER

Answered 2020-Jun-06 at 08:23

What Google is doing is signing the APKs that it generates from the App Bundle.

The release keystore you sign your App Bundle with is effectively only used by Google to authenticate the origin of the artifact. What is served to users are APKs signed with a key called the "app signing key".

If you go to the "App Signing" page in the Play Console, you will be able to find the upload certificate (which corresponds to your release keystore) and the app signing certificate.

Copy the SHA-1 of the app signing certificate.

Then, did you register your game in the Play Console in the "Game services" section? If so, go to "Linked apps", select "Android" and after filling the details of package name etc., you'll be asked to enter the SHA-1 to create the Client ID.

In there, paste the SHA-1 copied previously.

Hope that helps.

Source https://stackoverflow.com/questions/62148182

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

Vulnerabilities

No vulnerabilities reported

Install PiracyChecker

You can download it from GitHub.
You can use PiracyChecker like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the PiracyChecker component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

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: