Unanswered question

Not able to record mobile application

Hello Team,

I did few steps for recording mobile application
1. Installed certificate in Android Device.
2. Controller and Android Device both are in same wifi network
3. In Android Device wifi advance setting select manual proxy Host Name : controller IP and proxy is 8090.
4. Controller recording options start client is disabled, and click on start recording.

In recording tool bar we identify warning message like
The request "xxxx.xxxx.xxx" has returned a missing certificate error.

Thanks in Advance,

CHINNIKRISHNA REDDY B.
CHINNIKRISHNA REDDY B.

CHINNIKRISHNA REDDY B.

Level
1
163 / 750
points

Answers

Did you get that error recording a native mobile application or from the browser in your mobile? If the former please try with the browser on the mobile and check if you can record any HTTPS web site without having a certifcate error?

What is your Android version?

CHINNIKRISHNA REDDY B.
CHINNIKRISHNA REDDY B.

CHINNIKRISHNA REDDY B.

Level
1
163 / 750
points

Hello Nouredine,
Thanks for reply, Able to record HTTPS web site in Mobile Browser.

Android Version :- 9

But when you recorded the HTTPS traffic did you get any SSL warning from the browser?

The goal is to make sure that the NeoLoad ROOT certificate is used by the browser. If it's the case then most likely your recording issue with i guess your native application is due to the fact that in Android 9 the user imported certificate are not trusted by default. You can check the neoload.log file for any unknown_certificate error. If it's the case then you need to modify the apk of your application to allow the use of user certificate like explained here

CHINNIKRISHNA REDDY B.
CHINNIKRISHNA REDDY B.

CHINNIKRISHNA REDDY B.

Level
1
163 / 750
points

Error message like below

2019/10/01 15:19:58 WARN - com.neotys.net.proxy.f.h: Exception during the recording 232 javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at com.neotys.net.proxy.d.h.a(h.java:40)
at com.neotys.net.proxy.d.h.a(h.java:139)
at com.neotys.net.proxy.d.j.<init>(j.java:33)
at com.neotys.net.proxy.f.h.b(h.java:384)
at com.neotys.net.proxy.f.h.i(h.java:257)
at com.neotys.net.proxy.f.h.call(h.java:213)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)