You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting the below error after adding Flipper to the Android application, "Failed to start client connection: Failed to exchange certificate with /APP_NAME/ on Device- 11 - API 30: Error: No matching device found for app"
Below are the connectivity logs from Flipper desktop client,
Certificate Signing Request being processed
Ensure OpenSSL is available
Obtain CA certificate
Deploy CA certificate to application sandbox
Deploying file 'sonarCA.crt' to device at '/data/user/0/package_name/files/sonar/'
Query available devices via adb
cat '/data/user/0/package_name/files/sonar/app.csr'
Unable to find a matching device for the incoming request
Failed to exchange certificate,Error: No matching device found for app: /package_name/
Insecure websocket connection attempt: /app_name/ on unknown.
Insecure connection attempt
Note: The device is not rooted and the application is installed in "system/priv-app" folder
OpenSSL was installed and the same application worked on rooted devices.
Android studio-generated APK is working as expected.
.\gradlew build generated APK with singing is not working as expected.
I am getting the below error after adding Flipper to the Android application,
"Failed to start client connection: Failed to exchange certificate with /APP_NAME/ on Device- 11 - API 30: Error: No matching device found for app"
Below are the connectivity logs from Flipper desktop client,
Note: The device is not rooted and the application is installed in "system/priv-app" folder
OpenSSL was installed and the same application worked on rooted devices.
Android studio-generated APK is working as expected.
.\gradlew build generated APK with singing is not working as expected.
Android version: 11
Windows: 10
Flipper desktop version: 0.239.0
Flipper Android version: 0.190.0
Please provide a solution for this issue.
The text was updated successfully, but these errors were encountered: