-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UNEXPECTED TOP-LEVEL EXCEPTION: Error:com.android.dx.cf.iface.ParseException: class name (com/paypal/android/sdk/a) does not match path (com/paypal/android/sdk/A.class) #48
Comments
Hey, can you give a little more detail on how you got this? Also, can you try to a Rebuild project? |
I've this problem too. I have it when i try to built and run my app. A tried to rebuild and clean my project, but without success. I have this problem since a week. |
I put together a blank 'Hello, Client!' project. I didn't have any issues building, and running it. This was using the latest version: |
Me too facing the same problem. I have just updated to latest android 23 and the problem started...
|
We're sorry you're running into problems. We'll need a little help reproducing this issue. What is your build environment (OS, version of Android Studio / Gradle, etc)? We do not technically support Eclipse, but whatever your environment we'll do our best to replicate and solve your issue. |
Hi My Build Environment Regards On 18 September 2015 at 20:32, Gary Bramwell notifications@github.com
|
My Build Environment I already used latest version 1.6.5, but this problem occured also with 1.6.4. Maybe is a Paypal API problem. |
Are you using Proguard on your project? If so, it would be useful to see what your We haven't seen this particular problem before with the PayPal SDK, but that doesn't rule out issues. |
No. It also happens in the debug environment too, where we don't use default proguard as well... |
Yes It happens in the debug environment for me too, recently |
Ok i solved by changing in Project build.grandle classpath 'com.android.tools.build:gradle:+' with classpath 'com.android.tools.build:gradle:1.3.0' |
Ah, I have tried that |
I think I found some trigger that could probably give a perspective: |
Seeing the same issue. I just updated platform/sdk tools and I'm using com.android.tools.build:gradle:1.4.0-beta5 |
Please let us know if you are still experiencing this issue with the recently released |
I'm seeing the same issue with 1.7.0 of the braintree sdk when using 1.4.0-beta5 build tools. If I switch back to 1.3.1 build tools, it works fine. |
We have confirmed this issue is caused by Thanks everyone for the report and information. |
Same issue here with braintree-api:1.7.1 and com.android.tools.build:gradle:1.4.0-beta6 |
@fred8: please see the previous comment. |
The issue is with the 1.4.0-beta6 build tools not supporting classes that are only different through different capitalization. The PayPal SDK has classes named both |
See this tools issue already tracking the problem. |
Hi, I faced that there was a conflict issue with Google Play Service plugin. |
@gcalaprice if |
Another option would be to not use classes that are only different by letter capitalization with |
Agreed about the proguard workaround. At the suggestion of @plastiv, we'll go ahead and do this, and publish a new PayPal release sometime shortly (few days). We have other Android 23 changes coming too that we'd like to deliver with that, so please understand the delay. |
I see there was a 2.11.0 PayPal SDK release using -dontusemixedcaseclassnames. When will there be a Braintree SDK please which uses this version? |
Same issue here. Can you tell me when the updates for braintree is coming? Because i won't use the proguard workaround if it is coming early, like tomorrow or something. |
The |
braintree_android 1.7.2 was just released with a version of the PayPal SDK that uses It should be available on maven in a few hours. |
I got the very same error with latest braintree update (1.7.2)Here is my build.gradle file:
Error is:
... and so on for many classes in paypal SDK. |
Hi There is absolutely no problem in your build.gradle file, // Top-level build file where you can add configuration options common buildscript {
} allprojects { |
1.7.2 resolves the problem for me (using android grade plugin 1.4.0-beta6). |
@anilkumarGL I do have gradle 1.3.1 so the problem is lays elsewhere. I just realized you wrote previously that if a project contians
Then this error will still present. Actually i do use google play services. Is there no workaround to make braintree android sdk work with google play services? Maybe previous builds or something..? |
@adamvarhegyi , for me this is working fine for me.. |
@adamvarhegyi have you synced and cleaned/rebuilt your project? There is no longer an |
Thanks guys for all the help, i had 2 problems the first was solved with the new braintree sdk release. The release is working perfectly, thanks for your time. |
Thank you sooooo much!! you giveme a clue to solve my problem |
The text was updated successfully, but these errors were encountered: