Instruments > device grayed out
I'm running an app on my iOS device but, in Instruments, that device is greyed out.
This also means I can't attach the process (Cant launch iOS app with Instruments on device). Is it anything to do with my earlier question: Instruments > Profile - Revoke and request
Xcode: 6.1.1
iOS: 7.1.2
Any idea why?
ios instruments
add a comment |
I'm running an app on my iOS device but, in Instruments, that device is greyed out.
This also means I can't attach the process (Cant launch iOS app with Instruments on device). Is it anything to do with my earlier question: Instruments > Profile - Revoke and request
Xcode: 6.1.1
iOS: 7.1.2
Any idea why?
ios instruments
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44
add a comment |
I'm running an app on my iOS device but, in Instruments, that device is greyed out.
This also means I can't attach the process (Cant launch iOS app with Instruments on device). Is it anything to do with my earlier question: Instruments > Profile - Revoke and request
Xcode: 6.1.1
iOS: 7.1.2
Any idea why?
ios instruments
I'm running an app on my iOS device but, in Instruments, that device is greyed out.
This also means I can't attach the process (Cant launch iOS app with Instruments on device). Is it anything to do with my earlier question: Instruments > Profile - Revoke and request
Xcode: 6.1.1
iOS: 7.1.2
Any idea why?
ios instruments
ios instruments
edited May 23 '17 at 12:01
Community♦
11
11
asked Mar 7 '15 at 10:18
SnowcrashSnowcrash
38.6k41135229
38.6k41135229
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44
add a comment |
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44
add a comment |
7 Answers
7
active
oldest
votes
I only had to reboot my phone (not my Mac), and then the error went away
(Xcode 9.2, iPhone X running 11.2.6).
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
add a comment |
i was having this issue and resolved it by
- Unplugging my device
- Turning my device off
- Rebooted my mac
- Turned device back on and plugged into computer after logging back in.
now it shows up in instruments. I tried unplugging device, restarting xcode, but that didn't work. rebooting everything is what did the trick for me.
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
add a comment |
I met the this problem. Xcode(Version 9.3.1 (9E501)), iphone 7, And I forcely quit the Instrument. It's work
add a comment |
I came across same problem today on xcode7.2.1, iOS 9.2.1, iPhone 6Sp. Resolved by rebooted my mac, my watch and the iPhone.
add a comment |
I don't know which process helped but I force quit AppleMobileDeviceHelper
and DTServiceHub
in the Activity Monitor and then it started working again (I was able to select my phone without rebooting).
add a comment |
If your workspace contains several projects and/or several targets, it seems that XCode doesn't know which binary to profile.
Just Edit your scheme -> Profile -> Choose an Executable
and it should enable the profiling option.
add a comment |
Recently, I confronted the question again on Xcode Version 10.1 (10B61), iphone 7 and Mac 10.14.1 (18B75). I resolved it by upgrading the deployment from 8.0 to 10.1. In fact, I have meet many strange Xcode bugs caused by the version, liking this one(xcode gpu shader profiler)
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%2f28913801%2finstruments-device-grayed-out%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
I only had to reboot my phone (not my Mac), and then the error went away
(Xcode 9.2, iPhone X running 11.2.6).
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
add a comment |
I only had to reboot my phone (not my Mac), and then the error went away
(Xcode 9.2, iPhone X running 11.2.6).
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
add a comment |
I only had to reboot my phone (not my Mac), and then the error went away
(Xcode 9.2, iPhone X running 11.2.6).
I only had to reboot my phone (not my Mac), and then the error went away
(Xcode 9.2, iPhone X running 11.2.6).
answered Mar 21 '18 at 23:51
MaxMax
6131818
6131818
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
add a comment |
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
2
2
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
Saved me a Mac reboot :)
– AnthoPak
May 9 '18 at 9:40
2
2
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
Rebooted Mac: did not help. Rebooted device: iPad shows up again in Instruments.
– Bram
May 22 '18 at 20:29
add a comment |
i was having this issue and resolved it by
- Unplugging my device
- Turning my device off
- Rebooted my mac
- Turned device back on and plugged into computer after logging back in.
now it shows up in instruments. I tried unplugging device, restarting xcode, but that didn't work. rebooting everything is what did the trick for me.
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
add a comment |
i was having this issue and resolved it by
- Unplugging my device
- Turning my device off
- Rebooted my mac
- Turned device back on and plugged into computer after logging back in.
now it shows up in instruments. I tried unplugging device, restarting xcode, but that didn't work. rebooting everything is what did the trick for me.
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
add a comment |
i was having this issue and resolved it by
- Unplugging my device
- Turning my device off
- Rebooted my mac
- Turned device back on and plugged into computer after logging back in.
now it shows up in instruments. I tried unplugging device, restarting xcode, but that didn't work. rebooting everything is what did the trick for me.
i was having this issue and resolved it by
- Unplugging my device
- Turning my device off
- Rebooted my mac
- Turned device back on and plugged into computer after logging back in.
now it shows up in instruments. I tried unplugging device, restarting xcode, but that didn't work. rebooting everything is what did the trick for me.
answered Mar 6 '16 at 21:00
odythodyth
3,46833044
3,46833044
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
add a comment |
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
12
12
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
We're definitely back in windows 98 territory on the mac nowadays. Can't believe how poor the quality of developer they're employing now is!
– amergin
Jan 14 '17 at 11:43
5
5
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
As Max noted in this answer, rebooting the Mac shouldn't be necessary (just reboot the iPhone) :)
– AnthoPak
May 9 '18 at 9:40
add a comment |
I met the this problem. Xcode(Version 9.3.1 (9E501)), iphone 7, And I forcely quit the Instrument. It's work
add a comment |
I met the this problem. Xcode(Version 9.3.1 (9E501)), iphone 7, And I forcely quit the Instrument. It's work
add a comment |
I met the this problem. Xcode(Version 9.3.1 (9E501)), iphone 7, And I forcely quit the Instrument. It's work
I met the this problem. Xcode(Version 9.3.1 (9E501)), iphone 7, And I forcely quit the Instrument. It's work
edited Jul 11 '18 at 6:19
answered Jun 5 '18 at 5:56
冯剑龙冯剑龙
167414
167414
add a comment |
add a comment |
I came across same problem today on xcode7.2.1, iOS 9.2.1, iPhone 6Sp. Resolved by rebooted my mac, my watch and the iPhone.
add a comment |
I came across same problem today on xcode7.2.1, iOS 9.2.1, iPhone 6Sp. Resolved by rebooted my mac, my watch and the iPhone.
add a comment |
I came across same problem today on xcode7.2.1, iOS 9.2.1, iPhone 6Sp. Resolved by rebooted my mac, my watch and the iPhone.
I came across same problem today on xcode7.2.1, iOS 9.2.1, iPhone 6Sp. Resolved by rebooted my mac, my watch and the iPhone.
answered Mar 9 '16 at 8:25
wupherwupher
3316
3316
add a comment |
add a comment |
I don't know which process helped but I force quit AppleMobileDeviceHelper
and DTServiceHub
in the Activity Monitor and then it started working again (I was able to select my phone without rebooting).
add a comment |
I don't know which process helped but I force quit AppleMobileDeviceHelper
and DTServiceHub
in the Activity Monitor and then it started working again (I was able to select my phone without rebooting).
add a comment |
I don't know which process helped but I force quit AppleMobileDeviceHelper
and DTServiceHub
in the Activity Monitor and then it started working again (I was able to select my phone without rebooting).
I don't know which process helped but I force quit AppleMobileDeviceHelper
and DTServiceHub
in the Activity Monitor and then it started working again (I was able to select my phone without rebooting).
answered Feb 8 '18 at 18:51
Felix LapalmeFelix Lapalme
8881024
8881024
add a comment |
add a comment |
If your workspace contains several projects and/or several targets, it seems that XCode doesn't know which binary to profile.
Just Edit your scheme -> Profile -> Choose an Executable
and it should enable the profiling option.
add a comment |
If your workspace contains several projects and/or several targets, it seems that XCode doesn't know which binary to profile.
Just Edit your scheme -> Profile -> Choose an Executable
and it should enable the profiling option.
add a comment |
If your workspace contains several projects and/or several targets, it seems that XCode doesn't know which binary to profile.
Just Edit your scheme -> Profile -> Choose an Executable
and it should enable the profiling option.
If your workspace contains several projects and/or several targets, it seems that XCode doesn't know which binary to profile.
Just Edit your scheme -> Profile -> Choose an Executable
and it should enable the profiling option.
edited Feb 27 '18 at 11:05
Stephen Kennedy
7,477135169
7,477135169
answered Feb 27 '18 at 10:42
Anthony NevoAnthony Nevo
11
11
add a comment |
add a comment |
Recently, I confronted the question again on Xcode Version 10.1 (10B61), iphone 7 and Mac 10.14.1 (18B75). I resolved it by upgrading the deployment from 8.0 to 10.1. In fact, I have meet many strange Xcode bugs caused by the version, liking this one(xcode gpu shader profiler)
add a comment |
Recently, I confronted the question again on Xcode Version 10.1 (10B61), iphone 7 and Mac 10.14.1 (18B75). I resolved it by upgrading the deployment from 8.0 to 10.1. In fact, I have meet many strange Xcode bugs caused by the version, liking this one(xcode gpu shader profiler)
add a comment |
Recently, I confronted the question again on Xcode Version 10.1 (10B61), iphone 7 and Mac 10.14.1 (18B75). I resolved it by upgrading the deployment from 8.0 to 10.1. In fact, I have meet many strange Xcode bugs caused by the version, liking this one(xcode gpu shader profiler)
Recently, I confronted the question again on Xcode Version 10.1 (10B61), iphone 7 and Mac 10.14.1 (18B75). I resolved it by upgrading the deployment from 8.0 to 10.1. In fact, I have meet many strange Xcode bugs caused by the version, liking this one(xcode gpu shader profiler)
answered Nov 21 '18 at 12:00
冯剑龙冯剑龙
167414
167414
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%2f28913801%2finstruments-device-grayed-out%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
Is your device is configured for development (look at it inside Xcode organizer, devices)?
– Rashwan L
Dec 31 '15 at 6:34
Make sure you configure the device for development. Then ensure that the Xcode project settings for the deployment target match your device's OS. Also, ensure that the 'device' option matches the device you are trying to build to.
– Tom Metzger
Jan 20 '16 at 18:58
I have the same issue, the device is definitely configured because I've profiled my app before on that device. Have you fixed the issue?
– Stas
Jan 27 '16 at 16:44