iPad Air - CoreBluetooth[ERROR] Cancelling picker as we couldn't communicate with Bluetooth
I'm working with the "ExternalAccessory framework".
I encountered a problem trying my app on a new iPad Air.
When i try to show the bluetooth picker this error appear:
CoreBluetooth[ERROR] Cancelling picker as we couldn't communicate with Bluetooth
The bluetooth is ON.
Picker return this error:
Error Domain=EABluetoothAccessoryPickerErrorDomain Code=3 "The operation couldn’t be
completed.
My app work on every Apple Device, except the new iPad Air.
EDIT
I can connect and communicate with my device. The problem appear only if i call the bluetooth picker.
EDIT 2
the problem appears also with a modified version of EADemo.
I've added this function.
- (void)searchDevice
[[EAAccessoryManager sharedAccessoryManager] showBluetoothAccessoryPickerWithNameFilter:nil completion:nil];
When i call it, BANG! The same error. Only in iPad Air
this problem will occur on all 64-bit devices
ipad core-bluetooth external-accessory
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
|
show 2 more comments
I'm working with the "ExternalAccessory framework".
I encountered a problem trying my app on a new iPad Air.
When i try to show the bluetooth picker this error appear:
CoreBluetooth[ERROR] Cancelling picker as we couldn't communicate with Bluetooth
The bluetooth is ON.
Picker return this error:
Error Domain=EABluetoothAccessoryPickerErrorDomain Code=3 "The operation couldn’t be
completed.
My app work on every Apple Device, except the new iPad Air.
EDIT
I can connect and communicate with my device. The problem appear only if i call the bluetooth picker.
EDIT 2
the problem appears also with a modified version of EADemo.
I've added this function.
- (void)searchDevice
[[EAAccessoryManager sharedAccessoryManager] showBluetoothAccessoryPickerWithNameFilter:nil completion:nil];
When i call it, BANG! The same error. Only in iPad Air
this problem will occur on all 64-bit devices
ipad core-bluetooth external-accessory
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
You got a CoreBluetooth (for Bluetooth Low-Energy) Error withExternalAccessory.framework(for classical Bluetooth) ?
– Larme
Dec 5 '13 at 15:00
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
1
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call-showBluetoothAccessoryPickerWithNameFilter:completion:and it works there. Digging into what's different now.
– Martijn Thé
Jan 13 '14 at 20:30
1
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59
|
show 2 more comments
I'm working with the "ExternalAccessory framework".
I encountered a problem trying my app on a new iPad Air.
When i try to show the bluetooth picker this error appear:
CoreBluetooth[ERROR] Cancelling picker as we couldn't communicate with Bluetooth
The bluetooth is ON.
Picker return this error:
Error Domain=EABluetoothAccessoryPickerErrorDomain Code=3 "The operation couldn’t be
completed.
My app work on every Apple Device, except the new iPad Air.
EDIT
I can connect and communicate with my device. The problem appear only if i call the bluetooth picker.
EDIT 2
the problem appears also with a modified version of EADemo.
I've added this function.
- (void)searchDevice
[[EAAccessoryManager sharedAccessoryManager] showBluetoothAccessoryPickerWithNameFilter:nil completion:nil];
When i call it, BANG! The same error. Only in iPad Air
this problem will occur on all 64-bit devices
ipad core-bluetooth external-accessory
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
I'm working with the "ExternalAccessory framework".
I encountered a problem trying my app on a new iPad Air.
When i try to show the bluetooth picker this error appear:
CoreBluetooth[ERROR] Cancelling picker as we couldn't communicate with Bluetooth
The bluetooth is ON.
Picker return this error:
Error Domain=EABluetoothAccessoryPickerErrorDomain Code=3 "The operation couldn’t be
completed.
My app work on every Apple Device, except the new iPad Air.
EDIT
I can connect and communicate with my device. The problem appear only if i call the bluetooth picker.
EDIT 2
the problem appears also with a modified version of EADemo.
I've added this function.
- (void)searchDevice
[[EAAccessoryManager sharedAccessoryManager] showBluetoothAccessoryPickerWithNameFilter:nil completion:nil];
When i call it, BANG! The same error. Only in iPad Air
this problem will occur on all 64-bit devices
ipad core-bluetooth external-accessory
ipad core-bluetooth external-accessory
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
edited Aug 25 '14 at 9:32
Tommaso Resti
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
asked Dec 5 '13 at 14:45
Tommaso RestiTommaso Resti
4,11321028
4,11321028
You got a CoreBluetooth (for Bluetooth Low-Energy) Error withExternalAccessory.framework(for classical Bluetooth) ?
– Larme
Dec 5 '13 at 15:00
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
1
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call-showBluetoothAccessoryPickerWithNameFilter:completion:and it works there. Digging into what's different now.
– Martijn Thé
Jan 13 '14 at 20:30
1
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59
|
show 2 more comments
You got a CoreBluetooth (for Bluetooth Low-Energy) Error withExternalAccessory.framework(for classical Bluetooth) ?
– Larme
Dec 5 '13 at 15:00
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
1
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call-showBluetoothAccessoryPickerWithNameFilter:completion:and it works there. Digging into what's different now.
– Martijn Thé
Jan 13 '14 at 20:30
1
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59
You got a CoreBluetooth (for Bluetooth Low-Energy) Error with
ExternalAccessory.framework (for classical Bluetooth) ?– Larme
Dec 5 '13 at 15:00
You got a CoreBluetooth (for Bluetooth Low-Energy) Error with
ExternalAccessory.framework (for classical Bluetooth) ?– Larme
Dec 5 '13 at 15:00
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
1
1
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call
-showBluetoothAccessoryPickerWithNameFilter:completion: and it works there. Digging into what's different now.– Martijn Thé
Jan 13 '14 at 20:30
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call
-showBluetoothAccessoryPickerWithNameFilter:completion: and it works there. Digging into what's different now.– Martijn Thé
Jan 13 '14 at 20:30
1
1
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59
|
show 2 more comments
2 Answers
2
active
oldest
votes
Your app needs to include a 64-bit slice (add arm64 to the ARCHS build setting), otherwise this problem will occur on 64-bit devices like iPhone 5S, iPad Air... This is a bug in iOS 7.0 - 7.0.3. It is supposed to be fixed in the next release.
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
add a comment |
Adding both:
#import <CoreBluetooth/CoreBluetooth.h>
#import <ExternalAccessory/ExternalAccessory.h>
To either the header of implementation fixed this for me.
Very strange because the frameworks are already linked at app launch?..
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
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%2f20402973%2fipad-air-corebluetootherror-cancelling-picker-as-we-couldnt-communicate-wit%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your app needs to include a 64-bit slice (add arm64 to the ARCHS build setting), otherwise this problem will occur on 64-bit devices like iPhone 5S, iPad Air... This is a bug in iOS 7.0 - 7.0.3. It is supposed to be fixed in the next release.
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
add a comment |
Your app needs to include a 64-bit slice (add arm64 to the ARCHS build setting), otherwise this problem will occur on 64-bit devices like iPhone 5S, iPad Air... This is a bug in iOS 7.0 - 7.0.3. It is supposed to be fixed in the next release.
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
add a comment |
Your app needs to include a 64-bit slice (add arm64 to the ARCHS build setting), otherwise this problem will occur on 64-bit devices like iPhone 5S, iPad Air... This is a bug in iOS 7.0 - 7.0.3. It is supposed to be fixed in the next release.
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
Your app needs to include a 64-bit slice (add arm64 to the ARCHS build setting), otherwise this problem will occur on 64-bit devices like iPhone 5S, iPad Air... This is a bug in iOS 7.0 - 7.0.3. It is supposed to be fixed in the next release.
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
answered Jan 14 '14 at 4:10
Martijn ThéMartijn Thé
2,81432237
2,81432237
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
add a comment |
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
YESSSSS! ;) you saved me <3
– Tommaso Resti
Jan 23 '14 at 15:19
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
i would like to give you 1000 score... ahahah i'll send to you a beer!
– Tommaso Resti
Jan 23 '14 at 15:26
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
Adding arm64 worked for me...and I am building for iOS 7.1, so does not appear to have been fixed all these months (and a couple of releases) later.
– Reid
Mar 17 '14 at 23:34
1
1
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
FYI not fixed in 8.0b2.
– Daniel T.
Jun 18 '14 at 19:12
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
I've gotten confirmation from Apple that they do not consider this a bug and it will NOT be fixed in iOS 8 GM. I strongly disagree with the assessment that it is not a bug, but it looks like if you want to use the in-app bluetooth picker you must build for both 32-bit and 64-bit.
– aggieNick02
Aug 29 '14 at 14:24
add a comment |
Adding both:
#import <CoreBluetooth/CoreBluetooth.h>
#import <ExternalAccessory/ExternalAccessory.h>
To either the header of implementation fixed this for me.
Very strange because the frameworks are already linked at app launch?..
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
add a comment |
Adding both:
#import <CoreBluetooth/CoreBluetooth.h>
#import <ExternalAccessory/ExternalAccessory.h>
To either the header of implementation fixed this for me.
Very strange because the frameworks are already linked at app launch?..
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
add a comment |
Adding both:
#import <CoreBluetooth/CoreBluetooth.h>
#import <ExternalAccessory/ExternalAccessory.h>
To either the header of implementation fixed this for me.
Very strange because the frameworks are already linked at app launch?..
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
Adding both:
#import <CoreBluetooth/CoreBluetooth.h>
#import <ExternalAccessory/ExternalAccessory.h>
To either the header of implementation fixed this for me.
Very strange because the frameworks are already linked at app launch?..
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
answered Nov 13 '18 at 11:51
iOSDeciOSDec
1302418
1302418
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%2f20402973%2fipad-air-corebluetootherror-cancelling-picker-as-we-couldnt-communicate-wit%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 got a CoreBluetooth (for Bluetooth Low-Energy) Error with
ExternalAccessory.framework(for classical Bluetooth) ?– Larme
Dec 5 '13 at 15:00
Quite interesting...
– Julian F. Weinert
Dec 5 '13 at 15:06
Yes. It's very strange.
– Tommaso Resti
Dec 5 '13 at 15:20
1
Seeing this too in our app (Pebble) on iPhone 5S. I made a quick test app that does nothing but call
-showBluetoothAccessoryPickerWithNameFilter:completion:and it works there. Digging into what's different now.– Martijn Thé
Jan 13 '14 at 20:30
1
I tried removed CoreBluetooth and all its uses from our app. Did solve it. I tried removing the EA protocol identifiers from the info.plist. Did not help. Removed the Bluetooth and EAAcessory related background modes from the info.plist. No cigar. Ended up filing a bug too and requested Dev Tech Support.
– Martijn Thé
Jan 13 '14 at 22:59