ProHzen / ksoap2-android

Automatically exported from code.google.com/p/ksoap2-android
0 stars 0 forks source link

java.lang.RuntimeException #167

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. trying to call SOAP Api and getting following exception
2. issue only on Samsung Stratosphere phone
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

java.lang.RuntimeException: An error occured while executing doInBackground()
    at android.os.AsyncTask$3.done(AsyncTask.java:200)
    at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:274)
    at java.util.concurrent.FutureTask.setException(FutureTask.java:125)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:308)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
    at java.lang.Thread.run(Thread.java:1019)
Caused by: java.lang.NoSuchMethodError: 
org.ksoap2.serialization.SoapObject.getPropertySafely
    at us.bnn.bean.BNNConvertor.getMyRole(BNNConvertor.java:450)
    at us.bnn.bean.BNNManager.getMyRole(BNNManager.java:738)
    at us.bnn.news.LoginActivity$MyRolesAsync.doInBackground(LoginActivity.java:659)
    at us.bnn.news.LoginActivity$MyRolesAsync.doInBackground(LoginActivity.java:1)
    at android.os.AsyncTask$2.call(AsyncTask.java:185)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
    ... 4 more

Original issue reported on code.google.com by izzy@breakingnewsnetwork.com on 5 Jul 2013 at 10:18

GoogleCodeExporter commented 8 years ago
I noticed the issue is only with phones that the 
OS: 2.6.35.7-1166103(10)
Model: SCH-I405

Original comment by izzy@breakingnewsnetwork.com on 6 Jul 2013 at 2:51

GoogleCodeExporter commented 8 years ago
Well. The method clearly exists so it must be some sort of problem related to 
your proguard config or whatever.

Original comment by mosa...@gmail.com on 19 Oct 2013 at 2:31