IOS 12 Crash on launch, exactly after splash screen
-
@Dimitar.Negrevski https://bugreports.qt.io/browse/QTBUG-70683 seems to be a similar issue
@ekkescorner Yep, it looks similar, it will be interesting if they find another workaround.
-
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?@maitai_vw For our QML application, adding a title to our QML Window fix the crash.
-
@maitai_vw For our QML application, adding a title to our QML Window fix the crash.
@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. -
@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.@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 ?
-
@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.@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.
-
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 appstoreUIAccessibility: _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.
-
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 appstoreUIAccessibility: _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.
-
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? -
Yep, it seems that with IOS 12.1 everything is fine, without any workaround. How can I mark issue as resolved?
-
Thanks for the confirmation !
You can use the "Topic Tools" button for that :)
