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

Forums

OverviewFelgo 3 Support (Qt 5) › macOS and iOS are just empty after 2.13.2 to 2.14 upgrade

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #17530

    Julian

    Hi,

    I just updated from 2.13.2 to 2.14 and now all my builds give out an empty App. One can see the top Bar (without) any text and the bottom navigation bar, but all content is missing. I migrated to the new build mechanisms too:

    build-BerlinVegan-V_Play_Desktop_Qt_5_9_2_clang-Release/
    build-BerlinVegan-Qt_5_9_2_iOS_V_Play-Release/

     

    Did I miss something in the docs? Did I forget something?

    #17534

    Günther
    Felgo Team

    Hi Julian,

    can you try whether the Felgo Examples work, for example the Component Showcase?

    If the issue also happens for the example or even with a fresh Felgo Project created in Qt Creator,
    please remove Felgo with the MaintenanceTool and re-install with our latest installers.

    Does the issue only happen for your project or in general?

    Best,
    Günther

    #17536

    Julian

    Günther: I will do that. Thanks.

    Just for reference. Logs at start:

    2017-11-26 13:17:16.034101+0100 harbour-berlin-vegan[14911:5484771] [DYMTLInitPlatform] platform initialization successful
    2017-11-26 13:17:16.225097+0100 harbour-berlin-vegan[14911:5484647] Metal GPU Frame Capture Enabled
    2017-11-26 13:17:16.225752+0100 harbour-berlin-vegan[14911:5484647] Metal API Validation Enabled
    Translations loaded
    JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform.
    System: loading config file from: ":/qml/config.json"
    NOTE: you are running a development build in Release Mode. However, the Release mode is recommended only for publish builds that are released to the app stores and for final testing. You can enable a publish build in the config.json file in your qml folder by setting the "stage" property to "publish". For more information see: https://felgo.com/doc/vplay-publishing/
    WARNING: VPlayFileUtils: Did not find the file or directory: "qml/translations"
    setting extrafileSelectorList to ("hd", "sd") , allFileSelectors: ("hd", "sd", "en_DE", "unix", "darwin", "mac", "ios")
    setting internalContentScaleFactorForImages which is used for MultiResolutionImage contextProperty to 0.5
    VPlayApplication: setting screenDpi contextProperty to 326
    VPlayApplication: setting devicePixelRatio contextProperty to 2
    VPlayApplication: setMainQmlFileName called for qmlFileName "qrc:/qml/harbour-berlin-vegan.qml" , used file: "qrc:/qml/harbour-berlin-vegan.qml"
    JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform.
    stale focus object QObject(0x0) , doing manual update
    qml: no licenseKey set, generate one here to remove the Felgo Splash screen and to use plugins for monetization, analytics, push notifications, social networks & more: http://felgo.com/licenseKey
    qml: Loaded font: 'Material Icons'
    2017-11-26 13:17:16.880137+0100 harbour-berlin-vegan[14911:5484647] refreshPreferences: HangTracerEnabled: 0
    2017-11-26 13:17:16.880179+0100 harbour-berlin-vegan[14911:5484647] refreshPreferences: HangTracerDuration: 500
    2017-11-26 13:17:16.880194+0100 harbour-berlin-vegan[14911:5484647] refreshPreferences: ActivationLoggingEnabled: 0 ActivationLoggingTaskedOffByDA:0
    =================================================================
    Main Thread Checker: UI API called on a background thread: -[UIView layer]
    PID: 14911, TID: 5484804, Thread name: QSGRenderThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 21
    Backtrace:
    4   harbour-berlin-vegan                0x00000001051fc550 _ZN11QIOSContext11makeCurrentEP16QPlatformSurface + 416
    5   harbour-berlin-vegan                0x0000000105b0db18 _ZN14QOpenGLContext11makeCurrentEP8QSurface + 192
    6   harbour-berlin-vegan                0x000000010595c34c _ZN15QSGRenderThread3runEv + 492
    7   harbour-berlin-vegan                0x000000010604ce78 _ZN14QThreadPrivate5startEPv + 372
    8   libsystem_pthread.dylib             0x0000000182c0c31c <redacted> + 308
    9   libsystem_pthread.dylib             0x0000000182c0c1e8 <redacted> + 0
    10  libsystem_pthread.dylib             0x0000000182c0ac28 thread_start + 4
    2017-11-26 13:17:16.920423+0100 harbour-berlin-vegan[14911:5484804] [reports] Main Thread Checker: UI API called on a background thread: -[UIView layer]
    PID: 14911, TID: 5484804, Thread name: QSGRenderThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 21
    Backtrace:
    4   harbour-berlin-vegan                0x00000001051fc550 _ZN11QIOSContext11makeCurrentEP16QPlatformSurface + 416
    5   harbour-berlin-vegan                0x0000000105b0db18 _ZN14QOpenGLContext11makeCurrentEP8QSurface + 192
    6   harbour-berlin-vegan                0x000000010595c34c _ZN15QSGRenderThread3runEv + 492
    7   harbour-berlin-vegan                0x000000010604ce78 _ZN14QThreadPrivate5startEPv + 372
    8   libsystem_pthread.dylib             0x0000000182c0c31c <redacted> + 308
    9   libsystem_pthread.dylib             0x0000000182c0c1e8 <redacted> + 0
    10  libsystem_pthread.dylib             0x0000000182c0ac28 thread_start + 4
    =================================================================
    Main Thread Checker: UI API called on a background thread: -[UIView contentScaleFactor]
    PID: 14911, TID: 5484804, Thread name: QSGRenderThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 21
    Backtrace:
    4   harbour-berlin-vegan                0x0000000105ae6f18 _ZNK7QWindow16devicePixelRatioEv + 44
    5   harbour-berlin-vegan                0x0000000105a7d880 _ZN24QQuickShaderEffectSource15updatePaintNodeEP7QSGNodePN10QQuickItem19UpdatePaintNodeDataE + 408
    6   harbour-berlin-vegan                0x00000001059aa8e8 _ZN19QQuickWindowPrivate15updateDirtyNodeEP10QQuickItem + 2472
    7   harbour-berlin-vegan                0x000000010599e5bc _ZN19QQuickWindowPrivate16updateDirtyNodesEv + 1192
    8   harbour-berlin-vegan                0x000000010599debc _ZN19QQuickWindowPrivate14syncSceneGraphEv + 240
    9   harbour-berlin-vegan                0x000000010595ac0c _ZN15QSGRenderThread4syncEb + 856
    10  harbour-berlin-vegan                0x000000010595b22c _ZN15QSGRenderThread13syncAndRenderEv + 852
    11  harbour-berlin-vegan                0x000000010595c368 _ZN15QSGRenderThread3runEv + 520
    12  harbour-berlin-vegan                0x000000010604ce78 _ZN14QThreadPrivate5startEPv + 372
    13  libsystem_pthread.dylib             0x0000000182c0c31c <redacted> + 308
    14  libsystem_pthread.dylib             0x0000000182c0c1e8 <redacted> + 0
    15  libsystem_pthread.dylib             0x0000000182c0ac28 thread_start + 4
    2017-11-26 13:17:17.077681+0100 harbour-berlin-vegan[14911:5484804] [reports] Main Thread Checker: UI API called on a background thread: -[UIView contentScaleFactor]
    PID: 14911, TID: 5484804, Thread name: QSGRenderThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 21
    Backtrace:
    4   harbour-berlin-vegan                0x0000000105ae6f18 _ZNK7QWindow16devicePixelRatioEv + 44
    5   harbour-berlin-vegan                0x0000000105a7d880 _ZN24QQuickShaderEffectSource15updatePaintNodeEP7QSGNodePN10QQuickItem19UpdatePaintNodeDataE + 408
    6   harbour-berlin-vegan                0x00000001059aa8e8 _ZN19QQuickWindowPrivate15updateDirtyNodeEP10QQuickItem + 2472
    7   harbour-berlin-vegan                0x000000010599e5bc _ZN19QQuickWindowPrivate16updateDirtyNodesEv + 1192
    8   harbour-berlin-vegan                0x000000010599debc _ZN19QQuickWindowPrivate14syncSceneGraphEv + 240
    9   harbour-berlin-vegan                0x000000010595ac0c _ZN15QSGRenderThread4syncEb + 856
    10  harbour-berlin-vegan                0x000000010595b22c _ZN15QSGRenderThread13syncAndRenderEv + 852
    11  harbour-berlin-vegan                0x000000010595c368 _ZN15QSGRenderThread3runEv + 520
    12  harbour-berlin-vegan                0x000000010604ce78 _ZN14QThreadPrivate5startEPv + 372
    13  libsystem_pthread.dylib             0x0000000182c0c31c <redacted> + 308
    14  libsystem_pthread.dylib             0x0000000182c0c1e8 <redacted> + 0
    15  libsystem_pthread.dylib             0x0000000182c0ac28 thread_start + 4

     

    #17539

    Julian

    Günther: Thanks for responding. It seems to be our app.

    #17543

    Günther
    Felgo Team

     

    Hi,

    if only your project is affected, the issue is maybe related to changes in the Navigation type that were part of the update, please see this topic:
    https://felgo.com/developers/forums/t/error-after-the-update-to-2-4

    Does your app e.g. use a customized Navigation per platform and are you able to resolve the issues with e.g. the snippet in the above post?

    Best,
    Günther

    #17590

    Micu

    Hey Günther et al.,

    The thing is: We do have our own menu abstraction (http://www.micuintus.de/2017/10/01/cross-platform-mobile-app-development-for-ios-sailfishos-and-android-with-qtqml/), which I tried to fix. Currently, we create our pages

    onLoaded()

    of of the NavigationItem: https://github.com/micuintus/harbour-Berlin-Vegan/blob/development/qml/components-v-play/MenuItem.qml#L21

    But we don`t receive that signal any longer with the new Felgo version. I did find a solution for the pages to show up again, but also do we no longer receive

    the

    selected()

    signal. Did you change anything there?

    #17606

    Günther
    Felgo Team

    Hi Micu,
    thanks for your message.

    We’ve found a bug with forwarding these signals in the new Navigation setup. We’ll work to fix this as soon as possible. There will probably be a minor update next week as well, we’d like to include the fix there if possible!

    Best,
    Günther

    #17608

    Francois

    Hello,

    we have the same issue here.

    Our navigation system is completely broken.

    Any suggestion for a workaround ? Or, better, is it possible to get sooner the fix ?

     

    Many thanks for your help.

    Best Regards.

    F.

     

Viewing 8 posts - 1 through 8 (of 8 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