-
Notifications
You must be signed in to change notification settings - Fork 602
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
update electron & remote & user agents #515
Conversation
94e8214
to
3425767
Compare
3425767
to
dd12266
Compare
Logging in is still pretty jank. I had to clear my data (or as much as I could), then try to sign in, then switch into my own account, then hard refresh. The home page is, for some reason, still showing the generic home page but now I get access to my library. I swore there was Chromecast support but I guess I might've dreamt it up. |
Correction, now it shows my front page after navigating around. |
And now opening and closing it breaks it again. Google really doesn't want us embedding YTM huh? |
@WhiteHusky It really should work now, did you update dependencies using |
Login worked for me instantly. Although there were no navigation items except for search, after returning back to home page. |
Okay nvm. They are having the same issue now. Seems like this is a common problem suddenly appearing with Electron apps, maybe? |
It is indeed an electron problem that has nothing to do with the app. see electron/electron#22346 (comment) this PR kinda works for some reason - it will try the first time with the normal mode, then if it fails it switches to the "One account. All of Google" mode, which works but if used then for unknown reasons it breaks the navigation until the app is restarted (but it stays logged in so the only problem is the navigation bug after log in) |
Is it possible to force a restart after successful login in the second case? If so, I would say that it is an acceptable workaround. On another note regarding this PR: a273f6f is out of scope in my opinion. Or does it have anything to do with the initial problem or resulting issues? I am guessing the simultaneous update to electron was needed for the remote package to work? (4 major versions is pretty big) |
Latest version actually works good for me when built and installed (still buggy in dev mode)
Well yes but its just that suddenly with the new electron version
More like the update to the remote package was needed because of the electron update.
|
@KIMBUM here are windows binaries with the latest changes try installing via the setup this time |
@Araxeus works like you said. First time failed, but second time works fine. Navigation also showed up for me, since reload seemed to happen automatically. I did notice however, that the disable-autoplay plugin seems to be broken now. Stops each time I try to press play 😞 |
Seems to work some of the time when the tooltip for "press to play" appears, but even though I just reinstalled it, the tooltip is not shown for the first startup 🤨 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix, tested on MacOS, looks promising! But I would separate the electron upgrade which might require more work
@th-ch Sorry but I really can't separate it now since remote doesn't work for me anymore no matter what I do
@KIMBUM I actually can't replicate anything? could you check again maybe>
@th-ch this useragent isn't really doing much, the actual fix is that when it fails (some accounts are shadowbanned) - it tries again with the original useragent which does work currently if login initially fail Lines 185 to 191 in 8f2ed30
|
* --experimental-wasm-bulk-memory * SharedArrayBuffer * getFolder from front * ytdl-core 4.9.2
All thats left is that disable-autoplay bug that I can't personally replicate. can anyone look into it? Its also worth noting that the portable version of the app / dev version has a bug in those 2 scenarios:
in which all navbar items disappear except the search button: No idea why would it ever happen, but it never happens if the app is installed - so maybe whenever you release a new version you should consider not including the portable version or add a warning? (According to my testing, this bug has no relation to the useragent, which makes sense since installing gets rid of it) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for the fix and the upgrade! Merging, will release a new version with all the recent changes
Update electron https://www.electronjs.org/blog/electron-16-0#end-of-support-for-12xy
which requires updating the remote package in this app as well as in custom-electron-prompt and custom-electron-titlebar
which caused some downloader bugs that needed fixing in commit baeebd1
Fix for logging in when account is "shadowbanned" (browser not secure error)
fix #507, fix #526, fix #17, fix #8, fix #327