GitHub / pebble/pebble-ios-sdk issues and pull requests
#30 - Whitelist
Issue -
State: open - Opened by oluwaseyi200-boss almost 3 years ago
#29 - Doesn't build for Simulator on Apple Silicon
Issue -
State: open - Opened by futuretap over 4 years ago
#28 - lastConnectedWatch in iOS 10.3
Issue -
State: closed - Opened by arlomedia about 8 years ago
- 1 comment
#27 - Update FirmwareMetadataPlatform for Diorite and Emery
Issue -
State: closed - Opened by maxbaeumle over 8 years ago
- 1 comment
#26 - How to check if user has accepted Bluetooth permission?
Issue -
State: open - Opened by edwinfinch over 8 years ago
- 5 comments
#25 - com.apple.private.externalaccessory.showallaccessories
Issue -
State: closed - Opened by szysz3 almost 9 years ago
- 7 comments
#24 - PebbleKit dynamic framework breaks with bitcode enabled
Issue -
State: closed - Opened by corvino almost 9 years ago
- 2 comments
#23 - Manual instructions in readme are incorrect
Issue -
State: closed - Opened by corvino almost 9 years ago
- 1 comment
#22 - CocoaPods create project only have dataLoggingService api
Issue -
State: closed - Opened by zszen about 9 years ago
- 1 comment
#21 - Update README.md
Pull Request -
State: closed - Opened by ir-fuel over 9 years ago
- 3 comments
#20 - appMessagesPushUpdate has incorrect signature (__nullableerror instead of __nullable error)
Issue -
State: closed - Opened by nivsto over 9 years ago
- 2 comments
#19 - App crashed in ExternalAccessory (iOS9)
Issue -
State: closed - Opened by HankMisfit over 9 years ago
- 2 comments
#18 - Updated to pebble 2.0 to 3.1.0 using cocaopods.... sending message from watch to iOS app is not working... i.e Button tap on watch
Issue -
State: closed - Opened by raheelahmad786 over 9 years ago
- 6 comments
#17 - PebbleKit-Static references PebbleKit and hence headers don't parse
Issue -
State: closed - Opened by motocodeltd over 9 years ago
- 5 comments
#16 - `watch.new` property is incompatible with Objective-C++
Issue -
State: closed - Opened by sjmerel over 9 years ago
- 2 comments
Labels: bug
#15 - 3.0 is not available via CocoaPods
Issue -
State: closed - Opened by pconno over 9 years ago
- 1 comment
#14 - Why platform iOS 7.1 for SDK 3.0?
Issue -
State: closed - Opened by mathiasAichinger over 9 years ago
- 2 comments
#13 - appMessagesRemoveUpdateHandler() has no effect
Issue -
State: closed - Opened by sjmerel over 9 years ago
- 2 comments
#12 - PebbleKit doesn't include "full" Bitcode
Issue -
State: closed - Opened by sjmerel over 9 years ago
- 10 comments
Labels: bug
#11 - isMobileAppInstalled always returning YES (iOS 9)
Issue -
State: closed - Opened by abcdev almost 10 years ago
#10 - Allow removal of added AppUUIDs
Issue -
State: closed - Opened by edwinfinch almost 10 years ago
- 3 comments
Labels: enhancement
#9 - appMessagesGetIsSupported frequently returns 0 when connection to Pebble classic from iOS SDK 3.0
Issue -
State: closed - Opened by jeradesign almost 10 years ago
- 9 comments
#8 - Choose BluetoothLE over Bluetooth-Classic more reliably
Issue -
State: closed - Opened by jeradesign almost 10 years ago
- 2 comments
Labels: enhancement
#7 - appMessagesKill does not kill app when called during willTerminate
Issue -
State: closed - Opened by jeradesign almost 10 years ago
- 1 comment
Labels: question
#6 - Carthage do no seems to work
Issue -
State: closed - Opened by yageek almost 10 years ago
- 6 comments
#5 - new pebblekit (3.0.0) produces lots of warnings in xcode 7
Issue -
State: closed - Opened by motocodeltd almost 10 years ago
- 14 comments
#4 - Update to support CocoaLumberjack 2.0
Issue -
State: closed - Opened by parrots almost 10 years ago
- 1 comment
#3 - Any chance of removing CocoaPods?
Issue -
State: closed - Opened by gabebear over 10 years ago
- 2 comments
#2 - appMessagesPushUpdate fails quietly on GCD side-thread
Issue -
State: closed - Opened by alist over 10 years ago
- 4 comments
#1 - Return value documentation for appMessagesAddReceiveUpdateHandler
Issue -
State: closed - Opened by alist over 10 years ago