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. IOS 12 Crash on launch, exactly after splash screen
Forum Updated to NodeBB v4.3 + New Features

IOS 12 Crash on launch, exactly after splash screen

Scheduled Pinned Locked Moved Solved Mobile and Embedded
21 Posts 5 Posters 5.1k Views 6 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.
  • M Offline
    M Offline
    maitai_vw
    wrote on last edited by
    #11

    I have I think the same problem (Widget based application crashing for some users after upgrading to iOS 12)
    From the bug reports it is not clear to me if there is a workaround?

    D 1 Reply Last reply
    0
    • M maitai_vw

      I have I think the same problem (Widget based application crashing for some users after upgrading to iOS 12)
      From the bug reports it is not clear to me if there is a workaround?

      D Offline
      D Offline
      Dimitar.Negrevski
      wrote on last edited by
      #12

      @maitai_vw For our QML application, adding a title to our QML Window fix the crash.

      M 1 Reply Last reply
      0
      • D Dimitar.Negrevski

        @maitai_vw For our QML application, adding a title to our QML Window fix the crash.

        M Offline
        M Offline
        maitai_vw
        wrote on last edited by
        #13

        @Dimitar.Negrevski Thanks for your reply
        My app is widget based. Adding a title to mainwindow passed the crash, but that is not enough. Uses cannot access any menu anymore (i.e. when taping on an action it crashes). Investigation is underway but difficult since I do not have an iOS device compatible with iOS 12.

        ekkescornerE D 2 Replies Last reply
        0
        • M maitai_vw

          @Dimitar.Negrevski Thanks for your reply
          My app is widget based. Adding a title to mainwindow passed the crash, but that is not enough. Uses cannot access any menu anymore (i.e. when taping on an action it crashes). Investigation is underway but difficult since I do not have an iOS device compatible with iOS 12.

          ekkescornerE Offline
          ekkescornerE Offline
          ekkescorner
          Qt Champions 2016
          wrote on last edited by
          #14

          @maitai_vw said in IOS 12 Crash on launch, exactly after splash screen:

          ... I do not have an iOS device compatible with iOS 12.

          have you tried with Simulator ?

          ekke ... Qt Champion 2016 | 2024 ... mobile business apps
          5.15 --> 6.9 https://t1p.de/ekkeChecklist
          QMake --> CMake https://t1p.de/ekkeCMakeMobileApps

          1 Reply Last reply
          0
          • M maitai_vw

            @Dimitar.Negrevski Thanks for your reply
            My app is widget based. Adding a title to mainwindow passed the crash, but that is not enough. Uses cannot access any menu anymore (i.e. when taping on an action it crashes). Investigation is underway but difficult since I do not have an iOS device compatible with iOS 12.

            D Offline
            D Offline
            Dimitar.Negrevski
            wrote on last edited by
            #15

            @maitai_vw Are you sure that menu crash is related to IOS 12, cause with our QML App, we don't have any problems with Menu.

            1 Reply Last reply
            0
            • M Offline
              M Offline
              maitai_vw
              wrote on last edited by
              #16

              Still searching on that one.
              I have 2 users concerned, on iPhone 6S both. Many others do not have the problem
              I do not have a 6S to test with, even worst no device iOS 12 compatible.
              Only thing I can tell is that I get this crash report in XCode from appstore

              UIAccessibility: _axuiElementForNotificationData

              and nothing more.

              Users swear they didn't set any accessibility stuff. Only common point is that they are both located in Swiss, lol.

              M 1 Reply Last reply
              0
              • M maitai_vw

                Still searching on that one.
                I have 2 users concerned, on iPhone 6S both. Many others do not have the problem
                I do not have a 6S to test with, even worst no device iOS 12 compatible.
                Only thing I can tell is that I get this crash report in XCode from appstore

                UIAccessibility: _axuiElementForNotificationData

                and nothing more.

                Users swear they didn't set any accessibility stuff. Only common point is that they are both located in Swiss, lol.

                M Offline
                M Offline
                maitai_vw
                wrote on last edited by
                #17

                Just to add that I have now switch from Qt 11.1.2 to 5.9.7, same pb for these users.

                M 1 Reply Last reply
                0
                • M maitai_vw

                  Just to add that I have now switch from Qt 11.1.2 to 5.9.7, same pb for these users.

                  M Offline
                  M Offline
                  maitai_vw
                  wrote on last edited by
                  #18

                  Finally it appears that users were, well, lying. They did have some accessibility options on, namely "speak screen" and another one. Once they finally removed it's all OK
                  To summarize:
                  I had the crash you reported, and I added a title to mainwindow (my app is widget-based, not qml)
                  That fixed the crash. But still there is a crash later if user is calling a qaction (I guess it's trying to speak the qaction.).
                  Is there a setting in plist or something to override to avoid that?

                  1 Reply Last reply
                  0
                  • M Offline
                    M Offline
                    maitai_vw
                    wrote on last edited by
                    #19

                    And finally the problem disappeared with iOS 12.1, without doing anything else. Even the trick with the title is not necessary anymore.

                    1 Reply Last reply
                    2
                    • D Offline
                      D Offline
                      Dimitar.Negrevski
                      wrote on last edited by
                      #20

                      Yep, it seems that with IOS 12.1 everything is fine, without any workaround. How can I mark issue as resolved?

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

                        Thanks for the confirmation !

                        You can use the "Topic Tools" button for that :)

                        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