@fluentui-react-native/tester 0.170.57 → 0.170.59

package/docs/android.md

@@ -1,84 +0,0 @@
-# Running the FluentUI Tester on Android
-
-`FluentUI Tester` is the test app that we use to test our FluentUI components during development. It uses the [react-native-test app](https://github.com/microsoft/react-native-test-app) under the covers, and loads the fluent-tester bundle.
-
-## Launch `FluentUI Tester` app on Android
-
-Prereqs:
-
-- FluentUI Tester is built uses react-native-test app, so install its [prereqs](https://github.com/microsoft/react-native-test-app#react-native-test-app) and follow instructions depending on whether you're developing on Windows or macOS.
-- Install [Android Studio](https://developer.android.com/studio)
-- Make sure you have setup an [Android Virtual Device](https://developer.android.com/studio/run/managing-avds)
-
-1. Make sure you have followed the [Getting Started](../../../README.md) instructions to install packages and build the entire FluentUI React Native repository. I.e. from the root of the repo:
-
-```sh
-yarn
-yarn build
-```
-
-2. Start the server by running:
-
-```sh
-cd apps/fluent-tester
-yarn start
-```
-
-3. To boot the app, open a new command prompt and run:
-
-```sh
-cd apps/fluent-tester
-yarn android
-```
-
-## Dependencies
-
-Dependencies are managed by
-[`@rnx-kit/align-deps`](https://github.com/microsoft/rnx-kit/tree/main/packages/align-deps).
-If you're looking to upgrade `react-native`, use the interactive upgrade command:
-
-```sh
-yarn rnx-align-deps --set-version
-```
-
-This command will ensure that all relevant packages are bumped correctly.
-
-You can read more about this tool here:
-[`@rnx-kit/align-deps` design document](https://github.com/microsoft/rnx-kit/blob/main/docsite/docs/architecture/dependency-management.md)
-
-## Debugging
-
-You can debug native code in Android Studio. To debug javascript code, you can either use standard web debugging, or you can use [React Native Tools](https://marketplace.visualstudio.com/items?itemName=msjsdiag.vscode-react-native) to debug directly in VS Code. The steps are as follows:
-
-1. Launch your test app + packager as you normally would
-2. Go the debug menu in VS Code and run the "Attach to Packager (Android)" configuration
-3. Open the developer menu in your test app, and click debug
-4. You now should be able to set breakpoints and step through your code directly in VS Code.
-
-## Troubleshooting
-
-- The first time you run your project, you may get errors about missing SDKs. Android Studio usually provides quick options to resolve these issues, but you can also go to Tools->SDK Manager to manually install or update SDK platforms or tools for your project.
-
-- If you get the error "command not found: adb", add the following to .bash_profile or .zprofile
-
-```sh
-export PATH=~/Library/Android/sdk/platform-tools:$PATH
-```
-
-- If you would like to debug in Android Studio, you can do the following to open the project there:
-
-```sh
-# macOS
-open -a "Android Studio" .
-
-# Windows
-# Easiest to open from within Android Studio - see picture below
-```
-
-![On Windows, it is easiest to open from within Android Studio, and the folder will show an Android Studio icon.](./../../../assets/fluent_tester_android_windows_open.png)
-
-Note: if Android Studio does not provide you with an "app" to run after you first open the project from the android folder, you may have to restart Android Studio.
-
-Once Android Studio finishes preparing your app folder, you will be able to build and run your app by clicking on the "app" dropdown in the menu bar. If you have not yet setup an AVD, please see [this page](https://developer.android.com/studio/run/managing-avds) on how to set one up.
-
-![Run your app from Android Studio with the "app" button in the menu bar.](./../../../assets/fluent_tester_android_app_built.png)

package/docs/ios.md

@@ -1,69 +0,0 @@
-# Running the FluentUI Tester on iOS
-
-`FluentUI Tester` is the test app that we use to test our FluentUI components during development. It uses the [react-native-test app](https://github.com/microsoft/react-native-test-app) under the covers, and loads the fluent-tester bundle.
-
-## Launch `FluentUI Tester` app on iOS
-
-Prereq: FluentUI Tester on iOS can only run on a Mac.
-
-1. Make sure you have followed the [Getting Started](../../../README.md) instructions to install packages and build the entire FluentUI React Native repository. I.e. from the root of the repo:
-
-```sh
-yarn
-yarn build
-```
-
-2. Then go into `apps/fluent-tester/ios` folder and run `pod install` to pull in the project-level Cocoapod dependencies defined in the podfile, and to generate a valid xcworkspace:
-
-```sh
-cd apps/fluent-tester/ios
-pod install
-```
-
-Note: if you get the error: "CocoaPods could not find compatible versions for pod "MicrosoftFluentUI"," you may need to run `pod install --repo-update`.
-
-3. Return to the `fluentui-tester` directory and run `yarn ios` to launch the FluentUI Tester app:
-
-```sh
-cd ..
-yarn ios
-```
-
-## Dependencies
-
-Dependencies are managed by
-[`@rnx-kit/align-deps`](https://github.com/microsoft/rnx-kit/tree/main/packages/align-deps).
-If you're looking to upgrade `react-native`, use the interactive upgrade command:
-
-```sh
-yarn rnx-align-deps --set-version
-```
-
-This command will ensure that all relevant packages are bumped correctly.
-
-You can read more about this tool here:
-[`@rnx-kit/align-deps` design document](https://github.com/microsoft/rnx-kit/blob/main/docsite/docs/architecture/dependency-management.md)
-
-## Debugging
-
-You can debug native code in Xcode. To debug javascript code, you can either use standard web debugging, or you can use [React Native Tools](https://marketplace.visualstudio.com/items?itemName=msjsdiag.vscode-react-native) to debug directly in VS Code. The steps are as follows:
-
-1. Launch your test app + packager as you normally would
-2. Go the debug menu in VS Code and run the "Attach to Packager (iOS)" configuration
-3. Open the developer menu in your test app, and click debug
-4. You now should be able to set breakpoints and step through your code directly in VS Code.
-
-## Troubleshooting
-
-- The first time you yarn ios, you receive an error and have to run "FluentTester.xcworkspace" directly from Xcode. The workspace can be found in the apps/fluent-tester/ios folder. After running the workspace the first time from Xcode, you will be able to `yarn ios` from the CLI.
-- If the packager didn't launch in a separate terminal and your iOS simulator just shows a white screen for your app, you can run `yarn start` from apps/fluent-tester to launch it separately
-- If you get the error: "Unable to resolve module... None of these files exist:...", close the packager and restart it by running `yarn start`. Note: you need to restart the packager when you switch to a different platform (e.g. from macOS or Android to iOS), but once it restarts you can reload the tester apps on all running platforms at once.
-- If you want to do direct debugging via xcode, after the pod install, you can launch src/FluentTester.xcworkspace and build/run the scheme "ReactTestApp"
-- If you want to have a clean rebuild of the generated iOS project, you can do the following:
-
-```sh
-cd apps/fluent-tester/ios
-rm FluentTester.xcworkspace
-rm -rf Pods/
-pod install
-```

package/ios/Podfile

@@ -1,45 +0,0 @@
-# Switching between node-modules mode and pnpm mode requires changing how relative paths are handled.
-
-# (pnpm mode) allow modules to resolve correctly in upstream podfiles
-ENV['REACT_NATIVE_NODE_MODULES_DIR'] = File.join(__dir__, '../node_modules')
-
-# (pnpm mode)
-require_relative '../node_modules/react-native-test-app/test_app'
-# (node-modules mode)
-# require_relative '../../../node_modules/react-native-test-app/test_app'
-
-workspace 'FluentTester.xcworkspace'
-
-# (pnpm mode)
-react_native_path = "#{__dir__}/../node_modules/react-native"
-# (node-modules mode)
-# react_native_path = "#{__dir__}/../../../node_modules/react-native"
-
-# Resolve the pinned Fluent UI Apple release directly instead of enumerating its full
-# CocoaPods spec history, whose GitHub fallback is frequently rate-limited in CI.
-microsoft_fluent_ui_podspec = 'https://cdn.cocoapods.org/Specs/5/f/8/MicrosoftFluentUI/0.13.1/MicrosoftFluentUI.podspec.json'
-
-# fmt 11.0.2 (pinned by React Native 0.81) fails to compile with Xcode 26 / Apple Clang 21, which is
-# stricter about `consteval` (fixed upstream in fmt 11.1). Force fmt's compile-time consteval
-# format-string checking off so the bundled fmt builds. This is ABI-safe and avoids a version bump
-# (multiple pods pin fmt = 11.0.2). Re-applied on every `pod install`.
-def patch_fmt_consteval(installer)
-  fmt_base = File.join(installer.sandbox.root.to_s, 'fmt', 'include', 'fmt', 'base.h')
-  return unless File.exist?(fmt_base)
-
-  contents = File.read(fmt_base)
-  patched = contents.gsub('#  define FMT_USE_CONSTEVAL 1', '#  define FMT_USE_CONSTEVAL 0')
-  return if patched == contents
-
-  # CocoaPods marks pod sources read-only; make the file writable before patching.
-  File.chmod(0o644, fmt_base)
-  File.write(fmt_base, patched)
-  Pod::UI.puts '[FluentTester] Patched fmt base.h to disable consteval (Xcode 26 / Clang 21 workaround)'
-end
-
-use_test_app!(:post_install => ->(installer) { patch_fmt_consteval(installer) }) do |target|
-  target.app do
-    platform :ios, '16.0'
-    pod 'MicrosoftFluentUI', :podspec => microsoft_fluent_ui_podspec
-  end
-end