[CoreMotion] UI API called on a background thread #298
Comments
|
@bill350 this only occurs on iOS 12 but we are going to release a new version with a fix very soon. |
|
This issue persists in 8.0.16 |
|
@Gazzini we will release the fix tomorrow. |
|
@Gazzini issue fixed on SDK version 8.0.17 Sorry for being later 😬. |
|
This issue persists in 8.0.17 |
|
@martyhoogendam are you sure that you are on 8.0.17 ? |
|
@Kmohamed specifically targeted 8.0.17 in Podfile. iPhone XS on iOS 12.1. Stacktrace below. Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState] |
|
Could you write bt all in lldb when the xcode found mainThread issue ? |
|
@Kmohamed here you go. |
|
Thanks a lot @martyhoogendam I think it's bug in iOS 12.1 on iPhone XS only |
|
Just confirm with me that scenario on your device and I will make a radar for it. |
|
Confirmed. Merely initializing a CMMotionManager in AppDelegate causes this crash. |
|
@martyhoogendam Thanks a lot for your collaboration. I found this radar related to the issue. |
|
@martyhoogendam you can use screenshot invocation instead. |
|
I appreciate you guys being diligent about this & filing a dupe radar. It's unfortunate that the thread-checker warning fires. I'd like to assume it's a false alarm & do something like this: So that I can still have the main-thread checker for development, but leave the shake functionality enabled for prod. In your best judgement, is this a false alarm @Kmohamed ? |
|
@Gazzini Good news. Btw it's fixed on iOS 12.1.1 |
|
I still have the problem on iPhone XS, iOS 12.1.4 ! |
|
@GhaisB I can not see on iOS 12.1.4 but you can try to initialize CMMotionManager |
|
The bug still exist ! I will use screenshot invocation instead, thank you very much ! |
|
Hi there, I'm working on an other project that uses Core Motion, I'm not using Instabug but it seems that we all encounter same issue, I found this topic on Google but also found this radar : https://openradar.appspot.com/45003816 For information, I'm encounter the same warning with my app on an iPhone XS iOS 12.1.4 but not on an iPhone 8 iOS 12.1.4. Edit: Tested on an iPhone X iOS 12.1.4, no warning either. Hope it helps |
|
I am also having the same issue (Xcode 10 + iPhone XS device with iOS 12.2) |
|
I can see that the radar is still open. but I can not reproduce it on iOS 12.2 |
|
Seems to be a hardware-specific issue. At least Xs, Xs Max, and Xr. Note: Simulators are not affected |
|
It's affecting my iPad 5th gen on 12.2 as well. It does seem to be an issue initializing a Core Motion Manager on newer devices, as initializing a CMMotionManager I assume instabug is using CoreMotion for the "Shake to Report" feature. |
|
@dafurman Yes, we are using CoreMotion for "shake to report". |
|
Update : Issue still here for me with iOS 12.2 and Xcode 10.2, on my iPhone XS. Still haven't any troubles on my iPhone 8. I'm ok about the idea of a hardware specific issue starting with X-series (or maybe Xcode ?) |
|
Update: Issue still found on my XR - iOS 12.2 physical device. Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState] On my 6s is working fine. |
|
Yes, it's device based issue 😞 |
|
Getting this with vanilla ARKit/SceneKit. Not using Instabug what so ever. Using physical iPhone Xs iOS 12.2 |
|
I made an Apple Developer Technical support and this was their answer:
unfortunately nothing new. |
|
@Kmohamed so there is an issue but it’s ”ok” for Apple? It's a feature? 😅 |
|
@bill350 Yes it's a threading feature 😆 |
|
@SandrikaJanjghava it's a device related bug from Apple, you can check the rest of the thread for more info. But anyway please make sure you are using the latest Instabug version (8.4.1) as 4.4 is really old. |
|
big thanks to you, I will check
On Thu, Jun 27, 2019 at 7:11 PM Yousef Hamza ***@***.***> wrote:
@SandrikaJanjghava <https://github.com/SandrikaJanjghava> it's a device
related bug from Apple, you can check the rest of the thread for more info.
But anyway please make sure you are using the latest Instabug version
(8.4.1) as 4.4 is really old.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#298?email_source=notifications&email_token=AEJ4RICRHQ3FRA7N7DENBATP4TKCZA5CNFSM4GDHX6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXN3HQ#issuecomment-506387870>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEJ4RIA2TE3KPYCZ23VN2ZDP4TKCZANCNFSM4GDHX6HA>
.
--
[image: logo]
*Sandro Janjghava*
CEO, Co-founder iDevelopers
571 99 26 00 <571992600> | sandro.janjghava@idevelopers.eu |
Innovation St #7
<https://www.google.ge/maps/place/Tech+Park+Georgia/@41.6878006,44.7683255,17z/data=!4m5!3m4!1s0x0:0x62876d14c29bde36!8m2!3d41.6881125!4d44.7693005>
<http://facebook.com/sandruncha>
|
|
it seems they fixed it in iOS 13 beta |
|
Still an issue on iPhone XS |
|
Still occurs on iPhone XS, iOS 12.4 |
|
I think it’s fixed in iOS 13 beta. Can someone else check please? |
I'm from the future :) The bug is still there |
Steps to Reproduce the Problem
1- Configure the SDK
2- launch the app
Expected Behavior
No error / warning on the Xcode console
Actual Behavior
Instabug integration code
SDK Version
8.0.15iOS Version
12.1Device Model
iPhone XS
[Optional] Project That Reproduces the Issue
The text was updated successfully, but these errors were encountered: