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

"Please sign in" Unable to play music #1692

Open
3 of 4 tasks
darkdevil86 opened this issue Oct 29, 2024 · 36 comments
Open
3 of 4 tasks

"Please sign in" Unable to play music #1692

darkdevil86 opened this issue Oct 29, 2024 · 36 comments
Labels
bug Something isn't working

Comments

@darkdevil86
Copy link

darkdevil86 commented Oct 29, 2024

Checklist

  • I am able to reproduce the bug with the latest debug version.
  • I've checked that there is no open or closed issue about this bug.
  • This issue contains only one bug.
  • The title of this issue accurately describes the bug.

Steps to reproduce the bug

  1. Search for any music
  2. click on play button
  3. It's showing "Please sign in"

Expected behavior

It should play music!

Actual behavior

It's should play music even application running in background.

Screenshots/Screen recordings

Screenshot_2024-10-29-08-19-36-88_f4703f2d42345ac28c56f11a6100c500

Logs

n/a

InnerTune version

0.5.10

Android version

Android 13

Additional information

No response

@darkdevil86 darkdevil86 added the bug Something isn't working label Oct 29, 2024
@loignon
Copy link

loignon commented Oct 29, 2024

I have the same issue on Android 14 and InnerTune 0.5.10 I will add that cached and offline songs still play correctly.

Funny to see that I tried playing the same song 🙂

@Hydrapralix
Copy link

Had the same issue. May have a look into #1653

@Amazing-Stardom
Copy link

I have the Same issues

@Paa8732
Copy link

Paa8732 commented Oct 29, 2024

I have the same issue

@Miner2003ia
Copy link

Miner2003ia commented Oct 30, 2024

I just changed the version And I get this problem when before That didn't happen @z-huang

@M00NJ
Copy link

M00NJ commented Oct 30, 2024

Everybody has this and it has nothing to do with InnerTune. It's YouTube forcing logins to kill off alternative front-ends and prevent Ad-blocking. Since InnerTune uses the official YouTube API this will be hard to fix long term, since YouTube is actively working on breaking it. Maybe something like Invidious is worth thinking about.

@choozn
Copy link

choozn commented Oct 31, 2024

It works for me

Cached songs are not affected by this.

@choozn
Copy link

choozn commented Oct 31, 2024

Duplicate of #1653.

@ulite-Amr
Copy link

I have the same issue @z-huang

@DNIKETAN2057
Copy link

Same issue kindly solve this bug

@DNIKETAN2057
Copy link

Screenshot_20241031_204316_InnerTune

@RuneCE
Copy link

RuneCE commented Oct 31, 2024

Everybody has this and it has nothing to do with InnerTune. It's YouTube forcing logins to kill off alternative front-ends and prevent Ad-blocking. Since InnerTune uses the official YouTube API this will be hard to fix long term, since YouTube is actively working on breaking it. Maybe something like Invidious is worth thinking about.

No it's already been fixed a long while ago lol - they just aren't/haven't released the change to the "releases" page everyone checks & downloads InnerTune from.
You have to use a slightly different method to get the fixed version.

@simplycod
Copy link

Everybody has this and it has nothing to do with InnerTune. It's YouTube forcing logins to kill off alternative front-ends and prevent Ad-blocking. Since InnerTune uses the official YouTube API this will be hard to fix long term, since YouTube is actively working on breaking it. Maybe something like Invidious is worth thinking about.

No it's already been fixed a long while ago lol - they just aren't/haven't released the change to the "releases" page everyone checks & downloads InnerTune from.
You have to use a slightly different method to get the fixed version.

What's keeping you from telling us the solution?
If there is a solution, please share it.
And thank you in advance

@RuneCE
Copy link

RuneCE commented Nov 1, 2024

Everybody has this and it has nothing to do with InnerTune. It's YouTube forcing logins to kill off alternative front-ends and prevent Ad-blocking. Since InnerTune uses the official YouTube API this will be hard to fix long term, since YouTube is actively working on breaking it. Maybe something like Invidious is worth thinking about.

No it's already been fixed a long while ago lol - they just aren't/haven't released the change to the "releases" page everyone checks & downloads InnerTune from.
You have to use a slightly different method to get the fixed version.

What's keeping you from telling us the solution? If there is a solution, please share it. And thank you in advance

Apologies for that!
Either go to "Actions" and use a debugging build, it may contain bugs and such, as those are not production releases - but I doubt you will notice anything, especially with just normal use!
Click Here for the direct download link to skip you the hassle of going through Actions tab.

You can also fork the project if you like, this allows you to take more control over the project by editing the code, adding tweaks of your own, etc - so the finished APK you create is perfect for your liking.

⚠️ NOTE: Just in case - on your current InnerTune, make sure to go to Settings > "Backup and Restore" > and backup your data so you can restore all your music.

Happy listening and have a blessed day, you can reply to this if you want to say anything! :)

@dt192
Copy link

dt192 commented Nov 1, 2024

This doesn't solve the issue for me, still asks for sign in

@RuneCE
Copy link

RuneCE commented Nov 1, 2024

This doesn't solve the issue for me, still asks for sign in

Is that directed at what I posted?
If so, I am not too sure what to tell you, you might be doing it wrong or using the wrong application? Uninstall every InnerTune application you have and freshly download InnerTune Debug (v0.5.10)
Unzip (extract) the .ZIP and install the APK.

@dt192
Copy link

dt192 commented Nov 1, 2024

Ok thanks, that did solve it. I had uninstalled and reinstalled the debug version and assumed that would clear the cache and data, but apparently I needed to clear the cache and data before uninstalling and reinstalling.

@RuneCE
Copy link

RuneCE commented Nov 1, 2024

Ok thanks, that did solve it. I had uninstalled and reinstalled the debug version and assumed that would clear the cache and data, but apparently I needed to clear the cache and data before uninstalling and reinstalling.

Ah, very strange... well, at least it worked at the end! Hooray!

@me-santu
Copy link

me-santu commented Nov 1, 2024

Same issue please give me innertune debug apk link

@PrecutCeiling64
Copy link

Mine got fixed after logging in with a fresh account.

@RuneCE
Copy link

RuneCE commented Nov 2, 2024

Same issue please give me innertune debug apk link

It's linked twice above right about your message xD (blue text: like this)

@RuneCE
Copy link

RuneCE commented Nov 2, 2024

Mine got fixed after logging in with a fresh account.

That is the problem... we don't want to login & avoid as many Google services as we can. xD.
Which this method bypasses.

@ecv80
Copy link

ecv80 commented Nov 2, 2024

Mine played for a few dozen seconds then got the logging error and never worked again no matter what. Happened on 0.5.6, updated to 0.5.10 on fdroid. Same.

Logging in didn't do anything for me. I'm gonna try deleting cache and data and installing the linked apk. It's a pity to lose the history tho.

@dt192
Copy link

dt192 commented Nov 2, 2024

@ecv80 The above is a separate app, so no need to delete the main app or clear that data/cache

@RuneCE
Copy link

RuneCE commented Nov 2, 2024

Mine played for a few dozen seconds then got the logging error and never worked again no matter what. Happened on 0.5.6, updated to 0.5.10 on fdroid. Same.

Logging in didn't do anything for me. I'm gonna try deleting cache and data and installing the linked apk. It's a pity to lose the history tho.

What dt192 said above + you can just backup your data (Settings > Backup and Restore > backup) then restore it in the debug version.

@PrecutCeiling64
Copy link

Mine got fixed after logging in with a fresh account.

That is the problem... we don't want to login & avoid as many Google services as we can. xD. Which this method bypasses.

Ohh gotcha 👍

@xgiulibix
Copy link

Mine got fixed after logging in with a fresh account.

That is the problem... we don't want to login & avoid as many Google services as we can. xD. Which this method bypasses.

Hey, the debug version crashes when I search for new songs. The ones I have in my library reproduce just fine. Is there an issue where this is discuss? An alternative option to solve this?

@RuneCE
Copy link

RuneCE commented Nov 4, 2024

Yeah, wouldn't trust a random guy advertising a fork of this app, but, just being published on the PlayStore, likely with no permission...

@RuneCE
Copy link

RuneCE commented Nov 4, 2024

lol, yeah, checked his profile, he closed-sourced his fork & published it to the PlayStore, pretty scummy.

No credit, no nothing, just his donation links and such, proof of a screenshot attached on the PlayStore:
AA952F8C-3380-4D20-9AF9-49C48626833C

@choozn
Copy link

choozn commented Nov 4, 2024

This bug has been fixed in the latest version of Innertune, if you have not been able to compile the new version from Android studio, you can download a fork of Innertune that I made from Google Play
https://play.google.com/store/apps/details?id=com.josprox.jossmusic

This way you can continue enjoying the player until a new version is uploaded to the repository. 🫶🏻

🤡🤡🤡

@ecv80
Copy link

ecv80 commented Nov 4, 2024

lol, yeah, checked his profile, he closed-sourced his fork & published it to the PlayStore, pretty scummy.

No credit, no nothing, just his donation links and such, proof of a screenshot attached on the PlayStore: AA952F8C-3380-4D20-9AF9-49C48626833C

Well that's illegal so at the very least Google should remove it from the app store if the author requests it, which he should.

@Malopieds
Copy link
Contributor

Well that's illegal so at the very least Google should remove it from the app store if the author requests it, which he should.

It's actually not illegal to publish a fork of this software to the playstore. The GPL3 license states that you can modify this code and publish it as you want. This is at most immoral to not give credits. The thing that would be illegal is that the code source is closed, which violates another part if the GPL3.

In the end this would still be illegal but:
1- google won't do anything
2- you don't want google anywhere near those apps since they're trying to get rid of them

@ecv80
Copy link

ecv80 commented Nov 16, 2024

Well that's illegal so at the very least Google should remove it from the app store if the author requests it, which he should.

It's actually not illegal to publish a fork of this software to the playstore. The GPL3 license states that you can modify this code and publish it as you want. This is at most immoral to not give credits. The thing that would be illegal is that the code source is closed, which violates another part if the GPL3.

In the end this would still be illegal but: 1- google won't do anything 2- you don't want google anywhere near those apps since they're trying to get rid of them

I wasn't sure I should bother replying but what the heck, if I'm heavily invested in politics I will as well just go with this.

I have the feeling you were thinking as you wrote instead of before you wrote. I said that's illegal and then you go on to comment on how it "actually" is not and at most just immoral to finally admit that it is illegal. Well thanks for the detailed remarks on why it is illegal but I was well aware of these. Forking does not magically get you rid of your due obligation of keeping the GPL license and the source open. If you publish a GPL work, fork or not, without the license and without the source code, you're breaking the license and that's illegal, period. No need for remarks on how it is actually not illegal to fork it. Nobody said it's illegal to just fork it.

  1. I don't know if Google usually acts upon copyright infringement -like claims or even reasonably quick. But I suspect they don't refuse to as doing so would turn them into necessary co-perpetrators before a judge.

1731748546448162450205506390924

@vivek551
Copy link

Anyone has the please sign in fixed fork...?

@James-Oakley
Copy link

Either go to "Actions" and use a debugging build, it may contain bugs and such, as those are not production releases - but I doubt you will notice anything, especially with just normal use! Click Here for the direct download link to skip you the hassle of going through Actions tab.

So if this is fixed, and the fix is committed, where is this at? Is there anything stopping the maintainer tagging and packaging a new release?

@TruongTanLuc201270
Copy link

Please see #1653 because not to be fixed yet.

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

No branches or pull requests