Tyrrrz / Tyrrrz/YoutubeExplode
Fix for the Issue #938 broken in v6.6.2
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 592
- Avg merge
- 3h 4m
- Merged PRs (30d)
- 1
Description
Version
6.6.2
Environment
Windows 11 25H2 26200.9168
Steps to reproduce
- Create a sample UWP app native project
- Add Nuget reference of youtubeexplode 6.6.1/6.6.2
- Build the project in Release x64/x86 with .NET Native tool chain compilation enabled.
The compilation fails with Internal compiler error: Sequence contains more than one element.
This breaks the fix for #938 - Downgrade System.Text.Json to 9.0.2 for UWP .NET Native Toolchain compatibility by @Copilot in #938
Details
Adding YoutubeExplode v6.6.2 in UWP projects should not break the UWP .NET Native Toolchain compatibility.
This works for the package 6.6.0
Checklist
- I have looked through existing issues to make sure that this bug has not been reported before
- I have provided a descriptive title for this issue
- I have made sure that this bug is reproducible on the latest version of the package
- I have provided all the information needed to reproduce this bug as efficiently as possible
- I have sponsored this project
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 failure in a sample UWP native project using YoutubeExplode 6.6.2, with Release x64 or x86 and the .NET Native toolchain enabled. Compare the build with version 6.6.0 and the versions affected by #938. Done means UWP projects build successfully with YoutubeExplode 6.6.2 without the “Sequence contains more than one element” compiler error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100