SSL handshake failed at /Users/nghiatran/etcetc

Open
#1,450 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, swift

Research direction

Start with the reported Android development setup and the screenshot, then inspect the referenced swift-nio-ssl path at Sources/CNIOBoringSSL/ssl/tls_record.cc:594. Reproduce the SSL handshake failure and determine whether the displayed path is only a diagnostic mismatch or indicates another problem; document the finding and a verified outcome.

Written by the indexing model from the issue text.

Description

question

Description

I'm trying to nset up an android device for development here, and my SSL handshake failed.

What I found interesting was that the error path does not exist on my machine!

image

/Users/nghiatran/Library/Developer/Xcode/DerivedData/NSProxy-chrjhjrygpkcrggquryyaaqcgvhz/SourcePackages/checkouts/swift-nio-ssl/Sources/CNIOBoringSSL/ssl/tls_record.cc:594

@NghiaTranUIT Is this just a display bug, or is something else going on?

Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProxymanApp/Proxyman

All issues in ProxymanApp/Proxyman

Similar issues

More Mobile Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.