Blockbuster bug with Unity and iPhone XR (specifically)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
more info! this seems to be a real, fresh, unity bug
less than 12.1.2 … seems to work on all devices
12.1.2 .. exhibits problem on an XR
12.1.2 .. perfect on an 8Plus, X and others tested so far
Note - the identical behavior happens with recent Unity (all 2018.2) and the brand new Unity 2018.3
Filed with Unity - 1114664
Simply get the latest Unity so 2018.3 or 2018.2
Make a new blank project for iOS.
Make the scene empty - just a cube or such.
Build through to the latest Xcode (so, Version 10.1 (10B61)),
Plug in an ordinary XR and Run ...
It does seem to run, but these odd errors appear.
(I don't actually know if they are errors or warnings, or ??)
Main Thread Checker: UI API called on a background thread:
-[UIApplication applicationState]
PID: 2496, TID: 691898, Thread name:
com.apple.CoreMotion.MotionThread,
Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021839f894 <redacted> + 56
5 CoreMotion 0x000000021ec25040 CoreMotion + 307264
6 CoreMotion 0x000000021ec25574 CoreMotion + 308596
It seems almost unbelievable Unity could make such a basic mistake, and anyway, there would be 10,000 discussions about it online already
I have tried on various phones, Macs etc etc .. what could it be??
It seems to be just a warning rather than a crash, but IDK. It's weird.
It's hard to see what CoreMotion has to do with anything (I clicked "off" the accelerometer from the Unity build, anyway).
What could be causing this error/warning on a iOS build?
ios unity3d core-motion iphone-xr
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
add a comment |
more info! this seems to be a real, fresh, unity bug
less than 12.1.2 … seems to work on all devices
12.1.2 .. exhibits problem on an XR
12.1.2 .. perfect on an 8Plus, X and others tested so far
Note - the identical behavior happens with recent Unity (all 2018.2) and the brand new Unity 2018.3
Filed with Unity - 1114664
Simply get the latest Unity so 2018.3 or 2018.2
Make a new blank project for iOS.
Make the scene empty - just a cube or such.
Build through to the latest Xcode (so, Version 10.1 (10B61)),
Plug in an ordinary XR and Run ...
It does seem to run, but these odd errors appear.
(I don't actually know if they are errors or warnings, or ??)
Main Thread Checker: UI API called on a background thread:
-[UIApplication applicationState]
PID: 2496, TID: 691898, Thread name:
com.apple.CoreMotion.MotionThread,
Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021839f894 <redacted> + 56
5 CoreMotion 0x000000021ec25040 CoreMotion + 307264
6 CoreMotion 0x000000021ec25574 CoreMotion + 308596
It seems almost unbelievable Unity could make such a basic mistake, and anyway, there would be 10,000 discussions about it online already
I have tried on various phones, Macs etc etc .. what could it be??
It seems to be just a warning rather than a crash, but IDK. It's weird.
It's hard to see what CoreMotion has to do with anything (I clicked "off" the accelerometer from the Unity build, anyway).
What could be causing this error/warning on a iOS build?
ios unity3d core-motion iphone-xr
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
sure man - i did of course!
– Fattie
Jan 4 at 21:16
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06
add a comment |
more info! this seems to be a real, fresh, unity bug
less than 12.1.2 … seems to work on all devices
12.1.2 .. exhibits problem on an XR
12.1.2 .. perfect on an 8Plus, X and others tested so far
Note - the identical behavior happens with recent Unity (all 2018.2) and the brand new Unity 2018.3
Filed with Unity - 1114664
Simply get the latest Unity so 2018.3 or 2018.2
Make a new blank project for iOS.
Make the scene empty - just a cube or such.
Build through to the latest Xcode (so, Version 10.1 (10B61)),
Plug in an ordinary XR and Run ...
It does seem to run, but these odd errors appear.
(I don't actually know if they are errors or warnings, or ??)
Main Thread Checker: UI API called on a background thread:
-[UIApplication applicationState]
PID: 2496, TID: 691898, Thread name:
com.apple.CoreMotion.MotionThread,
Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021839f894 <redacted> + 56
5 CoreMotion 0x000000021ec25040 CoreMotion + 307264
6 CoreMotion 0x000000021ec25574 CoreMotion + 308596
It seems almost unbelievable Unity could make such a basic mistake, and anyway, there would be 10,000 discussions about it online already
I have tried on various phones, Macs etc etc .. what could it be??
It seems to be just a warning rather than a crash, but IDK. It's weird.
It's hard to see what CoreMotion has to do with anything (I clicked "off" the accelerometer from the Unity build, anyway).
What could be causing this error/warning on a iOS build?
ios unity3d core-motion iphone-xr
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
more info! this seems to be a real, fresh, unity bug
less than 12.1.2 … seems to work on all devices
12.1.2 .. exhibits problem on an XR
12.1.2 .. perfect on an 8Plus, X and others tested so far
Note - the identical behavior happens with recent Unity (all 2018.2) and the brand new Unity 2018.3
Filed with Unity - 1114664
Simply get the latest Unity so 2018.3 or 2018.2
Make a new blank project for iOS.
Make the scene empty - just a cube or such.
Build through to the latest Xcode (so, Version 10.1 (10B61)),
Plug in an ordinary XR and Run ...
It does seem to run, but these odd errors appear.
(I don't actually know if they are errors or warnings, or ??)
Main Thread Checker: UI API called on a background thread:
-[UIApplication applicationState]
PID: 2496, TID: 691898, Thread name:
com.apple.CoreMotion.MotionThread,
Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000021839f894 <redacted> + 56
5 CoreMotion 0x000000021ec25040 CoreMotion + 307264
6 CoreMotion 0x000000021ec25574 CoreMotion + 308596
It seems almost unbelievable Unity could make such a basic mistake, and anyway, there would be 10,000 discussions about it online already
I have tried on various phones, Macs etc etc .. what could it be??
It seems to be just a warning rather than a crash, but IDK. It's weird.
It's hard to see what CoreMotion has to do with anything (I clicked "off" the accelerometer from the Unity build, anyway).
What could be causing this error/warning on a iOS build?
ios unity3d core-motion iphone-xr
ios unity3d core-motion iphone-xr
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
edited Jan 7 at 15:40
Fattie
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
asked Jan 4 at 15:41
FattieFattie
19.8k31209455
19.8k31209455
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
sure man - i did of course!
– Fattie
Jan 4 at 21:16
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06
add a comment |
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
sure man - i did of course!
– Fattie
Jan 4 at 21:16
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
sure man - i did of course!
– Fattie
Jan 4 at 21:16
sure man - i did of course!
– Fattie
Jan 4 at 21:16
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06
add a comment |
1 Answer
1
active
oldest
votes
In fact, (January 2019)
the Unity dudes contacted me and explained that yeah, it's a bug!
So, that's that.
It does seem to be a warning - everything seems to proceed even though it happens.
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54042042%2fblockbuster-bug-with-unity-and-iphone-xr-specifically%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In fact, (January 2019)
the Unity dudes contacted me and explained that yeah, it's a bug!
So, that's that.
It does seem to be a warning - everything seems to proceed even though it happens.
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
add a comment |
In fact, (January 2019)
the Unity dudes contacted me and explained that yeah, it's a bug!
So, that's that.
It does seem to be a warning - everything seems to proceed even though it happens.
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
add a comment |
In fact, (January 2019)
the Unity dudes contacted me and explained that yeah, it's a bug!
So, that's that.
It does seem to be a warning - everything seems to proceed even though it happens.
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
In fact, (January 2019)
the Unity dudes contacted me and explained that yeah, it's a bug!
So, that's that.
It does seem to be a warning - everything seems to proceed even though it happens.
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
answered Jan 7 at 15:40
FattieFattie
19.8k31209455
19.8k31209455
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54042042%2fblockbuster-bug-with-unity-and-iphone-xr-specifically%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should log this as a Unity bug. You can log bugs from the mac app, via Help menu > Report a Bug...
– Rhythmic Fistman
Jan 4 at 21:10
sure man - i did of course!
– Fattie
Jan 4 at 21:16
I've been running into the same bug with ARKit and SceneKit and and iPhone XR. It happens when I try to programmatically instantiate view controllers from a View Controller running an ARKit Session. Then the UI freezes and I have to relaunch. Has anyone else seen this with SceneKit based apps or does a solution exist by now? Here is my call stack: i.stack.imgur.com/KPW4v.png
– Sebastian
Jan 29 at 18:01
fascinating, @Sebastian , thanks. I have not tried the issue with AR myself. :O
– Fattie
Jan 29 at 18:06