* 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 tokens-global.ios.ts
* Bump design tokens package to include colors
* Fix tester error (copied Android fix)
* Change files
* Update theme-tokens package.json
* Fixed Badge tint-severe colors
* Attempt to use win32 as platform
* Bump @rnx-kit/jest-preset package
* yarn test -u (snapshots update from windows to win32)
* Remove console.log statements
* Change files
* Split buttonTokens into platform specific files + fix bad merge
* Make badge tests run on win32 instead of ios
* Change files
* Revert "Change files"
This reverts commit 364d33f5ba.
* Revert "Make badge tests run on win32 instead of ios"
This reverts commit fe55c0120f.
* Update snapshots (changes are the differences between ios and windows tokens)
* Change files
Co-authored-by: Valentyna Kozlova <vkozlova@microsoft.com>
### Platforms Impacted
- [ ] iOS
- [ ] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
### Description of changes
I noticed that the component cache doesn't actually cache the result from the first time we hit the code, so it's not actually caching anything.
Fixing the cache to save the result of requiring the native component.
Added unit test
Also added new config to run jest debugger for the current folder's tests
### Verification
Test written to ensure that the cache is working and that the requireNativeComponent code isn't hit more than once per component
### Pull request checklist
This PR has considered (when applicable):
- [ ] Automated Tests
- [ ] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
### 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
* 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.
* 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
- [X] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
### Description of changes
Standing up a token pipeline for high contrast modes on macOS. Most token values are based off of iOS, some are guesstimates based on existing controls in Office.
### Verification
Ensured tokens can be consumed in the apple theme.
### 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 TypeScript 4.5.4.
* Change files
* Caught values are now treated as unknown instead of Error. Add appropriate type checking/casting to fix build errors.
* Update tslib
* Change files
* 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
Andrew Coates
Saad Najmi
Ruriko Araki
dependabot[bot]
Ayush Singh
Krystal Kramer
Tommy Nguyen
lyzhan7
Harrie Shin
Nabil Khalil
dannyvv
chiuam
Saad Najmi
Adam Foxman
Chris Pearson