mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1754] "Failed to start the audio device" error on iOS #965
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#965
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @davinci-klod on GitHub (Mar 7, 2024).
Original GitHub issue: https://github.com/koel/koel/issues/1754
Describe the bug
Hi,
I'm facing an issue. When I'm trying to play a song on iOS, nothing happens. On my console, here's the error prompted :
I tested to use x_sendfile to solve this issue but It was not the solution in my case. The problem happens in Safari, Chrome and Firefox, but not on Desktop. I'm not using the mobile app, just simply trying to use Koel via browser.
Could you help me with this please ? Thanks you !
To reproduce
Simply trying to play a song on a iOS device.
Expected behavior
Songs playing on a iOS device.
Environment
@phanan commented on GitHub (Mar 10, 2024):
This likely is related to mobile Safari's (including Chrome and Firefox, as they're just Safari on iOS) strict policy when it comes to the AudioContext. At this moment there's very little I can do about this, as it pops up once in a while with a new version of Safari, and it's very inconsistent (works with some and doesn't with others).
May I suggest you look at the mobile app instead? If you can't / don't want to build it, you can always buy it from the AppStore. I know it's a paid product in that case, but it doesn't have this annoying issue (as well as some others as with mobile PWA) and it's a way to further support the project.