microsoft/react-native-gallery

This repo contains the react-native Gallery app created by Microsoft

React Native Gallery

Welcome to React Native Gallery. A React Native Windows application which displays the range of React Native components with Windows support. React Native Gallery is currently live in the Microsoft Store! Follow the link to download.

Building React Native Gallery

If you wish to build React Native Gallery on your computer locally, follow the following steps:

1. Clone the repository.
2. In the root directory of the repository on your device, run yarn.
3. In the same directory run npx react-native run-windows.

Note: First builds will take considerably longer than subsequent builds due to the number of community modules consumed by the React Native Gallery

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

For addtional information about contributing to React Native Gallery visit here.

Adding Sample Pages

To add a sample page:

1. Author your page as a standard RN component and export the component. See https://github.com/microsoft/RNGallery/tree/main/src/examples for existing sample pages
2. Add an entry to the array in the RNGalleryList

import {FooExamplePage} from './examples/FooExamplePage';

export const RNGalleryList: Array<IRNGalleryExample> = [
  ...
  {
    key: 'FooExamplePage',
    component: FooExamplePage,
  },
];

It's that simple! The app will pick up your new sample page, add an item in the navigation draw for it, and navigate to your page when the user clicks on it. If you want a more detailed set of instructions on how to add a page visit here.

react-native-gallery's Issues

Upgrade to 0.63

Currently the app is built against RNW version 62. Upgrade to 63.

Known issues:
-Will need to remove the manual linking of @react-native-communit/checkbox and letting auto-linking do its thing

Changing Theme to dark in app's Settings doesn't do anything

Simple ScrollView doesn't show text scrollbar

The first ScrollView example shows a scrollbar for the whole page but not for the text in the first example:

Image page throws exception under Debug mode

Navigating to the Image page while running the gallery app throws some exceptions.

The exceptions are harmless, that is, if we press "Continue" button to continue execution, then eventually the page does show up, but it's not good for the development experience.

 	KernelBase.dll!00007fffb5c94b89()	Unknown
 	vcruntime140d_app.dll!00007fff887eb1f0()	Unknown
>	Microsoft.ReactNative.dll!winrt::throw_hresult(const winrt::hresult result) Line 4893	C++
 	Microsoft.ReactNative.dll!winrt::check_hresult(const winrt::hresult result) Line 4964	C++
 	Microsoft.ReactNative.dll!winrt::impl::consume_Windows_Foundation_IUriRuntimeClassFactory<winrt::Windows::Foundation::IUriRuntimeClassFactory>::CreateUri(const winrt::param::hstring & uri) Line 755	C++
 	Microsoft.ReactNative.dll!winrt::Windows::Foundation::Uri::<lambda>(const winrt::Windows::Foundation::IUriRuntimeClassFactory & f) Line 2299	C++
 	Microsoft.ReactNative.dll!winrt::impl::call_factory<winrt::Windows::Foundation::Uri,winrt::Windows::Foundation::IUriRuntimeClassFactory,winrt::Windows::Foundation::Uri <lambda>(const winrt::Windows::Foundation::IUriRuntimeClassFactory &)>(winrt::Windows::Foundation::Uri::winrt::Windows::Foundation::Uri <lambda>(const winrt::Windows::Foundation::IUriRuntimeClassFactory &) && callback) Line 6249	C++
 	Microsoft.ReactNative.dll!winrt::Windows::Foundation::Uri::Uri(const winrt::param::hstring & uri) Line 2301	C++
 	Microsoft.ReactNative.dll!react::uwp::UriTryCreate(const winrt::param::hstring & uri) Line 317	C++
 	Microsoft.ReactNative.dll!react::uwp::ReactImage::SetBackground$_ResumeCoro$1() Line 200	C++
 	Microsoft.ReactNative.dll!react::uwp::ReactImage::SetBackground$_InitCoro$2() Line 198	C++
 	Microsoft.ReactNative.dll!react::uwp::ReactImage::SetBackground(bool fireLoadEndEvent) Line 385	C++
 	Microsoft.ReactNative.dll!react::uwp::ReactImage::ResizeMode(react::uwp::ResizeMode value) Line 69	C++
 	Microsoft.ReactNative.dll!Microsoft::ReactNative::ImageViewManager::UpdateProperty(Microsoft::ReactNative::ShadowNodeBase * nodeToUpdate, const std::string & propertyName, const winrt::Microsoft::ReactNative::JSValue & propertyValue) Line 133	C++
 	Microsoft.ReactNative.dll!Microsoft::ReactNative::ViewManagerBase::UpdateProperties(Microsoft::ReactNative::ShadowNodeBase * nodeToUpdate, winrt::Microsoft::ReactNative::JSValueObject & props) Line 245	C++
 	Microsoft.ReactNative.dll!Microsoft::ReactNative::ShadowNodeBase::updateProperties(winrt::Microsoft::ReactNative::JSValueObject & props) Line 32	C++
 	Microsoft.ReactNative.dll!Microsoft::ReactNative::UIManagerModule::createView(__int64 reactTag, std::string viewName, __int64 rootTag, winrt::Microsoft::ReactNative::JSValueObject && props) Line 141	C++
 	Microsoft.ReactNative.dll!Microsoft::ReactNative::UIManager::createView::__l2::<lambda>() Line 558	C++
 	Microsoft.ReactNative.dll!Mso::Details::FunctionObjectWrapper<void <lambda>(void),void>::Invoke() Line 165	C++
 	Microsoft.ReactNative.dll!Mso::Functor<void __cdecl(void)>::operator()() Line 412	C++
 	Microsoft.ReactNative.dll!std::invoke<Mso::Functor<void __cdecl(void)> &>(Mso::Functor<void __cdecl(void)> & _Obj) Line 1585	C++
 	Microsoft.ReactNative.dll!std::_Invoker_ret<void,1>::_Call<Mso::Functor<void __cdecl(void)> &>(Mso::Functor<void __cdecl(void)> & _Func) Line 745	C++
 	Microsoft.ReactNative.dll!std::_Func_impl_no_alloc<Mso::Functor<void __cdecl(void)>,void>::_Do_call() Line 948	C++
 	Microsoft.ReactNative.dll!std::_Func_class<void>::operator()() Line 996	C++
 	Microsoft.ReactNative.dll!react::uwp::BatchingQueueCallInvoker::PostBatch::__l5::<lambda>() Line 41	C++
 	Microsoft.ReactNative.dll!std::invoke<void <lambda>(void) &>(react::uwp::BatchingQueueCallInvoker::PostBatch::__l5::void <lambda>(void) & _Obj) Line 1585	C++
 	Microsoft.ReactNative.dll!std::_Invoker_ret<void,1>::_Call<void <lambda>(void) &>(react::uwp::BatchingQueueCallInvoker::PostBatch::__l5::void <lambda>(void) & _Func) Line 745	C++
 	Microsoft.ReactNative.dll!std::_Func_impl_no_alloc<void <lambda>(void),void>::_Do_call() Line 948	C++
 	Microsoft.ReactNative.dll!std::_Func_class<void>::operator()() Line 996	C++
 	Microsoft.ReactNative.dll!Mso::React::MessageDispatchQueue::tryFunc(const std::function<void __cdecl(void)> & func) Line 41	C++
 	Microsoft.ReactNative.dll!Mso::React::MessageDispatchQueue::runOnQueue::__l2::<lambda>() Line 36	C++
 	Microsoft.ReactNative.dll!Mso::Details::FunctionObjectWrapper<void <lambda>(void),void>::Invoke() Line 166	C++
 	Microsoft.ReactNative.dll!Mso::QueueService::InvokeTask(Mso::Functor<void __cdecl(void)> && task, std::optional<std::chrono::time_point<std::chrono::steady_clock,std::chrono::duration<__int64,std::ratio<1,1000000000>>>> endTime) Line 208	C++
 	Microsoft.ReactNative.dll!Mso::TaskDispatcherHandler::Invoke() Line 168	C++
 	CoreMessaging.dll!00007fffb2d57406()	Unknown
 	CoreMessaging.dll!00007fffb2d253db()	Unknown
 	CoreMessaging.dll!00007fffb2d19c34()	Unknown
 	CoreMessaging.dll!00007fffb2d194de()	Unknown
 	CoreMessaging.dll!00007fffb2d2996b()	Unknown
 	CoreMessaging.dll!00007fffb2d28e26()	Unknown
 	CoreMessaging.dll!00007fffb2d27061()	Unknown
 	CoreMessaging.dll!00007fffb2d26e83()	Unknown
 	user32.dll!00007fffb678e858()	Unknown
 	user32.dll!00007fffb678e299()	Unknown
 	Windows.UI.dll!00007fffa6eaa98b()	Unknown
 	Windows.UI.dll!00007fffa6eaa680()	Unknown
 	Windows.UI.dll!00007fffa6eaa50b()	Unknown
 	Windows.UI.Xaml.dll!00007fffa5e23e20()	Unknown
 	Windows.UI.Xaml.dll!00007fffa5e23dbf()	Unknown
 	twinapi.appcore.dll!00007fffae875eca()	Unknown
 	twinapi.appcore.dll!00007fffae82e65f()	Unknown
 	SHCore.dll!00007fffb646e449()	Unknown
 	kernel32.dll!00007fffb6c47034()	Unknown
 	ntdll.dll!00007fffb7fc2651()	Unknown

Upgrade to 0.63

Currently the app is built against RNW version 62. Upgrade to 63.

Known issues:
-Will need to remove the manual linking of @react-native-communit/checkbox and letting auto-linking do its thing

Update gallery to RNW 0.64 release

RNW is currently previewing the 0.64 release. As of right now the 5th preview us up:

• react-native-windows_v0.64.0-preview.5

It would be useful to validate the 0.64 previews with this gallery app (see issue #23). Let's get a build of gallery on 0.64 ready so we can start testing it.

What does the Close button at the end of the NavView do?

Seems unnecessary, can it be removed? Or moved to the "BottomMenuItems" with a [X] in it so it's clear that this isn't another page

Add More Badges to Gallery Pages

Currently Gallery had the Wrapped Windows Control badge on pages that wrap a native xaml control. Request to add additional pages for Community Module vs. Core Component identification, etc.

• Community Module Badge
• Core Component Badge

Create list of manual verification steps

Related issue: microsoft/react-native-windows#5326

We'd like to use this Gallery app as a tool for validating RNW releases. This can involve visiting a list of pages and doing certain operations on each page to ensure the UI is working as expected. This isn't a complete answer, and automated verification is definitely where we want to save more time on manual process, but having a manual list is a good start. That's the first step.

Some pages are missing callback examples

Skimmed over some pages and noticed that eg. Slider and Date/TimePicker are not hooked up to any state on the page - interacting with them doesn't result in any changes to the app page. I think this is how those controls get used primarily.

Suggestion: add some dynamic text that is altered by interactions with those components.

(+nit: the first Pressable example is missing an onPress callback)

Add a Settings page

We need a Settings page in the app to house things like theme switches, font size, copyrights or other things as needed when the app grows.

Try to target WinUI 2.6 prerelease

Let's not push this to main until 2.6 is mature. But we should see if there are any issues targeting WinUI 2.6 and start playing around with that build.

https://www.nuget.org/packages/Microsoft.UI.Xaml/2.6.0-prerelease.210217002

Add hyperlink to checkbox page

Each sample page that uses a community module should have a hyperlink in the example page.
Add a hyperlink to the Checkbox sample page.

Gesture Handler Page Blank in Release Mode

Gesture Handler page is blank in Release mode but renders correctly in Debug mode.

Resolve App Publish Warnings

Current copy of React Native Gallery in the Store has produced two warnings: (1) that a privacy statement is needed, (2) that the submission inaccurately claims Mixed Reality support. These issues must be fixed by 5/3.

CI is failing due to running out of disk space

As the title says, the CI is currently failing on two open PRs due to running out of disk space:

#27
#46

The error: You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 0 MB

Github Actions runners only guarantee 14GB of disk space: https://docs.github.com/en/actions/reference/specifications-for-github-hosted-runners#supported-runners-and-hardware-resources

A potential solution is probably so setup a Gallery-specific Actions runner (on Azure for instance).

Add a screenshot of the app to the README.md

It'd be a nicer landing page for the repo if it had a screenshot or two.
Compare with the readme for the XAML Controls Gallery or the Avalonia Controls Gallery

WebView page hangs for about 10-20s

Seems worse on first navigation (the NavView exit animation gets stuck for a while). Seems like something is spinning the UI thread.

Text page has underlined space

The last example has an underlined space between "blue" and "and underlined text.", consider moving the   to the non-underlined text fragment.

Show React Native version in Settings->About page

In the Settings->About part of the gallery it shows the app version (e.g. 1.0.0.0 is what I see currently).
It'd be useful to see the RN version there.

Add page for Button component

https://reactnative.dev/docs/button

This component doesn't map to a native control. Also Pressable exists. However we will get questions about conformity of the Button control design and showing it in the gallery would be helpful.

Links don't have the correct mouse cursor behavior

The screenshot didn't capture it, but when I mouseover the links at the bottom of a page, such as "Source code" or "Send feedback about this page" I would expect the mouse cursor to be the "hand" and visually indicate this is clickable

Add RN Gallery to manual checklist for cutting RNW releases

We can use the gallery app to validate the quality of RNW major releases.
Nick Gerleman is driving overall release quality/schedule, need to coordinate with him.

Rough outline of steps:

1. Update RN Gallery to target latest RNW
   1a) May require updating community modules
2. Run through the pages and validate they still work

Performance Issue: Visual Tree Fails to Remove Pages

Environment

Run the following in your terminal and copy the results here.

1. npx react-native --version: 5.0.1-alpha.2
2. npx react-native info:

System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
Memory: 48.81 GB / 63.84 GB
Binaries:
Node: 14.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.3
System Images: android-29 | Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions: 10.0.18362.0, 10.0.19041.0
IDEs:
Android Studio: Version 4.1.0.0 AI-201.8743.12.41.7199119
Visual Studio: 16.9.31205.134 (Visual Studio Enterprise 2019)
Languages:
Java: 1.8.0_282
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: ^0.64.0-rc.1 => 0.64.0
react-native-windows: ^0.64.0 => 0.64.2
npmGlobalPackages:
react-native: Not Found

• Target Platform Version(s): 10.0.18362.0, 10.0.19041.0

• Target Device(s): Desktop

• Visual Studio Version: 2019

• Build Configuration: Debug and Release

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

1. Start up React Native Gallery with npx react-native run-windows.
2. Open up 10+ component pages in the app. Observe that the time it takes to load each page slowly increases. Creates a lot of lag in the app and poor user experience.
3. Inspecting the Visual Tree shows that the app creates a new page in the Visual Tree each time a page is navigated to and it doesn't destroy pages that have been navigated away from.

Expected Results

Each page should quickly render when selected from the menu. Load time should be consistent from the first page you load to the Xth.

Snack, code example, screenshot, or link to a repository:

React Native Gallery repo

Gallery uses NavigationContainer from the community module '@react-navigation/native' for its navigation menu. This code could contain the bug, or it could be in gallery's use of NavigationContainer, or a bug in RNW.

Print PDF button doesn't do anything

"Print" page, Print PDF button doesn't do anything (exceptions are seen in the debugger)

fix auto-linking of checkbox

When we upgraded to 0.63, we were unable to get auto-linking working for the @react-native-community/checkbox module.

To remove the manual linking I did this:

remove:
PackageProviders().Append(winrt::CheckboxWindows::ReactPackageProvider());
from App.cpp

This generated a redbox error. Probably need help from @jonthysell to figure this one out.

SketchCanvas Renders Gallery Blank in Release Mode

SketchCanvas leaves Gallery blank in Release mode following #127. @jaimecbernardo could you look into this?

Remove NavigationView from Gallery

From here Gallery freezes when react-native-xaml page is loaded. Suspect that the NavigationView component is what's causing the freeze. Temporarily remove this example until issue can be looked into more.

Add page for Expander component

Add a new page for the Expander component recently added to FURN. Here is the README for the Expander.

Note: The app will also need to be updated to WinUI 2.6

[xaml] Link to gallery has trailing .com

in the react-native-xaml page, there is a hyperlink button that points to "https://github.com/microsoft/react-native-gallery.com" instead of "https://github.com/microsoft/react-native-gallery"

[Feature] Add info to "send feedback" link that's on every page

This could pre-populate the issue text with version/screenshot/page we were on

Upgrade to react-native-windows 0.64.4

Hi,

react-native-windows 0.64.4 contains fixes that would allow an updated version of react-native-sketch-canvas to work.
After react-native-gallery is upgraded to 0.64.4, I'd open a PR to update and enable react-native-sketch-canvas.

Thank you.

Master Task: Build out of pages for V1 release

The goal of this task is to define the set of pages needed to release v1 of the RN Gallery, announce to the public, and evangelize.

The list only contains the most fundamental controls, to help reduce the time to official V1 announcement.

Core Components (has UI)

• View
• Image
• Pressable
• ScrollView
• Switch
• Text
• TextInput
• FlatList

Community Components (has UI)

• Checkbox
• Slider
• Picker
• DateTimePicker
• WebView

Windows-only Components (has UI)

• Popup
• Flyout

Move gallery app to use RNW NuGet package

This should speed up builds
Ideally all of the modules it uses can be updated to consume RNW from NuGet too

Make this available on Microsoft Store?

Like XAML Controls Gallery, people who don't plan to install Visual Studio or any development tools should have a chance to check out the current React Native for Windows 😉

Clicking on SensitiveInfo buttons doesn't do anything

Not sure what is supposed to happen but clicking the buttons doesn't seem to do anything

Enabled a Scaled Back Permissions Page

Currently the permissions page seeks to request almost every permission possible. This causes the app’s appxmanifest to have a ton of capabilities, more than seem necessary. Look into reducing the scope of the permissions that the permissions page is trying to seek. Look into temporarily remove the permissions page entirely.

Accessing the Permissions page crashes the app

As in the title. Looking at the callstack, I'm hitting an unhandled exception at RNPermissions.cpp@64
Could be the gallery app is missing some app manifest attributes, compared to the example one in the RNPermissions repo.

Add indication on pages of whether a control is native or JavaScript

Some React Native controls are implemented directly with their native stack, while some are implemented from primitives in JavaScript and don't heavily lean on larger native controls. It would be helpful to indicate this information somewhere, and the gallery could be a good fit.

There's nothing wrong with being a JavaScript control. So any indicator shouldn't cast that as being a bad thing. It's just additional information for apps that might need to know.

Reasons for wanting to know:

• visual alignment with native controls versus consistency across platforms
• knowledge of behavioral differences that result from the native controls

Ideas for how to indicate status:

• a link to the native docs for the corresponding native control (when there is a clear link)
• some kind of badge

Can't see the menu/drawer after running the app

Can't navigate through examples since menu is not visible

Add page for react-native-xaml

It would be good to add a page showcasing how you can use XAML directly from JSX :)
https://github.com/asklar/react-native-xaml

dummy issue

Just filing this issue to get an image URI up on the repo:

Add App Launch to CI Loop

Add app launch of RN Gallery to CI Loop in ADO.

Permissions page doesn't show anything for several seconds

Publish app to App Store

The app is currently not being published to the App Store. This task is tracking publishing it.

Add Touchable Component Pages

Touchable components are used frequently for press interactions. These are non-native components that are a part of core.

Add CI Loop to repo

We need to add a CI Loop to verify:

• Typescript compiles, lint rules pass
• Native app builds without errors

Add support for theme switching

Within the settings page, we should have the ability for the user to change their theme default from dark to light.

This may also mean saving that settings locally somehow so the user doesn't have to do this every time. Perhaps through AsyncStorage?

Error: Unable to resolve module ./index

the build doesn't fail on react-native run-windows, but it gives the mentioned error below in Metro and doesn't show the app.

Error: Unable to resolve module ./index from C:\Users\thedf\Downloads\react-native-gallery-main/.: ./index could not be found within the project or in these directories:
  node_modules

If you are sure the module exists, try these steps:
 1. Clear watchman watches: watchman watch-del-all
 2. Delete node_modules and run yarn install
 3. Reset Metro's cache: yarn start --reset-cache
 4. Remove the cache: rm -rf /tmp/metro-*
    at ModuleResolver.resolveDependency (C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:234:15)
    at DependencyGraph.resolveDependency (C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\node-haste\DependencyGraph.js:414:43)
    at C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\lib\transformHelpers.js:318:42
    at C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\Server.js:1471:14
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\Server.js:146:24)
    at _next (C:\Users\thedf\Downloads\react-native-gallery-main\node_modules\metro\src\Server.js:168:9)

Environment

Run the following in your terminal and copy the results here.

1. npx react-native --version:
   5.0.1-alpha.2
2. npx react-native info:
   System:
   OS: Windows 10 10.0.19042
   CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
   Memory: 19.72 GB / 31.90 GB
   Binaries:
   Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
   Yarn: 1.22.10 - C:\node-v12.18.3-win-x64\yarn.CMD
   npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
   Watchman: Not Found
   SDKs:
   Android SDK: Not Found
   Windows SDK:
   AllowDevelopmentWithoutDevLicense: Enabled
   AllowAllTrustedApps: Enabled
   Versions: 10.0.14393.0, 10.0.18362.0, 10.0.19041.0
   IDEs:
   Android Studio: Not Found
   Visual Studio: 16.9.31129.286 (Visual Studio Professional 2019)
   Languages:
   Java: 1.8.0_232 - C:/Program Files/AdoptOpenJDK/jdk-8.0.232.09-openj9/bin/javac.exe
   npmPackages:
   @react-native-community/cli: Not Found
   react: 16.13.1 => 16.13.1
   react-native: ^0.64.0-rc.1 => 0.64.0
   react-native-windows: ^0.64.0 => 0.64.2
   npmGlobalPackages:
   react-native: Not Found
3. npx react-native run-windows --info :

System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Memory: 19.84 GB / 31.90 GB
Binaries:
Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - C:\node-v12.18.3-win-x64\yarn.CMD
npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
npmPackages:
react: 16.13.1 => 16.13.1
react-native: ^0.64.0-rc.1 => 0.64.0
react-native-windows: ^0.64.0 => 0.64.2
Installed UWP SDKs:
10.0.14393.0
10.0.18362.0
10.0.19041.0

• Target Platform Version(s):
  Windows Desktop
• Target Device(s):
  Visual Studio 2019
• Visual Studio Version:
  Which build configuration are you running? Debug

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

1.Clone the repository.
2.In the root directory of the repository on your device, run yarn.
3.In the same directory run npx react-native run-windows.

Expected Results

Exprected to get the app running

Update app to 0.65

RNW 0.65 has released!

Per the RNW 0.65 Release Status we need to update the gallery app to that version.