-
-
Notifications
You must be signed in to change notification settings - Fork 16
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 fetch any data #217
Comments
Thank you for reporting this. I’ve been running into it too. I’ll take a
look asap
…On Wed, 13 Nov 2024 at 04:45, Adrian Vovk ***@***.***> wrote:
App doesn't seem to be able to load any content anymore. I deleted the
app's data dir and recreated it to try and work around the problem, signed
in again, but the problem still persists. Any page I try to open in the app
leads to the same error message:
MuseError: Can't fetch data
{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"errors": [
{
"message": "Request contains an invalid argument.",
"domain": "global",
"reason": "badRequest"
}
],
"status": "INVALID_ARGUMENT"
}
}
***@***.***:///com/vixalien/muzika/js/main.js:9737:5
***@***.***:///com/vixalien/muzika/js/main.js:11274:15
***@***.***:///com/vixalien/muzika/js/main.js:11282:26
***@***.***:///com/vixalien/muzika/js/main.js:11309:24
***@***.***:///com/vixalien/muzika/js/main.js:19286:12
***@***.***:///com/vixalien/muzika/js/main.js:24757:38
***@***.***:///com/vixalien/muzika/js/main.js:24787:17
***@***.***:///com/vixalien/muzika/js/main.js:24916:17
***@***.***:///com/vixalien/muzika/js/main.js:24897:16
***@***.***:///com/vixalien/muzika/js/main.js:32528:14
***@***.***:///org/gnome/gjs/modules/script/package.js:207:19
@file:///app/bin/com.vixalien.muzika.Devel:22:40
@file:///app/bin/com.vixalien.muzika.Devel:28:6
The app also logs the following to the terminal:
Gjs-Console-Message: 21:43:55.533: caching soup requests at /var/home/adrian/.var/app/com.vixalien.muzika.Devel/cache/com.vixalien.muzika.Devel/soup-cache
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
(com.vixalien.muzika.Devel:2): Gjs-Console-CRITICAL **: 21:43:56.236: Couldn't get logged in user
(com.vixalien.muzika.Devel:2): Gjs-WARNING **: 21:43:56.238: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed ***@***.******@***.***:///org/gnome/gjs/modules/script/package.js:207:19
@file:///app/bin/com.vixalien.muzika.Devel:22:40
@file:///app/bin/com.vixalien.muzika.Devel:28:6
Troubleshooting information:
{
"argv": [
"/app/bin/com.vixalien.muzika.Devel"
],
"version": "nightly-67afe41",
"uri": "library:playlists",
"logged_in": true,
"language": "English (US) - en"
}
—
Reply to this email directly, view it on GitHub
<#217>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJB5FCOTNN45WPM53GG3UOT2AK4MVAVCNFSM6AAAAABRVNIFLKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY2TGOJVGQYTKNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Same error here. |
This is due to a change on how YouTube handles authentication. Sadly, I don't know of any methods to use the new authentication scheme, but it seems they now use an Authorization Header with Someone needs to reverse engineer this hash, but it's different from the old SAPISIDHASHs because the current ones all end with |
Furthermore, YTM now requires you to be logged in before playing anything on iOS and Android, meaning our old method to play songs while not logged in won't work, i.e. unless we figure out how to decipher the streams YTM sends on browser ( |
I don't know if it's related bu spotify_to_ytmusic is using browser auth instead of oauth. Is this helpful? |
Same with youtui. They are switching to browser auth nick42d/youtui@b206a8e |
is there any update on this? |
App doesn't seem to be able to load any content anymore. I deleted the app's data dir and recreated it to try and work around the problem, signed in again, but the problem still persists. Any page I try to open in the app leads to the same error message:
The app also logs the following to the terminal:
Troubleshooting information:
The text was updated successfully, but these errors were encountered: