TelegramMessenger / TelegramMessenger/Telegram-iOS

Unable to write a message if you are a new user

Open
#308 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Swift
Stars
9k
Forks
2.9k
PR merge metrics
No merged PRs in 30d

Description

Checklist
  • I am reporting an issue in existing functionality that does not work as intended
  • I've searched for existing [GitHub issues]
Description

If you are a new user (new phone number, never use Telegram before) - you cannot start chat before switching to a settings tab. After going to the tab all working as expected.

Expected Behavior

I expect to see my messages in chat

Actual Behavior

Nothing happens. New messages in chat does not appear

Steps to Reproduce
  1. Download Telegram from App Store
  2. Login with new phone number
  3. Don't switch any tabs in tab bar
  4. Tap to new message button and find anybody by nickname and start chat with him
  5. New messages will not be sent
Environment

Device: iPhone/iPad X

iOS version: 11.4

App version: 6.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flow on an iPhone or iPad with iOS 11.4 and app version 6.2: use a new phone number, open a chat from the new-message button, and send a message before switching tabs. Compare this with the same flow after visiting Settings; done means new users can send messages and see them in chat without switching tabs.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.