TelegramMessenger / TelegramMessenger/Telegram-iOS

Logout caused assertion failed

Open
#229 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

Describe the issue that you are experiencing
When I choose "Log out" after selecting my account, the app crashed with Assertion failed at line 597 of SqliteValueBox.swift.

In Xcode console log:

SQL error 1: table t10 already exists on SQL
Assertion failed: file /path/to/Telegram_v5.13.1/telegram-ios/submodules/Postbox/Sources/SqliteValueBox.swift, line 597
2020-01-20 18:00:04.898301+0800 Telegram[65473:7368242] Assertion failed: file /path/to/Telegram_v5.13.1/Telegram_v5.13.1/telegram-ios/submodules/Postbox/Sources/SqliteValueBox.swift, line 597
Expected Behavior

Tell us what should happen
Logging out shouldn't crash the app

Actual Behavior

Tell us what happens instead
Log out crashed the app

Steps to Reproduce
  1. Choose the account in Settings
  2. Select "Log out"
  3. crash app
Environment

Device: iPhone/iPad X
iPhone Xr simulator

iOS version: 13.X
iOS 13.3

App version: 5.X
5.13.1

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

Inspect submodules/Postbox/Sources/SqliteValueBox.swift at line 597 and reproduce the logout flow in an iPhone XR simulator. Confirm completion by logging out without the table t10 already exists SQL error or assertion crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, swift
Domain
databases, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.