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
- Enter the SMS code you received and hit **Submit.**
71
72
72
73
73
-
6.**Save your platforms:**
74
+
### 6. **Save your platforms:**
74
75
75
76
76
77
- Tap the **Platforms** tab.
@@ -88,8 +89,7 @@ Steps to Use the Platform Feature:
88
89
- When successful, the icon will light up!
89
90
90
91
91
-
92
-
7.**Choose a Gateway Client:**
92
+
### 7. **Choose a Gateway Client:**
93
93
94
94
95
95
- Tap the **Country** tab.
@@ -106,7 +106,7 @@ Steps to Use the Platform Feature:
106
106
- Alternatively, you can select a gateway client from the list that pops up when you hit the send button after composing your message.
107
107
108
108
109
-
8.**Send a message:**
109
+
### 8. **Send a message:**
110
110
111
111
112
112
- On the **Recent** page, tap the **Compose icon.**
@@ -135,38 +135,41 @@ Your encrypted message will appear there, just hit Send.*
135
135
136
136
Our **"Store Tokens On-Device"** feature gives you more control over your account credentials by keeping your access tokens on your phone instead of on the RelaySMS servers. This tutorial walks you through how to enable or disable this feature and how to refresh Twitter tokens when using local storage.
137
137
138
-
**Enabling On-Device Token Storage**
138
+
## **Enabling On-Device Token Storage**
139
139
140
140
To start storing your access tokens locally on your device:
@@ -177,35 +180,32 @@ To stop using local token storage and go back to storing tokens on the cloud:
177
180
- However, **new tokens** generated after this will be saved to the **RelaySMS cloud server**, not your device.
178
181
179
182
180
-
181
-
**Refreshing Twitter Tokens (For On-Device Use Only)**
183
+
### **Refreshing Twitter Tokens (For On-Device Use Only)**
182
184
183
185
Due to Twitter's security limitations, tokens stored on your device can only be used **once per tweet**. To send another tweet, you’ll need to **revoke and restore** the token.
184
186
185
187
Here’s how:
186
188
187
-
1. After sending a tweet, you’ll receive an **SMS delivery status message**. If you're using an on-device token, this message will include a **refreshed Twitter token**.
188
-
189
+
### 1. After sending a tweet, you’ll receive an **SMS delivery status message**. If you're using an on-device token, this message will include a **refreshed Twitter token**.
189
190
190
-
2.**Copy the entire SMS message** (as-is).
191
191
192
+
### 2. **Copy the entire SMS message** (as-is).
192
193
193
-
3. Open the **RelaySMS app** and go to the **Inbox** section.
194
194
195
+
### 3. Open the **RelaySMS app** and go to the **Inbox** section.
195
196
196
-
4.**Paste** the full SMS message into the inbox.
197
197
198
+
### 4. **Paste** the full SMS message into the inbox.
198
199
199
-
5. The app will automatically extract and refresh your Twitter token.
200
200
201
+
### 5. The app will automatically extract and refresh your Twitter token.
201
202
202
-
6. You’re now ready to send your next tweet.
203
+
204
+
### 6. You’re now ready to send your next tweet.
203
205
204
206
205
207
Repeat this process **after every Twitter message** if you're using local token storage.
206
208
207
209
208
-
209
-
210
210
## [How to Use the On-Device Token Storage Feature](/docs/On-Device%20Tutorial/On-DeviceToken#how-to-use-the-on-device-token-storage-feature)
3. Tap the three dots once more and choose **Add HTTPS Gateway Server**.
62
-
63
-
4. Two gateway servers need to be added in order for both Android and iOS users of the RelaySMS app to use the gateway client to publish their messages online.
48
+
Tap on the menu dots in the top right corner of the routed messages page.
49
+
Tap on the three dots in the top right corner of the Gateway clients messages page.
50
+
Tap the three dots once more and choose Add HTTPS Forwarders.
0 commit comments