iOS builds

danwo tests a Release build of your app, with its JavaScript bundled in, so no Metro server runs during tests. danwo build-ios makes that build for the Simulator, without code signing.

Build itCopy Anchor Link

npx @danwo/cli build-ios app

built app/.danwo/builds/dd5eb4ac77e9aa9b.app in 111 s (log: app/.danwo/builds/build-ios.log)

app is the folder of your Expo project, which needs an ios.bundleIdentifier in its config. danwo:

1. runs expo prebuild --platform ios, which also installs the CocoaPods;
2. lets the app make plain HTTP calls, which the proxy routes to your backend;
3. runs xcodebuild for the Simulator, Release, for this Mac's CPU only, unsigned.

HTTPS needs nothing in the build: danwo trusts its certificate in the simulator itself.

Reuse itCopy Anchor Link

The build is kept under <project>/.danwo/builds/, keyed by a hash of the app's sources. An unchanged app isn't built again. Force a rebuild with --force, and see the tools' output with --verbose.

Build it from the configCopy Anchor Link

buildIos from @danwo/expo does the same inside your environment, so a test run always has a current build:

import { buildIos } from "@danwo/expo"

export async function currentApp(): Promise<string> {
  const build = await buildIos({ project: "app" })

  return build.app
}

Close the in-app browserCopy Anchor Link

On Android, a Custom Tab closes when Checkout links back to the app. On iOS, a Safari view stays over the app until the app closes it. Close it when the link arrives:

useEffect(() => {
  if (Platform.OS === "ios" && returned?.startsWith("danwoshop://"))
    WebBrowser.dismissBrowser().catch(() => undefined)
}, [returned])

openAuthSessionAsync closes itself, but iOS first asks the user to allow the sign-in, and the test taps Continue like a person would.

NextCopy Anchor Link