-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 not find [email protected] in Nuget.org #13369
Labels
Comments
microsoft-github-policy-service
bot
added
the
Needs: Triage 🔍
New issue that needs to be reviewed by the issue management team (label applied by bot)
label
Jun 20, 2024
Hi @oudi , there were some problems on our end with getting the NuGet published on time with the NPM release. 0.74.9 has just published and should be available in a couple hours. |
chrisglein
added
the
Needs: Author Feedback
The issue/PR needs activity from its author (label drives bot activity)
label
Jun 24, 2024
@oudi This should be resolved for you. Let us know if not. |
microsoft-github-policy-service
bot
removed
the
Needs: Triage 🔍
New issue that needs to be reviewed by the issue management team (label applied by bot)
label
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem Description
Can not find [email protected] in Nuget.org after npx react-native-windows-init latest , the version of react-native-windows is 0.74.9, when running
npx react-native run-windows
error NU1102 Microsoft.ReactNative, the version of https://www.nuget.org/packages/Microsoft.ReactNative/ is 0.74.8, forget something you guys?Steps To Reproduce
npx react-native-windows-init --language cs --version latest --overwrite --experimentalNuGetDependency
Expected Results
No response
CLI version
0.74.0
Environment
Community Modules
No response
Target Platform Version
None
Target Device(s)
No response
Visual Studio Version
None
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: