barefootstache<p><a href="https://qoto.org/tags/DailyBloggingChallenge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DailyBloggingChallenge</span></a> (78/100)</p><p>It seems like <a href="https://qoto.org/tags/Telegram" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Telegram</span></a> has an initial re-sign-in block on a new device when it is not an <a href="https://qoto.org/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Android</span></a>/ <a href="https://qoto.org/tags/iOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iOS</span></a> device. This mean logging into e.g. <a href="https://qoto.org/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GrapheneOS</span></a> doesn’t permit one to use SMS as an authentication method rather one needs to use an existing install on a device that was registered.</p><p>How to resolve:</p><ol> <li>Install Telegram on the initial operating system or device <code>K</code>.</li> <li>Authenticate it by receiving the code via SMS, which can be any secondary device.</li> <li>Install Telegram on the new device and authenticate it by getting the code via a message on Telegram on device <code>K</code>.</li></ol><p>Remarks:</p><p>It could only be an issue if installing a fork of Telegram like <a href="https://qoto.org/tags/Forkgram" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Forkgram</span></a>.</p>