Paul Frazee
1044c8bb8b
* Dont append the server's domain name when a custom domain is used * Update the settings look & feel and add a tool to remove accounts from the switcher * Try not rendering the bottomsheet when no modal is active. There are cases where the bottomsheet decides to show itself when it's not supposed to. It seems obvious to do what this change is doing -- just dont render bottomsheet if no modal is active -- but previously we experienced issues with that approach. This time it seems to be working, so we're gonna yolo try it. * Implement a handle-change modal with support for custom domains (closes #65)
Bluesky
Build instructions
- Setup your environment using the react native instructions.
- Setup your environment for e2e testing using detox:
- yarn global add detox-cli
- brew tap wix/brew
- brew install applesimutils
- After initial setup:
cd ios ; pod install
- Start the dev servers
git clone git@github.com:bluesky-social/atproto.gitcd atprotoyarncd packages/dev-env && yarn start
- Run the dev app
- iOS:
yarn ios - Android:
yarn android - Web:
yarn web
- iOS:
- Tips
npx react-native infoChecks what has been installed.- On M1 macs, you need to exclude "arm64" from the target architectures
- Annoyingly this must be re-set via XCode after every pod install
- The android simulator won't be able to access localhost services unless you run
adb reverse tcp:{PORT} tcp:{PORT}- For instance, the localhosted dev-wallet will need
adb reverse tcp:3001 tcp:3001
- For instance, the localhosted dev-wallet will need
- For some reason, the typescript compiler chokes on platform-specific files (e.g.
foo.native.ts) but only when compiling for Web thus far. Therefore we always have one version of the file which doesn't use a platform specifier, and that should bee the Web version. (More info.)
Various notes
Debugging
- Note that since 0.70, debugging using the old debugger (which shows up using CMD+D) doesn't work anymore. Follow the instructions below to debug the code: https://reactnative.dev/docs/next/hermes#debugging-js-on-hermes-using-google-chromes-devtools
Running E2E Tests
- Make sure you've setup your environment following above
- Make sure Metro and the dev server are running
- Run
yarn e2e - Find the artifacts in the
artifactfolder
Polyfills
./platform/polyfills.*.ts adds polyfills to the environment. Currently this includes:
- TextEncoder / TextDecoder