[Darren]

Hi,

I have just returned to Felgo after a summer away.

I am trying to update to the latest version.  Currently I have Qt 5.8, Qt Creator 4.2.1 and Felgo 2.10.1.

When I try to update using the maintenance tool, it begins retrieving information from the meta-repository, but when it gets to 53% of the way through, I receive the following error message:

Network error while downloading ‘https://sdk.felgo.com/qt/online/qtsdkrepository/windows_x86/desktop/qt5_57/qt.57.qtdatavis3d.win32_msvc2015/5.7.0-1meta.7z’: Connection closed.

 

What am I doing wrong?

Thank you

Darren.

 

[Marcin]

Hi Darren,
For me it looks like the installer tries to update even qt 5.7 libraries which, looks like, are no longer available on Felgo servers.
Does the Maintennce tool, when you click Update, on the libraries list show any qt 5.7 libraries?
If yes, if you uncheck them so won’t be added, does the update work?
In general I think only qt 5.9 libraries are supported now so probably removing everything below is a good option.

[Darren]

This solution half worked – I went into Settings before running the update.  Then I unchecked every Qt repository that was less than 5.9.  It performed the update, and I am able to run my game on the desktop using the kit Felgo Desktop (Qt 5.9.0 MinGW).

However I cannot now find a kit for android or IOS.

If I try to add/remove components in the maintenance tool, Qt 5.9 does not show up so there is no option to add android or IOS kits.

Also, in Qt Creator, if I select Help/About, it says I have: Qt Creator 4.3.0, based on Qt.5.8.0, built in May 2017.

This doesn’t sound right?

[GüntherFelgo Team]

Hi Darren!

The iOS and Android Kits can usually be added with the MaintenanceTool as you described. As your installation of Felgo and MaintenanceTool was quite old already, I recommend to remove Felgo completely and do a fresh install of the latest version, you can download it here.

Best,
Günther

[Darren]

Thanks Günther – I’ve deleted my old Felgo and done a fresh install.

The ABOUT box in QT Creator still says that it was built in May 2017 and is based on Qt 5.8… although I’m definitely running 5.9 now and don’t have 5.8 installed.

The maintenance tool allowed me to add Android after my install, and it shows up in my kits (not tested yet though).

But I still can’t see the iOS kit anywhere.  Has it changed?  It is not in my options for update.

Thanks

Darren.

[Marcin]

Hi Darren,
Just to update you, my Qt Creator in About also shows Qt 5.8 built in May.
I don’t think this is any issue.
Looks like it doesn’t matter that it wasn’t built with the same Qt version as the libraries Felgo uses.
I think Felgo uses more official stable QtCreator version and newest official wasn’t built with Qt 5.9?
I don’t think Felgo rebuilds QtCreator with newest Qt version.
Not sure.

As for iOS. That is really weird, on Mac I have no problem with iOS kits. I see macOS under Qt 5.9.
Of course on no Mac machines you probably won’t see macOS libraries in Qt. At least I don’t.
It looks like for iPhone there is no specific library in Qt, macOS is the only thing I use and it works.

[GüntherFelgo Team]

Hi Darren!

Building for iOS is only possible with a mac computer, if you are running Felgo on windows the iOS Kits are thus not available.

The “About” info in Qt Creator is not an issue. We are not building Qt Creator ourselves, but ship the official Qt Creator build with some customizations like our Qt Creator plugin.

Do you have issues with building for Desktop or Android or does everything work fine now?

[Darren]

Hi Guys,

Sorry for the delay – I’m away on a course during the week at the moment.

Thanks for the help – sorry for being an idiot – I forgot you don’t get the IOS without being on the Mac.  I haven’t actually updated QtCreator on my Mac yet and am working on my Pc. I’ll cross that hurdle another time!

I have managed to get the latest version of Qt Creator installed and working on my machine now.  It is Qt Creator 4.4.

It appears to work perfectly on the desktop and I can run my game without any issues.

When I try to use Android though, I get the following errors, which appear to be related to Gradle (I have updated my Gradle to the latest version now, which is 4.2 but still have the same problem):

 

FAILURE: Build failed with an exception.

* Where:

Build file ‘E:\Git\tankz\build-Tankz-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug\android-build\build.gradle’ line: 18

* What went wrong:

A problem occurred evaluating root project ‘android-build’.

> Failed to apply plugin [id ‘com.android.application’]

> Gradle version 2.2 is required. Current version is 3.4. If using the gradle wrapper, try editing the distributionUrl in E:\Git\tankz\build-Tankz-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug\android-build\gradle\wrapper\gradle-wrapper.properties to gradle-2.2-all.zip

* Try:

Run with –stacktrace option to get the stack trace. Run with –info or –debug option to get more log output.

BUILD FAILED

Total time: 1.572 secs

Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils

Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils

Building the android package failed!

— For more information, run this command with –verbose.

21:44:19: The process “E:\FelgoSDK\5.9\android_armv7\bin\androiddeployqt.exe” exited with code 14.

Error while building/deploying project Tankz (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.9.0 for Android armv7))

When executing step “Build Android APK”

[Marcin]

Hi Darren,
Hopefully this is the last issue you encounter 🙂
It is a common issue and one time fix is possible(one time as until you manually delete files in build directory).
Please check this post and previous one:
https://felgo.com/developers/forums/t/facebook-plugin-examples-arent-working#post-16451

Not sure if it’s covered in any docs/known issues yet, if not, maybe it would be a good idea to create something like this in Android deployment section.

[Darren]

Hi Marcin,

Thank you for your help – changing the gradle line to gradle-2.10-all.zip didn’t work, but when I changed it to gradle-2.2-all.zip it DID get past this step and appears to work.

Unfortunately I have a talent for creating issues – the build failed at a later step with this error:

 

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ‘:mergeDebugResources’.

> Crunching Cruncher ic_launcher.png failed, see logs

* Try:

Run with –stacktrace option to get the stack trace. Run with –info or –debug option to get more log output.

BUILD FAILED

Total time: 1 mins 19.351 secs

Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils

Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils

Building the android package failed!

— For more information, run this command with –verbose.

07:56:22: The process “E:\FelgoSDK\5.9\android_armv7\bin\androiddeployqt.exe” exited with code 14.

Error while building/deploying project Tankz (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.9.0 for Android armv7))

When executing step “Build Android APK”

[Marcin]

Hi Darren,
Sorry, it wasn’t that clear.
The Gradle issue is fixable by putting the version you get in error message, not exact the same I used in the link.
Like you saw, your error was Gradle version 2.2 is required. so this version you need to use.

Fortunately in that issue the app itself gave some hints:
“try editing the distributionUrl in E:\Git\tankz\build-Tankz-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug\android-build\gradle\wrapper\gradle-wrapper.properties to gradle-2.2-all.zip”

As for the second issue, didn’t see that yet.
Looks like some assets issue but don’t have a clue yet what to do here.
I think the file is missing or the app can’t read etc.
ic_launcher.png is the app icon and can be most of the time found in: android/res/drawable-*/ic_launcher.png.
All drawable directories should have one.

[GüntherFelgo Team]

Hi Darren,

editing the gradle-wrapper.properties setting to the version that is mentioned solves the first issue.

About the Cruncher is_launcher.png problem:
This issue occurs more or less randomly when building for Android. In our experience the build is usually successful again without a single change just by hitting build/run e.g. a second or third time after it fails initially. A fresh re-build can also help (right-click on project in Qt Creator, choose “Clean”, choose then “Run qmake”).

Best,
Günther

[Darren]

Günther,

As always you show that you really know your stuff… your solution worked perfectly!

I rebuilt everything and then my game deployed to my android phone with no problems.

Thank you to you and Marcin for your help.

Darren.