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

[BUG] Leading space in offset number causes LRC parse error

Open Beginner friendly
  • Is something wrong?
#1,024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

Start by locating the LRC parsing code and its tests in the Kotlin Android app, then check how the offset tag is parsed when its numeric value has leading whitespace. Reproduce with [offset: 500] and compare with [offset:500]; done means the lyric loads without showing the parse error and the offset is respected.

Written by the indexing model from the issue text.

Description

need confirm

Describe the bug
Player failed to parse LRC files which contains offset number with leading space, like [offset: 500] instead of [offset:500]. The number was set with MiniLyrics on Windows.

To Reproduce
Steps to reproduce the behavior:

  1. Open Gramophone
  2. Play any song with LRC file containing offset tag mentioned above
  3. Open lyric view
  4. See error, entire content of LRC file also displayed

Expected behavior
LRC file loaded properly

Screenshots
Both of my smartphones displays same error. Translation: Failed to parse lyric
Image

Smartphone (please complete the following information):

  • Device: Oppo A5s & Poco M4 Pro
  • OS: Android 8.1.0 (ColorOS V5.2.1) & Android 13 TP1A.220624.014 (HyperOS 1.0.8.0.TKEIDXM)
  • App Version: 1.1.2

Additional context
If I remove leading space, LRC loaded properly and respects offset setting.

  • I will open one issue per bug, follow the issue format and will add [BUG] to the start of my issue title, and I acknowledge that if I don't follow the format, my issue might get closed without further explanation.
Dominant language
Kotlin
Stars
2.3k
Forks
136
Avg merge
1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 FoedusProgramme/Gramophone

All issues in FoedusProgramme/Gramophone

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.