Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business

Forums

OverviewFelgo 3 Support (Qt 5) › How to debug ios app, build via cloud build

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #23485

    Peter

    Hi, so far I can ditribute my app to Testflight with receiving an email: <b>ITMS-90078: Missing Push Notification Entitlement</b>

    The crash log of my IPhone looks like:

    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000008
    VM Region Info: 0x8 is not in any region.  Bytes before following region: 4375134200
          REGION TYPE                      START - END             [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
          UNUSED SPACE AT START
    --->  
          __TEXT                 0000000104c74000-0000000104dd8000 [ 1424K] r-x/r-x SM=COW  ...pp/iosproject
    
    Termination Signal: Segmentation fault: 11
    Termination Reason: Namespace SIGNAL, Code 0xb
    Terminating Process: exc handler [447]
    Triggered by Thread:  0
    
    Thread 0 name:
    Thread 0 Crashed:
    0   iosproject                    	0x00000001059e3cd0 0x104c74000 + 14089424
    1   iosproject                    	0x0000000105d1f710 0x104c74000 + 17479440
    2   iosproject                    	0x0000000105a42340 0x104c74000 + 14476096
    3   iosproject                    	0x0000000105a42498 0x104c74000 + 14476440

    So I dont have any meaningful symbols in it. How can I receive such an error log with debug symbols?

     

    #23487

    Peter

    I could start the ipa with Instruments Zombies scheme. The console output is the following:

    QML debugging is enabled. Only use this in a safe environment.
    Warning: 
    
    #####################################
    WARNING: you are building a publishBuild, but your mainQmlFile entry point is not loaded from RESOURCES but with DEPLOYMENTFOLDERS. This would allow others to inspect your QML sources! To avoid that and to secure your source code, perform the following steps:
    1.) Create a .qrc file similar to the ones from the Felgo demos and enable RESOURCES += resources.qrc in your .pro file.
    2.) Remove the DEPLOYMENTFOLDERS += qmlFolder line from the .pro file.
    3.) Set the main qml file to "qrc:/qml/Main.qml" in your main.cpp.
    #####################################
    
     ((null):0, (null))
    Warning: QQmlApplicationEngine failed to load component ((null):0, (null))
    Warning: file:///private/var/containers/Bundle/Application/XX-XX-XX-XX-XX/iosproject.app/qml/Main.qml:12 Type GameWindow unavailable
    qrc:/qml/Felgo/core/GameWindow.qml:25 Type GameWindowApplicationWindow unavailable
    qrc:/qml/Felgo/core/GameWindowApplicationWindow.qml:667 Type GameWindowItem unavailable
    qrc:/qml/VPlay/core/GameWindowItem.qml:796 Type Settings unavailable
    qrc:/qml/VPlay/core/Settings.qml:14 Type Storage unavailable
    qrc:/qml/VPlay/core/Storage.qml:2 module "QtQuick.LocalStorage" is not installed
     ((null):0, (null))
    <End of Run>

     

    #23488

    Peter

    update: I installed qt on macOS, run qmake and build it via xcode. This binary is running on 2 different iPhones properly. So the issue is: What does the cloud build different from the local xcode build.

    #23522

    Alex
    Felgo Team

    Hi Peter,

    Thanks for sharing the information. You mentioned you used “Instruments Zombies scheme”. Did you resign the app and deploy it to the device before starting up Instruments (TestFlight builds are not debuggable usually)?

    Can you also let us know if you use the DEPLOYMENTFOLDERS or RESOURCES for loading your Main.qml file?

    Thanks,

    Alex

    #23556

    Peter

    It seems it was an signing issue regarding developer/deployment. It is hard for newbes to figure out the correct signings. Your cloud build service works so far for me for android. For the iOS builds I am using a Macbook now. Because of 2-factor auth I have to use a mac anyway to upload the app to appstore. Would be very charming if 2-factor auth could be handled in the future. This would mean you won’t have to have a mac.

Viewing 5 posts - 1 through 5 (of 5 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded