Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. QOpenGLWidget not working on iOS 18 (e.g. hellogl2 example)

QOpenGLWidget not working on iOS 18 (e.g. hellogl2 example)

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
iosopengl es
5 Posts 2 Posters 1.4k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    NatWalker
    wrote on last edited by
    #1

    I'm currently porting an application from 5.15 to 6.9.1 and I am having problems running the app on iOS 18.5 . The app previously used QGLWidget which I've replaced with QOpenGLWidget. The app however just shows a black screen. I then tried the OpenGL Examples in 6.9.1 and the example hellogl2, which also uses QOpenGLWidget, has the same problem. Is this a known issue and does anyone have an example of code working on iOS 18 using QOpenGLWidget? Note, the example hellogles3 does work but uses QOpenGLWindow and not widgets.

    The errors I see both in our app and the hellogl2 example on startup are as follows:

    OpenGL ES calls are not allowed while an application is backgrounded
    QRhiGles2: Failed to make context current. Expect bad things to happen.
    Failed to create QRhi for QBackingStoreRhiSupport

    I am using the 6.9.1 toolchain file 6.9.1/ios/lib/cmake/Qt6/qt.toolchain.cmake

    Many thanks.

    1 Reply Last reply
    0
    • N Offline
      N Offline
      NatWalker
      wrote on last edited by
      #2

      The problem is not specific to iOS 18: it also happens on iOS 17.7.8

      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by
        #3

        Hi and welcome to devnet,

        I think you should directly check the bug report system.

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        N 1 Reply Last reply
        1
        • SGaistS SGaist

          Hi and welcome to devnet,

          I think you should directly check the bug report system.

          N Offline
          N Offline
          NatWalker
          wrote on last edited by
          #4

          @SGaist Many thanks for your suggestion. I've raised a bug for the issue: 138913. I posted here first as I wasn't sure if this was not supported and to check whether anyone knew of a work around.

          1 Reply Last reply
          2
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            Sure thing ! No problem with asking first here :-)
            Thanks for the link !

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved