[com.google.android.youtube] Crash when using old versions of the old YT App, regardless of Vanced, OGYouTube or vanilla YouTube
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Affected app
Name: [YouTube]
Package id: [com.google.android.google]
Describe the bug
microG seems to be incompatible with old versions of the YouTube app now, which wasn't the case when I last tested it a year ago. I tested it on OGYouTube v12.43.52, YouTube Vanced v14.21 and Vanilla YouTube v14.42. Either the app crashes after a few seconds or it displays a loading circle into infity despite sucessful requests to the YouTube servers. This doesn't occur with official GMS.
To Reproduce
Steps to reproduce the behavior:
- Install an old version of the YouTube app, for example v14.42
- Try to open it
- It will crash after a few seconds
Expected behavior
The app staying open on the 400 - Precondition check failed error that InnerTube returns, or showing the UI if the app is spoofed to allow sucessful API requests
System
Android Version: [13]
Custom ROM: [Kenvyra OS 13]
microG
microG Core version: 0.2.28.233013-49
microG Self-Check results: All ticked
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the crash with YouTube v14.42, OGYouTube v12.43.52, or Vanced v14.21 on Android 13 using microG Core 0.2.28.233013-49, then compare the behavior with official GMS. Check whether the apps consistently crash or loop after the InnerTube 400 response; done means the old app remains open as described or displays its UI when API requests succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100