1、错误:android.content.res.Resources$NotFoundException
解析:参数类型传错会提示此错误,例如:textView.setText(int i);应该传String类型的值,**textView.setText(String.valueOf(int i));**改成这样就没事了。
2、错误:Caused by: java.lang.UnsatisfiedLinkError: dlopen failed: “/data/app/com.sinofreely.calligraphy-1/lib/arm64/libvudroid.so” is 32-bit instead of 64-bit
解析:arm的so只留下这两个目录:armeabi 和 armeabi-v7a ,其他都删掉。所以把arm-v8的so删掉就好了。
3、错误:SoapFault - faultcode: ‘soap:Server’ faultstring: ‘The given SOAPAction getApplicationEquipmentList does not match an operation.’ faultactor: ‘null’ detail: null
解析:这个错误是我在用ksoap2库请求后台WebService接口时报出的错误,下面是Android的网络请求方法
/**
* webservice请求
* @param wsdl 接口地址
* @param namespace 命名空间
* @param method 接口方法名
* @param json 请求参数
* @return 结果
*/
private String requestWebService(String wsdl, String namespace, String method, JSONObject json){
String result = “”;
SoapObject soapObject = new SoapObject(namespace, method);
if(json!=null)
soapObject.addProperty(“arg0”, json.toString());
SoapSerializationEnvelope soapSerializationEnvelope = new SoapSerializationEnvelope(SoapEnvelope.VER11);
soapSerializationEnvelope.bodyOut = soapObject;
soapSerializationEnvelope.dotNet = false;
HttpTransportSE httpTransportSE = new HttpTransportSE(wsdl,Constants.INSTANCE.getNET_OUT_TIME());
httpTransportSE.debug = true;
//添加HeaderProperty信息,解决调用call的时候报java.io.EOFException错误
ArrayList headerPropertyArrayList = new ArrayList<>();
headerPropertyArrayList.add(new HeaderProperty(“Connection”, “close”));
try {
httpTransportSE.call(method, soapSerializationEnvelope,headerPropertyArrayList);
if(soapSerializationEnvelope.getResponse()!=null){
result = soapSerializationEnvelope.getResponse().toString();
}
} catch (SocketTimeoutException e) {
e.printStackTrace();
result = buildErrorJson(“408”,“请求超时”);
}catch (Exception e) {
e.printStackTrace();
if (TextUtils.isEmpty(result)) {
result = buildErrorJson(“404”, “网络异常,获取数据失败”);
}
}
return result;
}
为什么会出现这个错误呢?先看下咱们是怎样发请求的!首先,SoapObject soapObject = new SoapObject(namespace, method); 这句话配置了namespace(命名空间,学过j2ee的应该都知道,这里不再细述)method(方法名,也就是服务端开放的方法),除了这两个,另外一个重点就是action名称,看这句话httpTransportSE.call(method, soapSerializationEnvelope,headerPropertyArrayList); 这里的method和上一句是同一个对象,也就是说,我这里的接口方法名和action的名字是一模一样的,所以如果后台配置的这两个名字不一样,那就会报上面这个错误信息,后台也不会收到你发的请求,它更不会报错。
**解决方案:**知道原因就好办了,如果你是Android端开发者,可以用浏览器访问wsdl 地址(例如:http://192.168.1.105:8080/delivery/ws/deliveryWsImpl?wsdl )找到要请求的方法名,检查下soapAction的名称是否正确,比如下图的名称 soapAction="getApplicationEquipmentList "多了一个空格,就会导致请求失败
其实还有另一种解决方案,就是请求的时候不传action名,直传方法名,也就是这样**httpTransportSE.call("", soapSerializationEnvelope,headerPropertyArrayList); **第一个参数是空字符串,这样也可以请求成功,不过还是建议第一种方案。
如果想了解下后台是如何配置WebService请求的可以看这里Apache CXF配置
4、Kotlin编译错误:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ‘:app:compileDefault_channelDebugKotlin’.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:103)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:73)
at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:249)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access TaskExecutorWorker TaskExecutorWorker TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl Worker.run(ThreadPoolExecutor.java:617)
at org.gradle.internal.concurrent.ThreadFactoryImpl kotlin_gradle_plugin(Tasks.kt:403)
at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.callCompiler$kotlin_gradle_plugin(Tasks.kt:297)
at org.jetbrains.kotlin.gradle.tasks.AbstractKotlinCompile.execute(Tasks.kt:259)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:50)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:113)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:95)
… 33 more
解析:编译kotlin项目的时候报以上错误基本上是 kotlin代码有错误引起的,有时候在升级AS版本,升级开发环境时也会出现,哪怕之前是正常的。只要我们找到错误的地方改正过来就好了,但从打印的错误日志中我们找不到错误位置怎么办?
解决方法:
1、点击右侧栏gradle标签;
2、选择 :app——build—— assembleDebug(我这里是选择assembleDefault_channel,Default_channel是项目渠道名称)
3、然后底部的Run标签里 可以看到打印的错误日志,从中可以找到代码错误的位置。