Clang error during Cloud Make process for iOS

[MappyIan]

We use the Cloud Make process to create the installation files for our mobile app.  We're trying to create a final build before AppStudio is withdrawn next month but when trying today we received an error with the iOS build (the Android app was built successfully):

The error says:

clang: error: unable to execute command: Segmentation fault: 11 clang: error: clang frontend command failed due to signal (use -v to see invocation) ./../../Project/NetworkingPrivate.h:36:23: warning: 'QNetworkConfiguration' is deprecated [-Wdeprecated-declarations] /Users/appfactory/Qt5.15.6/5.15.6/ios/include/QtNetwork/qnetworkconfiguration.h:62:7: note: 'QNetworkConfiguration' has been explicitly marked deprecated here

This sounds like a problem with AppStudio or the Cloud Make process.  Can anyone from ESRI advise? @ChrisLeSueur @TrevorFrame 

[MappyIan · Accepted solution]

For what it's worth, I tried re-building the app (without making any changes whatsoever), and the third time round the Cloud Make process worked without error and the app built fine.  Maybe there was a glitch at Esri's end?  Who knows.

[josephcamerion]

I ran into this too when trying to push an iOS build. What worked for me was editing out any direct references to QNetworkConfiguration since it’s deprecated, then rebuilding locally with Xcode instead of relying on Cloud Make. Also Check your project is pointing at Qt 5.15.6 cleanly I had to wipe the build cache once to stop the segfaults. Might be worth a shot before AppStudio fully shuts down.

[josephcamerion]

I ran into this too when trying to push an iOS build. What worked for me was editing out any direct references to QNetworkConfiguration since it’s deprecated, then rebuilding locally with Xcode instead of relying on Cloud Make. Also Check your project is pointing at Qt 5.15.6 cleanly I had to wipe the build cache once to stop the segfaults. Might be worth a shot before AppStudio fully shuts down.

[MappyIan]

Thanks @josephcamerion, but we've deprecated our app now so won't be using this again.  I have to admit I was under the impression everything had been pulled by Esri, I didn't realise the Cloud Make process was still running.  Thanks for replying though.