The telegram always automatically dropped.

[freya zhang]

current build number: 290
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-03-30 12:57:03
version version: 290
version ubuntu: 20160330
version device: 20160310-193f49c
version custom: 20160324-945-18-69

Precondition:
Wifi is connected.

Steps:
1. Open Telegram
2. Move off the welcome page
3. Select your country
4. Type in you mobile number
5. Popup appears confirm your number
6. App returns to your mobile number input page with a spinning icon
7. Finally the app closes, note there is no crash and my log looks similar to the one that Evan attached.

Actual result:
The telegram always automatically dropped and the UI jumps to the entering identifying code interface again and again.

Expected result:
The telegram should not automatically dropped and it should work normally.

[TarotChen (tarotchen)]

Issue is easy to be reproduced under an unstable network

[Evan Wang (wsy324)]

The issue still exist on latest rc-proposed image r335

$ system-image-cli -i
current build number: 335
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-15 22:21:32
version version: 335
version ubuntu: 20160514
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9

[Dave Morley (davmor2)]

I managed to login on arale but not on krillin I am therefore assuming that this is a race condition of some sort as the original report was against arale and Tarot was under the impression it was down to the network being flaky.

I have ping jin and mzanetti on telegram and pointed them at this issue.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I see similar behaviour on latest bq M10 rc-proposed channel.

When I launch Telegram it goes to a blank screen:-

http://popey.com/~alan/screenshots/device-2016-05-17-144714.png

On my other device I get a notification in Telegram:-

"Telegram, [17.05.16 14:45]
Your login code: XXXXX

This code can be used to log in to your Telegram account. We never ask it for anything else. Do not give it to anyone!

If you didn't request this code by trying to log in on another device, simply ignore this message."

And the app is still blank.

[Dave Morley (davmor2)]

Reflashed krillin and can still reproduce it there. will continue testing around this tomorrow it is getting late here now.

[Evan Wang (wsy324)]

According to Jin's suggestion, if delete the folder /home/phablet/.cache/QML/Apps/com.ubuntu.telegram_telegram*, then it can login successfully, and not back to sign in page after doing some actions for a while.

[Evan Wang (wsy324)]

relaunched telegram after deleted the .cache/QML/App/com.ubuntu.telegram*

[Jin (jindallo)]

Checked with Evan,
delete QML cache recovers Telegram into normal.

And I also analyzed the logs, below pattern is minor to Telegram we can ignore:
    libust[19847/19876]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958)
    libust[19847/19875]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958)
if QML cache deleted does not work for you, please use this attached test click package to give it a try,
anything please let us know, and we will keep updating here.

[Dave Morley (davmor2)]

@jin so the click version you attached to the bug gets to the page in the steps and then resets to the welcome screen.

[Jin (jindallo)]

@Dave,

For now.. correct,
because from the log, it shows below:
    [20160517 22:01:58.582 EDT qml: authLoggedIn "false"
which means Telegram library does not get the phone number authenticated,
I follow our UX flow to make the app. as first start (delete .config/.cache),
to be honest, I don't really like this test click, but does it work to you??

And, did you try to delete the QML cache at first in testing?
Thanks.

[Jin (jindallo)]

After checked with Dave,
the attached click 2.2.4.1 does not work.

Please do not use that one to do the validation.

[Pat McGowan (pat-mcgowan)]

sorry assume the bug is still valid even though the attached click is not

[Pat McGowan (pat-mcgowan)]

is this still valid?

[Jin (jindallo)]

The multi-accounts feature is fixed/enhanced within milestone 31 as version 2.2.24.0,
and it is released already.

And the issue now is not reproducible, for me,
I will set it as Incomplete.

[Yuan-Chen Cheng (ycheng-twn)]

mark invalid. Feel free to reopen if you still saw this happens.