Possible client registration regression on version 0.7.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend-api-design, mobile
Research direction
The issue is a client registration regression in version 0.7.0 compared to 0.6.0. Start by examining the registration flow in the codebase, focusing on changes between these versions. Look for network handshake logic, error handling, and any new authentication or API calls. Reproduce the issue by building both versions and comparing logs during the 'Registering' phase.
Written by the indexing model from the issue text.
Description
Describe the Bug
Today I tried to enroll my new phone (Samsung galaxy zfold ultra) to my pangolin instance. It kept getting hung up on "registering". I went through recreating my pangolin containers several times, wiping storage and VPN profiles for pangolin, checking to ensure all of the required ports are open and receiving on my host, etc. It refused to connect under any circumstance.
I also tried from mobile network and from wifi. I tried changing settings within the pangolin app, and tried multiple DNS settings on the android device.
I uninstalled and reinstalled the android app from the play store, and I cleared the storage: No luck. Finally I uninstalled 0.7.0 and installed 0.6.0 from the releases page here on github, and it registered and connected almost right away.
Environment
- OS Type & Version: Android 17
- Pangolin Version: 1.23
- Edition (Community or Enterprise): Enterprise (personal use)
- Gerbil Version: latest
- Traefik Version: latest
- Newt Version:
- Client Version: 0.7.0
To Reproduce
Unsure exactly; see my description.
AI Disclosure
I didn't use AI to write this.
Expected Behavior
Within the pangolin app, "Registering" should switch to "Connected" with a green dot after the initial handshake. It did not do that under any circumstance.
- Dominant language
- Kotlin
- Stars
- 44
- Forks
- 11
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fosrl/android
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
needs investigating
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Switching organizations breaks Olm hole punching for the same client installationPossibly taken @oschwartz10612 claimed this 6 days ago. Openneeds investigating
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SimonHalvdansson/Harmonic-HN#363 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Automattic/pocket-casts-android#6095 ·
Maintainers usually reply within 1 day