The application receives data from the web service. The procedure for receiving data is launched in the service. On a device with Android 4.4.0, everything works correctly. On the emulator, under Android 6.0 falls.

SoapSerializationEnvelope soapEnvelope = new SoapSerializationEnvelope(SoapEnvelope.VER12); soapEnvelope.dotNet = true; soapEnvelope.setOutputSoapObject(soap_request); soapEnvelope.implicitTypes = true; List<HeaderProperty> headers = new ArrayList<HeaderProperty>(); headers.add(new HeaderProperty("Authorization", "Basic "+ Base64.encode(loginpassword.getBytes(Charset.forName("UTF-8"))))); HttpTransportSE transport = new HttpTransportSE(URL,120000); transport.debug = true; transport.call(SOAP_ACTION, soapEnvelope, headers);

The fall does not happen immediately, but a few seconds after the launch of the request. Approximately it looks like the time the server needs to respond. I would be glad if you kick in the right direction.

The log is very large, so I will give only the beginning:

 08-23 08:56:32.091 12612-12617/soap.watersmith.ua.soap A/art: art/compiler/dex/mir_method_info.cc:104] Check failed: invoke_type == kVirtual (invoke_type=direct, kVirtual=virtual) 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] Runtime aborting... 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] Aborting thread: 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] "Jit thread pool worker thread 0" prio=5 tid=2 Runnable (still starting up) 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] | group="" sCount=0 dsCount=0 obj=0x0 self=0xac2cf200 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] | sysTid=12617 nice=0 cgrp=default sched=0/0 handle=0xb2b2b930 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] | state=R schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] | stack=0xb2a2e000-0xb2a30000 stackSize=1018KB 08-23 08:56:32.176 12612-12617/soap.watersmith.ua.soap A/art: art/runtime/runtime.cc:366] | held mutexes= "abort lock" "mutator lock"(shared held)

The entire log on pastebin link: http://pastebin.com/Fe1z4FrP

I changed targetSDK in the manifest to 23, (before it was 17) The log volume dropped significantly when it fell. Moreover, sometimes the fall does not happen immediately after receiving the server's response, but a bit later, like on the screenshot: http://prnt.sc/c9dop4

  • one
    Look through the debugger that is contained in the answer. try {transport.call (SOAP_ACTION, soapEnvelope, headers) SoapObject resultsString = (SoapObject) envelope.getResponse (); } catch (Exception e) {e.toString (); } - Ivan Vovk
  • try - cath did not help immediately after transport.call (SOAP_ACTION, soapEnvelope, headers); On SoapObject resultsString = (SoapObject) soapEnvelope.getResponse (); departure takes place. The error does not fall into the cath. - Sergey Vodakov
  • 3
    Judging by the text of the error, not the java-code "falls", but the virtual machine itself, i.e. This is a bug in the emulator. - Roman

1 answer 1

Judging by the text of the error, not the java-code "falls", but the virtual machine itself, i.e. This is a bug in the emulator. - Roman 55 min. backwards

The problem really was in the emulator. Friends, do not repeat my mistakes, do not ignore the requests of the studio to be updated. After updating "Google APIs Intel x86 Atom System Image 23" from revision 7 to 16! It all worked.