Repository navigation
Pebble connects, but appMessagesAddReceiveUpdateHandler never called #4
Description
Activity
I reloaded the pebble firmware file to make sure that wasnt altered in any way, and the watch now alternates between saying "Up" and "Down" on press, or "Send Failed!"
The ios app still reports "Watch connected" but the console on most recent runs says
2016-04-04 13:02:17.044 PebbleKit-iOS-Tutorial-2[317:32905] [W] [PBWatchReconnectionService addPeripheralIdentifier:] Couldn't retrieve peripheral for identifier 5D1855AB-A883-5F6B-7E62-8C5C4E4722FBTook another look at this to see if anythings changed, and it hasnt for me.
I found the appmessage docs updated with much more error checking and added all that. In cloudpebble I tend to get Error preparing the outbox APP_MSG_BUSY
On ios I still get the
Couldn't retrieve peripheral for identifiererror on every load. and appMessagesAddReceiveUpdateHandler is never called@jacobrosenthal, I faced this problems with messaging too.
Try to send some message from app to Pebble every timewatchDidConnectgets called.@DmytroLisitsyn Thank you sir. That does indeed fix this example! (though not the
Couldn't retrieve peripheral for identifierwarning)Still Couldn't retrieve peripheral for identifier
That is sad!
Anyone can help me?
KeyButtonUp and KeyButtonDown can not be called at all.This was my fix commit in my fork
jacobrosenthal@8a8fcc0Thanks jacobrosenthal, Perfectly solve the issue. And is there a swift version for this example project?
Up/down presses on the demo app arent triggering appMessagesAddReceiveUpdateHandler