It's Qt 5.12 time.

dobey

And PLEASE avoid doing any upgrade on your devices with apt if you were doing that at any point, until further notice. Your device will almost certainly break currently if you do, requiring you to flash again with the installer.

Thanks!

lduboeuf

@dobey ubports-qa is concerned?

dobey

@lduboeuf Yes, as it attempts to do an upgrade which pulls in other packages. It should not be used currently either.

lduboeuf

@dobey maybe a post on ubports-qa and dev Telegram group is needed

jezek

@dobey Is crossbuilder safe?

dobey

@jezek Not for building against Ubuntu Touch. Anything using the Ubuntu Touch apt repositories will be problematic until Qt 5.12 transition is done.

jezek

@dobey Ok, I will stop using crossbuilder for deployment to phone, cause it uses apt repositories, for a while. Will look forward for a notification when it's safe. Thanks.

poVoq

Will there be a quick guide for qt app developers on what has changed and suggestions on how to updated your apps?

jonius

@povoq with latest Clickable you can test your app in Desktop Mode with CLICKABLE_QT_VERSION=5.12 clickable desktop. That env var works for debugging on device as well, given you got Qt 5.12 installed there.

dobey

OK. All the necessary PRs have been merged (there will still be more fixes to come as well though). We should have new devel channel images available for updating your devices soon.

Anyone who used ubports-qa to test the xenial_-_qt-5-12 and related branches should reset their devices by flashing again with the installer, or switching to rc channel in settings to get a full flash. Those branches are no longer valid. There's still a little rebase work needed for mainline and possibly android9 devices, but should be done soon.

poVoq

@dobey Is it pushed already?

Not sure if related, but the 196 update on my OnePlus3 just failed to install and now I am stuck at the boot logo with a broken install (error seems to have been: "couldn't load bitmap icon_error (error -7)" which is also shown in the ubports recovery now).

dobey

@povoq Yes. It seems like maybe some delta images were messed up somehow (unrelated to Qt 5.12 itself).

Can you flash the device again with the installer?

poVoq

Dekko2 seems to be partially broken with 5.12? Notifications still come in, but launching it results in a white screen only on my phone.

PhoenixLandPirat

@povoq Might be wrong, but I think that that is an issue that Dekko developers have to fix?

There are a few extra issues with the OnePlus 3 also, such as the camera, and lack of message bubbles in the messaging app.

poVoq

@phoenixlandpirat Yeah I guess. I wish Dekko2 was treated a bit more like a core app, as it really is more or less one.

PhoenixLandPirat

@povoq There are several core apps that don't have maintainers that don't get updates, or only once in a blue moon, unfortunately.

dobey

@povoq They were made away of the issue at the same time as Teleports (which has been fixed). Dekko is using qbs and doing a few things a little differently though, so I'm not sure how to correctly update the quickflux dep there.

poVoq

Anyone also noticed that forcing the screen to stay on seems to have stopped working? At least on Puremaps the navigation is broken because of the screen turning off after a short while.

kugiigi

The issue on splash screen seems to be back or is that something that developers has to adjust? My apps use SVG and they are displayed small unlike before.

Fla

@kugiigi I think you need to adjust it yes.