* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Moving all test assets to the same folder in /Common/
* Revert "Moving all test assets to the same folder in /Common/"
This reverts commit cb3ab14325.
* Adding initial ios testing
* Merging to upstream main
* Reverting back to upstream/main
* ios working
* Removed MacOS BasePage because we can use the same selector as Win32. No need for it anymore. All macOS tests running correctly
* Removing platform-specific NavigateAppPage. Now that the selectors are the same, we don't need separate ones
* Trimming down all component's PageObject to just ONE file. No need for platform-specific page objects anymore, since they all pull from the same selectors
* iOS and macOS both fully working
* Adding iOS to CI Pipeline
* Change files
* Reverting previous mistakes
* Reverting unwanted change
* Removing unwanted change
* Reverting podfile.lock
* Reverting podfile changes
* Adding additional comments
* Fix prettier
* Increasing iOS retry timeout. App takes longer to load because of emulator
* Increasing app connection timeout across the board
* Change files
* Improve display name's in .ado pipeline
* Improving ADO E2E logic to remove duplicate steps
* Fixing parameter in .ado
Co-authored-by: dev <dev@oe-mac-C07-C60ES-JYVY-checkout.selfhost.corp.microsoft.com>
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Moving all test assets to the same folder in /Common/
* Revert "Moving all test assets to the same folder in /Common/"
This reverts commit cb3ab14325.
* Win32 Tests Working
* Disabling macos and windows tests temporarily
* Change files
* Fix prettier
* Increase Jasmine default timeout
* Re-enabling macOS and Windows E2E tests in the CI
* Add more logging for E2E Tests
* Changing degree of logging for testing purposes in macos testing
* Reverting WDIO config files and improving code structure
* Re-adding mascos basepage
* Re-adding macOS Tests
* Reverting mistake change in Button/Checkbox
* Transforming WDIO hooks to async
* Reverting previous WDIO config file changes that were for testing
* Re-adding menu tests
* Adding back NativeTester tests
* make sure iOS folder path is Debug-iphoneos and then also add wildcard for folder path to find the .a libraries to strip
* i forgot that for furn we only ship "release" flavor in nuget. so we should review debug if cehck
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Moving all test assets to the same folder in /Common/
* Revert "Moving all test assets to the same folder in /Common/"
This reverts commit cb3ab14325.
* Testing
* Updating yarn.lock
* Moving app maximize
* Testing
* Taking screenshots of every test
* Maximize app in spec instead of wdio
* The name of the FluentTester window changed with a new PR, so I'm updating the selector (this was causing an error)
* Adding back all the specs for testing
* Testing maximize app in the beforeSuite() hook so it gets called before every spec file
* Adding all macos specs to test
* Adding to readme about how to run MacOS e2e tests
* Revert previous .ado changes. Also improve publish artifacts logic because now Win32 reports/screenshots are in a different place than other platforms
* Fixing commenting error in .ado
* Fixing quotation error in .ado
* Adding '' to .ado file
* Change files
* Changing name of macOS job
* Trying to fix ado pipeline
* yarn prettier-fix
* PR Changes
* Nit: Spacing
* Nit: Grammer
* Nit: Comments
* Reverting previous testing change
* Reverting podfile.lock
* Improving comments and attempting to make a change to the CI: Start the RN Server in background bash
* Reverting ADO change that didn't work
* Reverting unwanted change
* Removing `yarn macos`
Want to see if the e2e tests can run without the server
* update fluent-tester
* delete others
* move FluentTester src
* yarn build works
* rnx-bundle works
* autolinking bug workaround + android
* windows works
* Update Apple CI
* More CI updates
* Update more CI
* update
* more updates
* More updates
* Change files
* maybe fix android
* fix ci?
* fix ci?
* ci
* setup emulator
* Remove expander
* More fixes
* The final countdown
* more fixes
* fix more links
* derp
* Change files
* Rearrange jobs and more fixes
* JS PR back to top
* remove flag that doesn't work
* Update android bundle name, enable single app mode
* forgot some
* Remove extra space
* update lock
* Update CI
* Remove Drawer from Fluent tester for now
* remove drawer again
* Change files
* Fix metro configs
* rerun `yarn configure-test-app` and add back some more metro config changes
* no expander
* update react dep + fix pipeline maybe
* delete duplicate job
* update yarn lock
* add back rnta
* Change files
* Move new tests
* Fix bundle
* update links + Podfile + delete podfile locks temporarily
* remove drawer again, add back locks
* Update apps/fluent-tester/package.json
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Update apps/win32/package.json
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Update apps/fluent-tester/metro.config.js
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* updates
* back to windows-2019
* merge
* remove --use-nuget
* Update .ado/azure-pipelines.yml
* Add back auto-lauch packager to ios/macos
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* check to see if we explicitly set our architecture nuget will publish both x86_64 and arm64 arch binaries and make sure RNCore ruby file isn't excluding any archs.
* while i am here, update xcode to 13.4
* ios simulator boot may fail when xcode is 13.4. try using 15.5 iOS version.
### Platforms Impacted
- [x] iOS
- [x] macOS
- [ ] win32 (Office)
- [x] windows
- [x] android
### Description of changes
(Apple only) RNTA version 1.1.4 updates it's xcconfigs so that the Address Sanitizer (ASAN) and Udefined Behavior Sanitizer (UBSAN) are OFF for release builds. We need this for downstream consumption. By updating our dependency, we can also remove one of our xcconfig flags where we hardcoded ASAN as off for release.
### Verification
CI
### Pull request checklist
This PR has considered (when applicable):
- [ ] Automated Tests
- [ ] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Added win32 nuget file - copied from macos, not working
* Attempting to publish Win32 FluentTester bundle to the react-native office feed for internal use so I can then pull the bundle into Devmain
* Change files
* Change name of Win32 Nuget Publish
* Adding publish to PR to test it
* Building repo
* Trying different NuGet command
* Only testing my NuGet push
* Assing assets to NuGet package
* Doing a full build in the CI
* Changing version number to build number
* Attempting to change the Version number to a cleaner number
* Changing publish path
* Trying new version number
* Fixing incorrect path for NuGet push
* Trying new approach
* Testing pipeline with directory
* Changing packagesToPublish path
* Push
* Revert
* Removing previous testing-only code
* Remove extra whitespace
* Adding <repository metadata to the .nuspec and ommitId property to the command-line to pack the NuGet
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Tests are running and succeeding, but the import still isn't working. I need to figure out how to import Platform from RN to choose the selector in BasePage
* Can't get WDIO to compile TS
* Updating WDIO to 6.5.0
* Updating Babel to 6.5.0 and integrating babel config. This should work, but it doesn't
* Making mac specific files
* Adding macos specific testing specs+page objects
* Fixing FocusZone spec for MacOS
* Reverting babel files back to original. The change did not work as I expected.
* Removing babel dependencies, not needed anymore
* Updating babel
* Nit changes
* Nit comments and removing unnecessary properties
* Nit comment
* Updating file name+import
* Nit changes to WebDriver macos config
* Adding MacOS E2E testing to CI pipeline
* Change files
* Updating file extensions of Windows specific files
* Removing Mac2 driver dependency from Win32/Windows package
* Removing unneeded package-locl files
* Fixing Appium logs
* Removing unnecessary dep from webdriver config
* Removing dep
* Removing dep
* Publishing MacOS build artifacts for CI
* testing ci
* Removing unnecessary step in CI Pipeline
* Updating Mac webdriver config file to take screenshots when test fails
* Testing CI
* Nit fix
* Reverting previous change
* Macos doesn't have browser.maximize funtionality
* Adding create a file functionality for reports
* Testing CI Pipeline - Seeing what directories are in /macos/ after E2E Test runs
* List contents of errorShots
* Reading contents of CI
* Testing CI
* Testing CI
* Finding applications folder
* Tesing CI for correct path
* Testing
* Test
* Testing CI
* Download tccutil command line tool
* Adding xcode to accessibility app permissions
* Updating download
* Attempting to disable SIP
* Removing unnecessary commands from CI
* Removing CI changes
* Nit styling
* Updating MacOS E2E Testubg documentation - How to run the tests locally
* Updating yarn.lock
* Nit: Spelling
* Update Podfile.lock
* Make publish overrides debug-compatible
If we want to use the nuget pack script to build debug configuration for sideloading, then we want optimization off and want more debug info.
* Initial nuget_pack.sh
First working version, based on refactored FUA script. -p option is currently a no-op, but -d option builds Debug as advertised.
* Use absolute paths for xcode_select_current_version.sh
Script behavior should not depend on $PATH.
* Update Podfile.lock
* Add prerequisite tasks
- Add do_prerequisites function that does yarn/gem/pod steps to bootstrap environment enough to build the native libraries
- Add git_clean function and a third -c level since this is a pretty common troubleshooting step
- Add special handling of the (now common) pushd/popd shell builtins, to suppress their normal output while not suppressing the logging of the command itself
- Rename print_error to log_error for consistency with log_action
- Use empty/nonempty as the boolean states for bash vars 'prerequisites' and 'debug'
* Rename script to nuget_pack_apple.sh
nuget_pack.sh works for FUA, but FURN includes platforms beyond Apple, so we should be more specific.
* Escape backticks
We don't actually want to run `pod install` when printing this message.
* podfile locks
Co-authored-by: Saad Najmi <sanajmi@microsoft.com>
* Update to react-native 0.64
* Cleanup after merge
* cleanup unused dependency
* fix dependencies, undo whitespace-only change
* fix dependencies. remove unneeded tslint/eslint suppression.
* revert unneeded change
* Update test snapshots
* Update callout test: border width picker must use values that can be converted between string and number. Picker requires strings, but the target borderWidth value is a number.
* SyntheticEvent: dispatchConfig prop is not present in react-native NativeSyntheticEvent. To compensate for its absence, make SyntheticEvent.dispatchConfig optional.
* Change files
* Remove forced resolution of react-native and react packages.
* Update react-native-test-app and ios pod versions
* Update CLI to 5.0.1 and use cli-platform-ios 5.0.2 since it has a critical fix for RNTA.
* Apply RNTA's published workaround for ios/android issues.
* take 2
* Update @react-native-community/slider, and removing pods which are autolinked.
* explicitly set jdk
* undo java version and remove ndk install
* Update RNTA
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Adding Button accessibility testing
* Adding accessibilityTesting for RadioGroup, Tabs, ExperimentalTabs, Link, Text
* Adding extra documention on page objects
* Uncomment all tests in bootpage
* Fixing faulty link
* Change files
* Nit comment fix
* Increasing depth of scroll
* Specify test descriptions for each component. It needs to be specific to each control so if there's an error, the screenshot fileName will be correct (it uses the test description)
* Changing where we scroll to find components. Before, we were scrolling at the title of the Test page. However, if our E2E component is far enough down, the title of the test page will be off-screen, thus causing an error
* Nit: Fixing params in WDIO hook
* Taking a screenshot on app boot
* Updating artifact location
* Reverting unwanting upgrade of WDIO
* Update yarn.lock
* Taking screenshot on app boot
* Making CI create the errorShots directory
* Changes to CI
* Testing CI - Win32 not creating Screenshots of E2E Testing. Testing dir in each directory
* Removing CI commands to check directory (this was for testing purposes only)
* Removing unneeded screenshots
* Updating Accessibility Role Control Types link
* Removing commented out code
* Updating a comment
* New pipeline to test if links on the repo are working
* Adding command
* Testing different path
* Parameter to fail test
* Reverting change
* Testing another fail condition
* Missing fail error
* Testing different test failure
* testing out xargs
* Fixing broken links to pass test
* Fix broken link
* Change name of config file
Co-authored-by: Krystal Kramer <krsiler@microsoft.com>
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Removing change file
* Testing CI pipeline to continueOnError
* Adding Windows
* Change files
* Reverting Callout TestPage changes and increasing E2E page timeout to 6 seconds from 3 seconds - hopefully will decrease likelihood of false-negative due to long wait between pages
* Moving continueOnError to be specific to the E2E testing task
* Testing a CI failure - will revert
* testing ci
* Reverting Callout Test page
* Removing unnecessary change file
* Change files
* Revert "Update our pipeline to use macOS 11 and Xcode 12.5 (#966)"
This reverts commit f049c29171.
* Keep Xcode 12.5
* revert to xcode 12.4, use macOS 11
* Only build and pack ship libraries
* test pipeline
* Remove yarn bundle from NuGet Publish as well
* Simplify pipelines a bit
* fix yml
* Comment out NuGet Publish from PR again
* Remove comment now that NuGet Publish is shorter
### Platforms Impacted
- [x] iOS
- [x] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
### Description of changes
This change refactors some of our native iOS and macOS code for better downstream integration into the office codebase.
Namely:
- Every native module's `<Component>-Bridging-Header.h` has been renamed to `<Component>ViewManager.h`.
- These files were never bridging headers, and cocoa pods / swift never interpreted them as such. There is potential to improve the RN docs on how to write a native swift module here as well.
- Adds the `BUILD_LIBRARY_FOR_DISTRIBUTION` flag to each native module's pod spec
- This flag allows for ABI stability in our swift static libraries. Note that the main side effect of this flag is it produces a `.swiftinterface` file in the static libraries' swift module. I do not include the swift module in the NuGet to be included downstream in office. In my testing I found it was not needed to get iOS NativeButton to link, so I opted not to include the swif module. This may change in the future as I try to figure out why the macOS NativeButton static library won't link.
- Adds the `OTHER_SWIFT_FLAGS=-gline-tables-only` flag to each native module's pod spec
- This is a potential security risk that is fixed, as per the comment here https://github.com/microsoft/fluentui-react-native/pull/710#discussion_r688016727 .
- removes the `CLANG_DEBUG_INFORMATION_LEVEL=line-tables-only` build flag
- This caused issues with the previous `BUILD_LIBRARY_FOR_DISTRIBUTION` flag and build failures. I'm not sure why.
- Sets the Swift version to 5.0
- I added this because I noticed that Azure pipelines would actually use the Swift 5.3.2 compiler, so I wanted to be explicit which version of swift we are compiling for.
Prior to this change, we could not link the NativeButton component downstream into office due to some linker issues. This change updates a few parts of our native iOS and macOS code such that we can now link the iOS NativeButton. The macOS NativeButton static library still does not properly link, I'll leave that as a followup.
### Verification
I had a local change downstream in office to consume an intermediate NuGet produced by this PR and test that linking worked. That's where I saw that iOS and not macOS works. Link for those who can see it: https://office.visualstudio.com/OE/_build/results?buildId=9621115&view=logs&j=4257c0a7-7659-5375-d6e0-cde9f28a3d36
### Pull request checklist
This PR has considered (when applicable):
- [x] Automated Tests
- [x] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
### Platforms Impacted
- [x] iOS
- [ ] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
WIP to test pipeline / NuGet consumption.
### Description of changes
This change updates our Avatar component (which was a native module wrapping the FluentUI Apple Avatar) to use the new FluentUI Apple Vnext SwiftUI implementation of Avatar. I also cleaned up the test page for Avatar and made it look a lot nicer.
The change is non-trivial: It required me to define a new obbj-c class and macros to pass properties from Javascript to the SwiftUI View. The class will need to be implemented one per every new component. The macros can be reused by future SwiftUI components. The macros and implementation were inspired by https://betterprogramming.pub/react-native-meets-swiftui-d1606a8e1681
Explanation:
SwiftUI talks to normal Swift / obj-c through a proxy / viewWrapper class. The proxy class gives you access to a state object, and a UIView that contains the SwiftUI view. The important bit: You can access the view from the proxy class, but you cannot access the proxy class from the view.
```
Proxy Class (MSFAvatar)
|-> View (UIView wrapper around SwiftUI View)
|-> State (Used to set properties on the SwiftUI View)
```
This does not work well with React Native. React Native View Managers expect to be able to set properties directly on the view via the view class, and know not about this indirection through the proxy object. To solve this, I created an extension on the proxy class that I named `MSFAvatarStorage` that allows me to store a key value pair of view->proxy classes. This means that given a view, I can now look up it's proxy object, then access it's state object to set properties.
```
Proxy Class (MSFAvatar)
|-> View (UIView wrapper around the SwiftUI view)
|-> State (used to set properties on the SwiftUI view)
|-> Storage (view->proxy object mappings)
```
The last bit I needed was extra macros to actually do this indirection:
```
#define RCT_EXPORT_SWIFTUI_PROPERTY(name, type, proxyClass) \
RCT_REMAP_VIEW_PROPERTY(name, __custom__, type) \
- (void)set_##name:(id)json forView:(UIView *)view withDefaultView:(UIView *)defaultView RCT_DYNAMIC { \
NSMutableDictionary *storage = [proxyClass storage]; \
proxyClass *proxy = storage[[NSValue valueWithNonretainedObject:view]]; \
proxy.state.name = [RCTConvert type:json]; \
}
...
// In MSFAvatarViewManager
RCT_EXPORT_SWIFTUI_PROPERTY(primaryText, NSString, MSFAvatar)
```
And now we have a working SwiftUI based native component in React Native!
### Verification
Rewrote the test app to test the SwiftUI based props. They work!
https://user-images.githubusercontent.com/6722175/120049216-e7f26700-bfde-11eb-855f-c0d9f5ab4166.mov
### Pull request checklist
This PR has considered (when applicable):
- [ ] Automated Tests
- [x] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Initial commit
* Add Nuget Pack Job to PR Pipeline
* Fix NuSpec
* Change files
* Clean up to make PR worthy
* fix ios bug, add xcconfig manually
* Add comment and issue to macOS avatar implementation
* initial commit
* Force build static libs in publish to make sure parsing is correct
* Revert change to test building static libs
* Move xcconfig to own file, retest in PR pipeline
* Copy template from fluentui-apple as they mismatch
* move macOS steps sooner
* Simplify xcodebuild template
* remove manual testing from PR pipeline
* ios and macos work, not android
* Move android test app to pproper structure
* some extra files
* turns out we need this
* Add Android CI build step
* Revert 0.63 change to ios and android
* Undo changes to windows test app
* Update documentation and ADO
* Fix yml
* fix react dependency
* Forgot quote mark
* try the macos image for Android PR
* Remove Android CI PR pipeline
* remove carets, fix run-ios args
* Update yarn lock
* Remove caret from Android
* Update apps/macos/package.json
* Yarn
* Merge
* Fixing repo
* Update package
* Merge
* Fixing WinAppDriver version for CI Pipeline
* Fixing repo
* Moving WinAppDriver change to only Windows jobs
* Initial Commit
* Set up CI with Azure Pipelines
Comment out NPM package publish [skip ci]
* Update publish-nuget-job.yml
* Update publish-nuget-job.yml
* Try to use jobs
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Deleted broken templates
* Update azure-pipelines.publish.yml for Azure Pipelines
* No more matrixes
* Update azure-pipelines.publish.yml for Azure Pipelines
* more changes
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update paths
* More updates
* Update
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* revert using cocoapod task
* Forgot word
* Remove compiler optimizations
* simplify apple-xcode-build
* Use xcode 12
* typo
* Add bridging header to podspec
* nevermind
* Remove section from Podfile
* Try only one config
* Use xcodebuild instead of xcode task
* typo
* another typo
* remove extra args from xcconfig
* simulator passes, device doesnt. what about mac?
* Maybe 4 of 6 passing
* Try xcode task again
* typo
* Maybe all 6 with a signing id
* more explicit derived data path
* maybe no sign
* Clean up ordering / path
* Remove unnecessary stuff
* Dont use env variable in one template
* Switch to use the default version of xcode like we do in fluentui apple
* Bring over xcode select script
* Move pipeline specific scripts to .ado/scripts
* Update nuspec comments to specify bundles are release bundles
* Explicitly specificy files to include in nuspec
* Update azure-pipelines.publish.yml for Azure Pipelines
* renamed nuspec in yml
* Fix some edits in package.nuspec
* Update azure-pipelines.publish.yml
* Set up CI with Azure Pipelines
[skip ci]
* fix merge error
* forgot files
* Addded Nuspec
* Update azure-pipelines.publish.yml for Azure Pipelines
Comment out this
* Update azure-pipelines.publish.yml for Azure Pipelines
Comment out variable group
* Set up CI with Azure Pipelines
[skip ci]
* Added just the package.json to the nuspec
* remove external, comment out yarn install and test
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Revert changes to publish yml, get ready for PR
* clean up yml
* Update azure-pipelines.publish.yml for Azure Pipelines
* Update azure-pipelines.publish.yml for Azure Pipelines
* Remove files from nuspec
* Back to the original .publish file with the extra template
* Update FluentUI.nuspec
* Update FluentUI.nuspec
* Update azure-pipelines.publish.yml
* Update publish-nuget-job.yml
* Update azure-pipelines.publish.yml
* Copy Link into Shimmer
* try to add it to fluent tester
* Shimmer test (copy of Link Test) showing in iOS test app
* Minimum set of files for an empty native shimmer control, everything is commented out that isn't needed
* obj c version of wrapped shimmer view. needs a /MicrosoftFluentUI/Swift Compatibility Header in the HSP of the generated xcconfig to work
* updated gitignore
* Converted to swift
* Try adding a podspec and referencing it in our final app
* rename podspec
* Remove unnecessary files
* ShimmerView rendering in test app
* Wrapped Shimmer View instead of ShimmerLinesView
* Moved a file
* Trying to add a custom property, does not work
* Using compose framework once more
* shimmerAppearance also exposed
* Lets just use props and no tokens for now
* cleaner swift file
* minor changes
* More changes
* Update some dependencies from the upstream counterpart
* Added new test
* Change files
* Fixed two bugs where Shimmer.tsx threw a tyoe error, and where ShimmerContainverView did not set props correctly
* Some extra comments / documentation
* Setting a defualt token works, customization does not
* Token customization works
* use updated FUA version of shimmer
* Updated podspec
* Add back a minimum iOS deployment target, remove tokenProps
* Update Xcode Version to 11.4.1
* Remove tokenprops: true from Shimmer
* initial lage init
* hook up build and test scripts via lage
* add full build support
* update new packages to use the new task runner
* update README with instructions on using Lage
* update commands executed in CI
* switch to using Lage for build sequencing
* Change files
* enable tests for FocusTrapZone
* turn on Link tests
* enable Stack tests
* add verbose output to full build task in CI
* add the verbose flag to the actual command this time
* split up build and bundle to handle resource failures
* rename full-build to buildci to be consistent with fabric, up memory limit in CI
* update README for buildci command
* try limiting concurrent processes for CI
* remove lerna dependency, leaving config file
* break up publish tasks to avoid failures
* try again to fix the CI
* fix lerna reference in README
* fix bad capitalization and try with full buildci command
* fix missing dep in contextual menu
* Yarn
* Enhance E2E Reporting + CI Reliability
* Nit - Formatting
* Removing sleep call - originated from RNW. Will observe how this affects the pipeline
* bump rnw version to 0.62.1
* Change files
* add missing lock file
* turn on logging for CI
* move back to experimental nuget usage
* update to use the experimental nuget support, for real this time
* more patches to project files
* Connect to correct nuget feed, and use correct nuget version
* fix another version
* Use midgard-yarn
* Use release in uwp for now.
* use x64 for now
* work around for CLI bug
Co-authored-by: Andrew Coates (REDMOND) <acoates@microsoft.com>
* Yarn
* UWP Testing
* UWP testing working
* Increasing Timeouts for WebDriverIO and Jasmine to account for long bundle loads
* Change files
* CI Tests
* CI Loop UWP
* Fix
* small fix
* Small
* CI
* Added certificate for UWP test
* Small change
* Adding NuGet download in CI
* Adding Nuget Restore command
* Small fix
* Testing CI
* CI
* CI
* CI
* CI
* Changing powershell CI
* CI
* Nuget Restore
* CI
* CI
* Removing NuGet restore from CI
* Removing nuget install
* Copying RNW's Pipeline for UWP
* CI
* CI Test
* CI
* s
* Testing
* ci
* d
* s
* c
* ;
* f
* a
* Added Windows 10 SDK to CI
* SDK
* SDK
* SDK fix
* Adding Nuget Restore back
* Nuget
* Dir
* Dir
* d
* d
* Checking dir
* d
* Adding certifcate to store
* Certificate
* CI
* Testing
* Testing
* adding react-native-public feed
* Fix
* Removing nuget restore
* Install nuget
* Opening new CMD to run server
* Testing E2E
* Install Node
* Changing server start
* server
* ci
* Opening new CMD with Powershell to start server
* Testind
* no message
* Test
* Changing script path
* Changing powershell to inline
* Server
* Running app
* d
* Checking to see if cmd process' keeps running
* Checking still
* Fixing server
* Fix
* Seeing if app is running
* Kill FluentTester, leave server
* App stopped working
* Retry
* D
* Re-submitting
* Testing CI Failure
* CI Testing Succeeding
* Changing syntax to shortcuts
* Fixing syntax error
* Adding in Windows PR
* Format E2E UWP Testing
* Small
* Cleaned up code for PR
* Delete @fluentui-react-native-button-2020-05-21-15-50-20-sammy-UWP_E2E.json
* PR Fixes
* Comment fix
* Comment Fix
* PR Fixes
* Adding Node.JS and NuGet install to setup-repo template
* Updated comments
* Add more scripts to package.json, change name to FluentTester for parity with win32, update yml files
* Undo yarn lock changes
* Maybe I do need this change
* move projects up a dir and opt apple platforms into lerna/yarn
* Don't need to modify these anymore with our projects moved up a level
* try to fix some out of tree platform issues for apple
* Fix build error of wrong platform
* Add parity to win32/windows with our index.js and index.tsx mapping.
* split ios/macos, stand up ios tester
* Remove bundles
* Update CI with our new project locations
* More CI updates
* Pushing up changes the CI says it needs in yarn.lock
* delete unused app.js file
Co-authored-by: Jason Morse <jasonmo@microsoft.com>
* Add macOS/iOS RN deps, update CI
* Update CI steps to launch custom macos/ios packagers
* Update azure-pipelines.yml
* Update azure-pipelines.yml
* Syntax fixes to CI
* Rewrite the yml to fit ADO syntax. Split packagers into two shell scripts
Delete extraneous ios target
* Update apple-xcode-build.yml
* Remove extra vmimage reference
* Update yarn.lock
* Specify vmIage as macos within the job
* Fix path to podfiles
* Add more explicit description of pod install task
* bash var syntax
* Update apple-xcode-build.yml
* Update condition variable syntax
* update missed var name
* add yarn install to platform folders to install node_modules
* yarn install
* update path to build
* Build with rn commands instead of xcodebuild
* synax fix
* Update build settings and remove part of build infra to unblock
* Update mac test project
* Clean up view controller and app delegate code to load the bridge more succinctly
* Pull in the same version of rn for mac/ios
* Make the view controller our delegate
* Remove a pod we dont need until we're on 0.61
* Remove other pods that don't exist in 0.60
* Fix up more pod deps to match 0.60.0 instead of 0.62.0
* Remove flipper deps
Samuel Freiberg
lyzhan7
Harrie Shin
Saad Najmi
dependabot[bot]
Ruriko Araki
dannyvv
Chris Pearson
Adam Foxman
Saad Najmi
Tommy Nguyen
Andrew Coates
Keven Arroyo
Mayank Shukla
Jason Morse
tkamireh
HeyImChris
Chris Hogan