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
Copy file name to clipboardExpand all lines: apps/mobile/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,8 @@
14
14
10.`cd ..` (leave the ios folder)
15
15
11.`yarn start` (must be within apps/mobile) launches `metro`, the heart of the mobile dev experience
16
16
12. You will see the metro options for launching the different environments and the devtools, and reload
17
-
13. You will also need to run `yarn run android` to open the correct ports for the android emulator to be able to access the backend. Once it opens the ports, you can just cancel the rest of its actions
17
+
13. To build/install the android app run `yarn run android` in a different terminal window.
18
+
13. To build/install the ios app run `yarn run ios` in a different terminal window. If it fails with error code 70 you need to specify the destination device or simulator you want to build for. You can select which to build for by running `yarn react-native run-ios --list-devices`
18
19
19
20
## Quick debug
20
21
1. Most code changes will hot-reload into the devices; sometimes you need to hit 'r' in the metro terminal instance to reload (what you see afer hitting `yarn start`)
@@ -123,4 +124,4 @@ Real-time updates are handled in urql by subscriptions. These are integrated int
123
124
### Push Notification testing
124
125
This requires tweaks to your local backend env; PUSH_NOTIFICATIONS_TESTING_ENABLED needs to be set to TRUE or sometimes you can get away with just adding specific hylo user ids to the HYLO_TESTER_IDS. And you'll need to add valid OneSignal ID and key to your backend env
125
126
126
-
After you have done this, the quick-n-dirty way to test is to go to the OneSignal model in the backend, insert a url you want to test, and then trigger a notification on a user that you have control of, and that exists in both in your local db and the prod db.
127
+
After you have done this, the quick-n-dirty way to test is to go to the OneSignal model in the backend, insert a url you want to test, and then trigger a notification on a user that you have control of, and that exists in both in your local db and the prod db.
0 commit comments