Unexpected red frame on the top when using telegram.

[freya zhang]

Information:
current build number: 357
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-06-22 13:04:23
version version: 357
version ubuntu: 20160622
version device: 20160526-af18709
version custom: 20160504-975-19-6

Steps:
1.Launch Telegrame and sign in your Telegrame account following the logging in steps.
2.Check the UI.

Actual result:
There is always extra red frame shown on top of the interface following the steps.
Expected result:
The UI should display normally,instead of displaying extra frame.

[Jin (jindallo)]

I confirmed with Telegram 2.2.23.0.

[Andrea Bernabei (faenil)]

Hi :)

Thanks for taking the time to report this!
The result is "expected", it is a consequence of
https://lists.launchpad.net/ubuntu-phone/msg20703.html

long story short, the Telegram app was using the old version of the Header component, which now shows a red frame to "push" all developers into switching to the new one, otherwise the app will stop working in one of the next updates.

The Telegram app has already been fixed to use the new Header component, so when the Telegram update will be released to the store the red frame will not be there :)
https://code.launchpad.net/~tpeeters/telegram-app/new-header/+merge/297787

[Jin (jindallo)]

Bug fixed,
and verified pass on developer side.

The change list is submitted as rev. 211,
below is the detail information.
    http://bazaar.launchpad.net/~libqtelegram-team/telegram-app/telegram/revision/211

Device Information:
    current build number: 468
    device name: mako
    channel: ubuntu-touch/rc-proposed/ubuntu
    last update: 2016-06-22 14:07:13
    version version: 468
    version ubuntu: 20160622
    version device: 20160401.1
    version custom: 20160622

[Jin (jindallo)]

Hello Ara,

Please help us QA this Telegram bug by using version: 2.2.23.1,
thanks for your help.

[Jin (jindallo)]

Hello Ethan,

Thanks for your help in advance,
please help us QA this issue.

[Jin (jindallo)]

Click package for testing attached.

[Ethan Chang (ethan.chang)]

Verified with ver2.2.24.0, I can no longer reproduce this issue.

[Jin (jindallo)]

Hello Penk,

This bug is verified and released at 2016.06.30,
you can "Fix Released" it directly,
thanks.

[Anupam (anupam207)]

Looks like this is an overlooked case: bug #1597702
and possibly this too: bug #1599504

[Olivier Tilloy (osomon)]

And yet another use case that was missed: bug #1600561.