Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Quest: device-code login shows nothing in the headset (player cannot see URL or code)

Closed
  • Is something wrong?
#239 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #326 by @thesprockee — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
authentication, mobile

Research direction

Start with the sentinel's auth state machine, where the state moves from starting to awaiting_user, and with the device_login.txt write under the Android app files path. Read the PCVR token-auth flow from PR #223 to see how it presents the URL, code and expiry. Done means a Quest player sees the login URL, code and expiry while the state is awaiting_user, and the game holds its login until the state becomes ready. The design choice about the dialog and the wait behaviour needs maintainer input first.

Written by the indexing model from the issue text.

Description

Problem

On Quest the device-code login gives the player no visible prompt. The sentinel writes device_login.txt under /sdcard/Android/data/com.readyatdawn.r15/files/ and asks Android to open a browser ([NEVR.AUTH] browser open requested ... open_result=33 (accepted)), but nothing appears in the headset. The player has no way to know a login is waiting, or what URL and code to use.

Evidence (smoke test 2026-10-08, integration build, Quest 2)

  • [NEVR.AUTH] auth state starting -> awaiting_user at 18:39:38, the game continued to its own login and reached NetGame switching state (from login failed, to logged out) at 18:40:38 while the player knew nothing about a login.
  • The owner (who ran the test): "i authorized the login, but i had no way to know there was a login thing. i think we need to trigger the dialog to tell the user to go to echovrce.com/login/device and type the code in."

Wanted

An in-headset prompt shown while the state is awaiting_user, carrying the URL and the code and the expiry, visible to a player wearing the headset. PCVR shows its own flow in the token-auth module; Quest needs the equivalent. Also decide what the game does during the wait (hold its login until ready).

Found by the Quest smoke test; related PR: #223 (token auth).

Dominant language
C++
Stars
2
Forks
3
Avg merge
9h 33m
Merged PRs (30d)
436

Getting set up

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 EchoTools/nevr-runtime

All issues in EchoTools/nevr-runtime

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.