You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add a line like `127.0.0.1 zulipdev.com` to your `/etc/hosts` as
108
+
described [here](https://zulip.readthedocs.io/en/latest/subsystems/realms.html?highlight=zulipdev.com#working-with-subdomains-in-development-environment). Notice
109
+
there's already a line mapping 127.0.0.1 to `localhost`; this is what
110
+
makes the iOS simulator work with `http://localhost:9991`, as
111
+
described [here](https://github.com/zulip/zulip-mobile/blob/master/docs/howto/dev-server.md#ios-simulator-macos-only), without
112
+
having to configure `EXTERNAL_HOST`. Likewise, you won't have to
113
+
set `EXTERNAL_HOST` to get it to work on the simulator.
114
+
- A physical device won't be aware of the `zulipdev.com` domain;
115
+
you'll have to test on the simulator. To use the native flow, you
116
+
will be able to sign into the simulator at the "device" level just
117
+
as you would on a real device.
118
+
- Temporarily allow the app to access `http://zulipdev.com` as
119
+
described in the section on `NSAppTransportSecurity` exceptions,
120
+
below.
121
+
122
+
To test the native flow, which uses an Apple ID you've authenticated
123
+
with in System Preferences, go to the ZulipMobile target in the
124
+
project and targets list, and, under General > Identity, set the
125
+
Bundle Identifier field to your development App ID (a.k.a. Bundle ID).
126
+
If you've already installed a build that used the canonical Bundle
127
+
Identifier, you'll see two app icons on your home screen. Be sure to
128
+
open the correct one; it might be easiest to delete them both and
129
+
reinstall to prevent any doubt.
130
+
131
+
You should now be able to enter `http://zulipdev.com:9991` (not
132
+
`https://`), see the "Sign in with Apple" button, and use it
133
+
successfully.
134
+
135
+
## Adding `http://` exceptions to `NSAppTransportSecurity` in `Info.plist`
136
+
137
+
If you need to connect to `http://zulipdev.com` or another host with
138
+
the insecure `http://`, you'll need to tell the app to make an
139
+
exception under iOS's "App Transport Security", either to allow access
140
+
any host with `http://`, or just to specific domains.
141
+
142
+
These exceptions should never be committed to master, as there aren't
143
+
any insecure domains we want to connect to in production.
144
+
145
+
To add an exception for the `zulipdev.com` domain, add the following
0 commit comments