Android Question Difficulty using payment library

abilio486software

Active Member
Licensed User
Hello,

I',m trying to use this payments library. Thanks to Erel we are almost there but for some reason still have this 3 errors.

What can be wrong?

Many thanks

PS: Project with manifest is attached and library is online because of its size:
Jar library (11Mb)


error.png
 

Attachments

  • verifone.zip
    9.8 KB · Views: 151
Last edited:

abilio486software

Active Member
Licensed User
Done! Now compiles without error!!

I followed an old GymReaper track and as I saw that you reinstalled the system, having solved the error, I decided to delete the values files that have this error and now compiles without problems :)


Now I'm going to see if it really works, but that's OK for now!

Many thanks Erel e GymReaper
 
Upvote 0

abilio486software

Active Member
Licensed User
Ops... When linking


Parsing code. (0.00s)
Java Version: 8
Building folders structure. (0.02s)
Compiling code. (0.03s)
Compiling layouts code. (0.00s)
Organizing libraries. (0.02s)
(AndroidX SDK)
Generating R file. (0.00s)
Compiling generated Java code. (0.05s)
Convert byte code - optimized dex. Error
trouble processing "javax/xml/bind/ServiceLoaderUtil.class":
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.
If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
1 error; aborting
 
Upvote 0

delgadol

Member
Google is introducing gradual changes in the development mode, including visual effects, life times, and who knows what else, I am certain that the development team is already watching what happens, because it mainly affects all the code that I use appcompact and desing, design will no longer be supported, and google asks that it no longer be used. for now, it only remains to wait and make a rollback to the sdk.
 
Upvote 0
Top