[Allan]

Hello,

 

I’m having a hard time for building on the latest Android version with Felgo 3.

Is it possible to do or it’s required to migrate to Felgo 4 ?

 

Thanks.

[GüntherFelgo Team]

Hi Allan,

the standard Android configuration for the current Felgo version (both Felgo 3 and Felgo 4) is targeting Android 14 (API Level 34). To properly support the latest versions, depending on the API changes, both the Qt SDK and Felgo might have to include specific updates to build and run as expected. Also Qt Creator has to be able to work with the latest build tools like Android NDK/SDK.

We are currently in the process of preparing a new Felgo 4 release based on the latest Qt 6.8 LTS version. I don’t have all the details at hand, but usually with such major releases the default Android configuration of Felgo is also updated. This includes the SDK components, as well as services like Cloud Builds.

In general, we try to keep the supported Android versions the same across Felgo 3 and Felgo 4. But at some point Felgo 3 might have to stay behind, especially when Qt discontinues their support for Qt 5. So in the long run, updating to Felgo 4 will surely be necessary.

Do you have a specific requirement for Android 36 (or 35) in your project? If not, I would recommend to stay with the Felgo default configuration, as there’s the least friction here. If a different configuration produces issues, it needs a deeper investigation what exactly causes it, and how to properly set everything up.

If you are currently blocked in any way and need help with figuring things out, please contact us at support@felgo.com.
We can properly discuss all the details and look for the best approach to solve the issues.

Best,
Günther

[Allan]

Hello,

 

Thanks. It’s okay if we can’t build for Android 36. I was afraid that the problem was in my project or config…

Do you know when the support will end for Felgo 3 ?

 

Best.

 

[GüntherFelgo Team]

We do not have an official end date for Felgo 3. Official Qt support for Qt 5.15 ends some time in 2025 now. It will then depend on how long Qt will maintain support for evolving platform APIs (e.g. Android/iOS SDK and tools) on Qt 5.15. It will probably depend on customer needs and how much use Qt 5 still sees, but support is no longer guaranteed.

I assume that we can still safely use it for another 2 years at least, but that’s just a good guess from my side. We will keep Felgo 3 alive with maintenance updates and fixes for as long as it is viable. Development of new features will mostly target Felgo 4 though.