pebble / cloudpebble

CloudPebble source. Here be dragons.
https://cloudpebble.net/
MIT License
211 stars 83 forks source link

"Installation failed. Check your phone for details." (No details) #116

Open tinnvec opened 9 years ago

tinnvec commented 9 years ago

I'm using Cloudpebble to develop a watchface for myself. Everything compiles well and I've not had troubles sending the face to my watch until now.

After compiling the watchface and linking to the phone, it returns an error of "Installation failed. Check your phone for details." However, the phone does not shed any light on what these details might be.

I've checked the usual suspects such as full watch slots and inability to connect to phone, but those were not issues in my case and I'm rather stumped as to what the problem might be. Any help would be greatly appreciated.

Pebble App Version: 2.1 (Android) Watch Firmware: 2.8 Watchface Source: GitHub

UPDATE 11/20: I didn't mention before that the phone app would crash often when attempting to load my watchface on the watch because I chalked it up to beta software. Today brought watch firmware 2.8 and phone app 2.1 proper, and while the phone app no longer crashes, the mysterious error continues without additional information on the phone.

(first posted on Stack Overflow)

ChristopherAlan commented 9 years ago

This happened to me and I found that I had created like 10 different font size resources but was only using 1. When I deleted the others and sent it to my phone it worked. Could help?

tinnvec commented 9 years ago

Thanks, ChristoperAlan, I actually accidentally did this the other day when i tried re-uploading my resources and it successfully sent to my phone.

Perhaps all this needs is more accurate error reporting from cloudpebble or even just an FAQ entry about unused resources

Katharine commented 9 years ago

I would love to have CloudPebble give better error messages. Unfortunately, the only message I get back from the install process is "success" or "failure".

willbrazil commented 9 years ago

@Katharine, I agree. I had a silly issue that took me a few min to resolve. I simply had all 8 app slots occupied. Again, it's silly but if the error message had mentioned what the problem was, it would have been an instant fix.

jor3l commented 9 years ago

Getting this with PebbleJS and the emulator, no idea whats wrong since it was working fine. :cry:

netgio commented 9 years ago

Same here (pebbleJS + cloud pebble + emulator) - working fine for 24 hours worth of builds but now I can't seem to install any apps - even the samples from the tutorial fail. I've restarted Chrome, logged in and out of CloudPebble, I've rebooted and still the same. Nothing in the compilation or application logs.

jor3l commented 9 years ago

@netgio For me, shutting down the pebble (click the gear) seems to fix the issue.

rdbsf commented 9 years ago

i was having same error. i cleared an app to make at least one empty slot and i was then able to install directly to the watch. hope that helps someone.

netgio commented 9 years ago

@jor3l - Thanks - that seems to be the workaround for the emulator... thought I'd tried it, but clearly I hadn't. I'm assuming this clears out some state on the servers that is not cleared by reloading the project or restarting the browser.

dallin-c commented 9 years ago

@netgio I have the same setup as you (Pebble.js, CloudPebble, and Emulator) but even restarting, logging in and out, and closing the browser didn't help. They really need to make a better error message!

EDIT: The cause was that I had unused images.

gcey commented 9 years ago

I also had this problem with the simulator in CloudPebble. Details would be very helpful. To me it seems, that my problems occurred, when I worked on two PCs (home @evening and work @day) on the same project and one PC blocked the other PC in some way.

jor3l commented 9 years ago

@gcey try to shut down the pebble emulator first (click the gear) then try again.

gcey commented 9 years ago

Sometime this helped, sometimes it didn't (maybe because the emulator was still active on the other PC).