mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-29 07:52:37 +01:00
Update content of files
This commit is contained in:
parent
d88ee86b04
commit
3b92210e56
3 changed files with 18 additions and 18 deletions
|
@ -215,7 +215,7 @@
|
|||
</div><div class="tr-section-col col-lg-4 col-xs-6">
|
||||
<div class="tr-section-wrap"><a href="/en/android_x/settings/" class="tr-section">
|
||||
<div class="tr-section-cover cover7"></div>
|
||||
<div class="tr-section-caption">Settings (1192)</div>
|
||||
<div class="tr-section-caption">Settings (1194)</div>
|
||||
</a></div>
|
||||
</div><div class="tr-section-col col-lg-4 col-xs-6">
|
||||
<div class="tr-section-wrap"><a href="/en/android_x/camera_and_media/" class="tr-section">
|
||||
|
@ -240,7 +240,7 @@
|
|||
</div><div class="tr-section-col col-lg-4 col-xs-6">
|
||||
<div class="tr-section-wrap"><a href="/en/android_x/unsorted/" class="tr-section">
|
||||
<div class="tr-section-cover cover0"></div>
|
||||
<div class="tr-section-caption">Unsorted (715)</div>
|
||||
<div class="tr-section-caption">Unsorted (713)</div>
|
||||
</a></div>
|
||||
</div>
|
||||
</section></section>
|
||||
|
|
|
@ -2429,6 +2429,14 @@
|
|||
"singular": "Finding by Phone Number"
|
||||
}
|
||||
},
|
||||
"FirebaseErrorResolve": {
|
||||
"url": "https://translations.telegram.org/en/android_x/settings/FirebaseErrorResolve",
|
||||
"photo_url": "https://telegra.ph/file/p/1fae32add9a/00478e5df53195bcae92b17.jpg?c=62,103,280,280,280,280",
|
||||
"has_binding": true,
|
||||
"values": {
|
||||
"singular": "Tap to resolve issue"
|
||||
}
|
||||
},
|
||||
"ForceBuiltinDecoding": {
|
||||
"url": "https://translations.telegram.org/en/android_x/settings/ForceBuiltinDecoding",
|
||||
"photo_url": "https://telegra.ph/file/p/6c0223aed90/8179138a6425fcd8dbc9217.jpg?c=10,745,364,364,280,280",
|
||||
|
@ -4042,6 +4050,14 @@
|
|||
"singular": "**Telegram X** was unable to display some notifications from <mark class=\"token\">%1$s</mark> due to an unknown system error.<br/><br/>Please make sure:<br/>• All system updates are installed<br/>• Telegram X is up-to-date<br/>• There are no notification restrictions in system settings.<br/><br/>If the steps above do not help, you might want to share the detailed error report to @tgandroidtests, or look up for troubleshooting tips for your device."
|
||||
}
|
||||
},
|
||||
"NotificationsGuideFirebaseError": {
|
||||
"url": "https://translations.telegram.org/en/android_x/settings/NotificationsGuideFirebaseError",
|
||||
"photo_url": "https://telegra.ph/file/p/1fae32add9a/00478e5df53195bcae92b17.jpg?c=0,154,600,636,264,280",
|
||||
"has_binding": true,
|
||||
"values": {
|
||||
"singular": "**Firebase Services** have failed to function properly due to error: <mark class=\"token\">%1$s</mark><br/><br/>Notifications may arrive with big delays or not arrive at all without them.<br/><br/>Please make sure:<br/>• Google Play Services are installed and up-to-date<br/>• Telegram X is up-to-date<br/>• Firebase services are enabled<br/>• They are not blocked by your Internet service or DNS provider<br/>• If you have firewall or ad blocking software, Firebase domains are whitelisted<br/>• You can see 404 message in a browser on this page: https://firebaseinstallations.googleapis.com/<br/>• System date and time is correct<br/>• Problem doesn't go away after restarting your device<br/>• All system updates are installed.<br/><br/>If the steps above do not help, you might want to share the detailed error report to @tgandroidtests and look up for additional troubleshooting tips for your device."
|
||||
}
|
||||
},
|
||||
"NotificationsGuideFirebaseUnavailable": {
|
||||
"url": "https://translations.telegram.org/en/android_x/settings/NotificationsGuideFirebaseUnavailable",
|
||||
"photo_url": "https://telegra.ph/file/p/3cd6e367375/b1606020b19f6fc5a9c0f17.jpg?c=0,0,600,376,278,174",
|
||||
|
|
|
@ -1448,14 +1448,6 @@
|
|||
"singular": "Sorry, this feature is currently not available in your region."
|
||||
}
|
||||
},
|
||||
"FirebaseErrorResolve": {
|
||||
"url": "https://translations.telegram.org/en/android_x/unsorted/FirebaseErrorResolve",
|
||||
"photo_url": null,
|
||||
"has_binding": true,
|
||||
"values": {
|
||||
"singular": "Tap to resolve issue"
|
||||
}
|
||||
},
|
||||
"FirebaseErrorResolveShareError": {
|
||||
"url": "https://translations.telegram.org/en/android_x/unsorted/FirebaseErrorResolveShareError",
|
||||
"photo_url": null,
|
||||
|
@ -2772,14 +2764,6 @@
|
|||
"singular": "Notifications for current account are disabled in system settings.<br/><br/>To enable notifications:<br/>• Tap System Notification Settings<br/>• Find «<mark class=\"token\">%1$s</mark>» notification category.<br/>• Turn toggle on to unblock notifications."
|
||||
}
|
||||
},
|
||||
"NotificationsGuideFirebaseError": {
|
||||
"url": "https://translations.telegram.org/en/android_x/unsorted/NotificationsGuideFirebaseError",
|
||||
"photo_url": null,
|
||||
"has_binding": true,
|
||||
"values": {
|
||||
"singular": "**Firebase Services** have failed to function properly due to error: <mark class=\"token\">%1$s</mark><br/><br/>Notifications may arrive with big delays or not arrive at all without them.<br/><br/>Please make sure:<br/>• Google Play Services are installed and up-to-date<br/>• Telegram X is up-to-date<br/>• Firebase services are enabled<br/>• They are not blocked by your Internet service or DNS provider<br/>• If you have firewall or ad blocking software, Firebase domains are whitelisted<br/>• You can see 404 message in a browser on this page: https://firebaseinstallations.googleapis.com/<br/>• System date and time is correct<br/>• Problem doesn't go away after restarting your device<br/>• All system updates are installed.<br/><br/>If the steps above do not help, you might want to share the detailed error report to @tgandroidtests and look up for additional troubleshooting tips for your device."
|
||||
}
|
||||
},
|
||||
"NotificationsGuideSyncAppOff": {
|
||||
"url": "https://translations.telegram.org/en/android_x/unsorted/NotificationsGuideSyncAppOff",
|
||||
"photo_url": null,
|
||||
|
|
Loading…
Reference in a new issue