Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open unscanned files via intent #115

Open
7 tasks done
Aga-C opened this issue Jan 19, 2025 · 1 comment
Open
7 tasks done

Can't open unscanned files via intent #115

Aga-C opened this issue Jan 19, 2025 · 1 comment
Labels
bug Something is not working

Comments

@Aga-C
Copy link
Member

Aga-C commented Jan 19, 2025

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 14

Affected device model

OnePlus 9 Pro

How did you install the app?

GitHub releases

Steps to reproduce the bug

Pre-requisite: ensure that Music Player has been opened at least once and has some scanned media in it.

  1. Create or download any music file in a directory visible in Music Player. Don't turn on Music Player at this moment, so the file isn't scanned.
  2. From a file management app, open that file in Music Player

Expected behavior

The app should play the file.

Actual behavior

The file isn't played. Instead, another file from the device is played.

Additionally, a toast is shown with an error: Error: java.lang.NullPointerException: getStringValue(..) must not be null.

Screenshots/Screen recordings

No response

Additional information

No response

@Aga-C Aga-C added the bug Something is not working label Jan 19, 2025
@IsHacker003
Copy link

I have the same issue. It also displays the toast "An unknown error occured". Does somebody have a solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

No branches or pull requests

2 participants