iOS release build fails (Qt World Summit Conference App)

hskoglund

I built your app with 7.3 (can't start 8.0, that silly "have to agree to license" keep popping up in Qt Creator :-(

ekkescorner

@hskoglund Xcode8 - I went thru all the problems and also https://bugreports.qt.io/browse/QTCREATORBUG-16968
it's working for other projects - so it's not a generic problem with Xcode8 I think
only this project causes release build problems

hskoglund

Should google on how to get rid of "Xcode not set up properly.." just a minute..

ekkescorner

@hskoglund think it was running xcodebuild -license from terminal

hskoglund

Did that, not enough. Think I have to edit the mkspecs...

hskoglund

https://bugreports.qt.io/browse/QTBUG-56004 did that, didn't help. Maybe because I upgraded to Sierra (macOS 10.11) yesterday :-(
I have time later tonight, can look into it more then...

ekkescorner

@hskoglund thx looking into this.

ekkescorner

BTW: thinking to clone my app and try it out if it works.
At first I want to know if it is safe to manage the same App (same name and content of .pro), but at different file locations in Qt Creator without any trouble.
thx for any hints

ekkescorner

also asked in Interest and Qt Creator List.
Eike Ziller found the reason why release build fails under iOS:

That’s a crash in Qt Quick Compiler, which looks like it is https://bugreports.qt.io/browse/QTBUG-54482

Eike saved my day :)
looked at the bugreport and immediately know the reason and fixed it:

Timer {
            id: autoVersionCheckTimer
            interval: 3600000 // 60*60*1000
            repeat: false
            onTriggered: {
                appWindow.doAutoVersionCheck()
            }
        }

just built the release, uploaded to AppStore and added build to TestFlight
now all projects are working with Qt 5.7 and Xcode8 :)

ekke

hskoglund

Good news!
(yesterday evening I tested building your app on Xcode 8 and it worked fine (of course!), I thought I'd sleep on it. So it was an overflow bug, good it's solved.)
Also yesterday I forgot rule #1: always google for the error message first (if you do, you get that QTBUG-54482 as the first hit, the bug report is from June 30) but since it worked for me, it wasn't obvious :-)

ekkescorner

@hskoglund I did a search but with the wrong line ;-)

so you have no issues with Sierra ?

hskoglund

@ekkescorner No Sierra seems quite harmless, I said no to installing Siri and the only new thing seems some new nice wallpapers with the Sierra mountains.
However getting Qt Creator 4.10 to build a sample app for iOS required editing 2(!) different .prf files in the mkspecs subdirectory jungle, thankfully it was documented on Stackoverflow. But I think that is more because of Xcode 8 and less because of Sierra.

ekkescorner

@hskoglund good to know. and yes: the mkspecs changes are caused by Xcode8.

SGaist

I confirm it's Xcode 8 that changed some stuff again. The next round of Qt releases are already fixed.

hskoglund

Yes indeed I just discovered, Xcode 8 has really moved my cheese.
For many years I've had my Xcode keyboard plugin, but now Xcode 8 has obsoleted that and introduced "Xcode source editor extensions".
Reminds me of when Microsoft changed the Visual Studio plugin infrastructure for VS2015 (was bad news for the Qt VS Addin) Apple had to do same kind of "improvement" now :-(

ekkescorner

@SGaist said in iOS release build fails (Qt World Summit Conference App):

I confirm it's Xcode 8 that changed some stuff again. The next round of Qt releases are already fixed.

yep - new Qt releases will help with mkspec changes
but there are also changes required in .pro because Xcode has new requirements for signing apps
I had to add under ios/:

QMAKE_XCODE_CODE_SIGN_IDENTITY = "iPhone Developer"
MY_DEVELOPMENT_TEAM.name = DEVELOPMENT_TEAM
MY_DEVELOPMENT_TEAM.value = XXX42XXX42
QMAKE_MAC_XCODE_SETTINGS += MY_DEVELOPMENT_TEAM

where team value can be found at Apple Developer/account membership
using Xcode 7.3 there's no need to add this

SGaist

I saw some people already experiencing an issue with that.

Seems like Xcode 8 is a bit less intuitive...

Thanks for the hint