* Update to RN 0.73
* Change files
* RN 73 requires node 18
* Add 72 profile
* Update wdio/appium etc to get it running on node 18
* fix
* fix
* Update podfile locks
* fix
* fix
* fix
* see if building fixes resolution of focus-zone by e2e tests
* Try specifying reports dir with full path
* Try debug level reporting to identify error creating logs
* try enabling more logs
* alternate way to specify logfile.
* downgrade @wdio/appium-service to move before https://github.com/webdriverio/webdriverio/pull/12095
* Test no-packager
* yarn init-test-app (With cleanup)
* Try install Java18
* fix
* fix
* Android E2E fixes
* fix?
* fix
* fix
* Add more logging for E2E android test failure
* more logs
* more log
* Use actual scroll region, to avoid OS swipe gestures
* Increase android time out to navigate to page
* fix
* remove extra try/catch and logging
* Fix windows build
* test windows PR without node install
---------
Co-authored-by: Saad Najmi <sanajmi@microsoft.com>
* Update appium and node version (#2620)
* Update appium beta version to version that doesn't use jsdoc
* Update tester_deps yarn.lock
* Change files
* Update a bunch of things in an attempt to get things working again...
* Update node?
* diagnose what's up with CI
* Introduce .node-version file
* remove midgard-yarn
* Frozel lockfile
* undo yarn please change
* Appium driver install added back
* Appium driver install added back
* Appium driver install added back
* Remove flakiness
---------
Co-authored-by: Saad Najmi <saadnajmi2@gmail.com>
* Add test steps to JS PR
* fix dry-run script
* temporarily remove buildci step
* try node 14.x
* build button package first
* add build step back
* back to node 16
* change npm install version to 9.5.0
* just scope build to button
* Add empty .npmignore file
* remove extra npm install and dry-run steps
* revert azure-pipelines script changes
---------
Co-authored-by: Ruriko Araki <ruaraki@microsoft.com>
Co-authored-by: Saad Najmi <saadnajmi2@gmail.com>
* Update appium beta version to version that doesn't use jsdoc
* Update tester_deps yarn.lock
* Change files
* Update a bunch of things in an attempt to get things working again...
* Update node?
* diagnose what's up with CI
* Introduce .node-version file
* remove midgard-yarn
* Frozel lockfile
* undo yarn please change
* Appium driver install added back
* Appium driver install added back
* Appium driver install added back
* Remove flakiness
---------
Co-authored-by: Saad Najmi <saadnajmi2@gmail.com>
* Add import plugin (eslintrc.json, package.json, yarn.lock)
* Changes from running yarn lint --fix
* Change files
* Change import order config "warn" to "error"
* Run yarn lint --fix again + some manual fixes
* Change files
* Run prettier
* Re-order - move standard libraries (react/react native) to the top
* Run yarn lint --fix after previous change
* Change files
* Bad merge
* Bump react-native-svg: 12.3.0 -> 12.x
* Change files
* 12.x -> 12.4.4 in package.json
* Add Graphics.Win2D as a dependency
* Revert "Add Graphics.Win2D as a dependency"
This reverts commit 7f3899bd93458d90f1236cc0724b4955bf67d802.
* Win2D.UWP added as a dependency
* Update yarn.lock
* Bump experimental icon rnsvg
* Bumping rnsvg to 12.5
* Add script to add win2d as a ReactTestApp dependency
* Add win2d script to uwp ado pipeline
* Update script to add Win2D.uwp dependency
* Commit for pipeline testing
* Remove disk size checks, keep fetchDepth in ado
* Change files
* Run windows Pr validation step on larger VM
* Add + use patch-package for Win2D.uwp dependency
Patching react-native-test-app is now more stable than the previous
commit.
* Revert accidental change to a change file
Co-authored-by: Larry Win <winlarry@microsoft.com>
Co-authored-by: Danny van Velzen <dannyvv@microsoft.com>
### Platforms Impacted
- [x] iOS
- [x] macOS
- [x] win32 (Office)
- [x] windows
- [x] android
Waiting to merge until Office bumps to 0.68.
### Description of changes
- Bump react-native from 0.66 to 0.68
- Add rnx-kit config sections for all packages to help with dependency management (see https://microsoft.github.io/rnx-kit/docs/guides/dependency-management)
- For reference, almost all packages I added an rnx-config section to have this:
```
"rnx-kit": {
"reactNativeVersion": "^0.68",
"reactNativeDevVersion": "^0.68",
"kitType": "library",
"capabilities": [
"core",
"core-android",
"core-ios",
"react"
]
}
- Ran `yarn rnx-dep-check --write` at root to fix dependencies for RN 0.68
### Verification
- iOS: Not yet tested *
- macOS: Not yet tested *
- win32 (Office): Need to re-test for new changes
- windows: Need to re-test for new changes
- android: Not yet tested *
*hoping someone could help me out with testing these platforms
### Pull request checklist
This PR has considered (when applicable):
- [x] Automated Tests
- [ ] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Making it so the appium driver packages get installed in each folder rather than the root. Appium looks for these drivers in the folder it's in, not the root. This was causing issues when trying to run E2E tests locally.
* Change files
* Update rnx-kit configurations
* `yarn rnx-dep-check --write`
* Remove workspace resolutions
* Update React / React Native / React Native macOS/Windows/Win32 dependencies
* Fix yarn build fallout
* Fix test fallout
* Update podfile locks
* Remove unnecessary dependency
* Change files
* Remove alpha cli resolution
* rnx-dep-check --write
* update lock
* update rex
* update lock
* update ios podfile
* update macos podfile
* upgrade RN types to version 0.66
* updated some components to 0.66 and renamed TurboModuleRegistry in getThemingModule
* resolved type errors
* bumped react dom
* bumped rn svg
* updated rn svg to latest version
* updated win32 rn to 0.66 for checkbox and interactive hooks
* updated component rn versions
* updated some packages and apps to 0.66
* updated all package types except for themes
* updated scripts rn types to 0.66
* updated fluent tester to rn 0.66
* updated RN types to 0.66 for win32 app
* updated theming to rn types 0.66
* updated yarn
* updated all >=17.0.1 react versions to >=17.0.2
* resolved podfile conflict
* updated podfiles
* Change files
* moved testID in Header to the first text element in the fluent tester
* removed 0-0 in rn versions
* updated yarn.lock
* removed resolutions, was causing windows tester to not load
* updated @react-native-community/cli
* added onPressIn and onPressOut for win32/windows/android and removed getTheming comments
* added onPressIn/Out to base adapters
* added onPressIn/Out for macos adapters
* removed notification test, just so the rn 0.66 pr can go through, and updated react for notification
* removed comment in fluenttester
* added jpeg-js and moment back to package.json resolutions
* updated react test renderer
* reverted some accidental changes to react-native-test-app version and svg versions
* fixed error on package.json for macos
Co-authored-by: Saad Najmi <sanajmi@microsoft.com>
Co-authored-by: Saad Najmi <saadnajmi2@gmail.com>
### Platforms Impacted
- [ ] iOS
- [ ] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
### Description of changes
This change forces @appium/support to be a newer version, which allows us to update a dependency that has security vulnerability (moment). And also allows us to remove another resolution (plist). One of our dependencies pins appium/support to a particular version and this resolution overrides that.
Kinda annoyed that appium declares all of their dependencies without ranges, but 🤷🏻♀️
### Verification
CI will run E2E tests
### Pull request checklist
This PR has considered (when applicable):
- [ ] Automated Tests
- [ ] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Fix metro config
* Update to latest @rnx-kit package versions.
* Update rnx-kit packages. Turn typechecking and duplicate package detection failures off, as they reveal errors that already exist in the monorepo.
* Change files
* Fix change file
* 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
* 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>
Ruriko Araki
Saad Najmi
Andrew Coates
dependabot[bot]
Rohan Prasad
Krystal Kramer
Lawrence Win
Lynn Zhang
Tommy Nguyen
Ayush Singh
Samuel Freiberg
Nabil Khalil
Saad Najmi
Adam Foxman
Keven Arroyo