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.0-beta9 2.1 (Android)
Watch Firmware: 2.7 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.
The answer to my particular issue, as it turns out, was that I had unused fonts. It's not a very obvious problem, so I hope this helps others out.
The main issue really was poor error reporting from cloudpebble due to the lack of error clarification returned from the pebble app to cloudpebble.
I have opened an issue on the cloudpebble github (that's where I found the answer) so if any further developments happen, they'll more than likely be there.
I found that the app had to be on a specific page for it to properly install on the pebble. I found this to be true if I installed on the terminal using the Pebble commands or using the web IDE CloudPebble.
The app has to be on the "My Pebble" scene/activity. Make sure when you attempt to install an app to Pebble that you are on that scene/activity regardless if you are installing using the web IDE or the command line.
Related
I've been working with PhoneGap for about two weeks now, yesterday I've build a new android app all went well except that the app starts very slow on my android device. It first shows me for three seconds just a black background except the navbar. So I want to ask how to boost it up or which files I could remove or what I've done wrong please I would be happy if you explain me also the file structure. Thanks in forward for your answers!
Your question is little bit vague. Please, give us more information about your app, about your config and what you’ve already tried.
If my app is slow on any device, I do generally the following:
Check if the same problem occurs in the browser
What’s going on at the start of the app in the browser (Chrome Dev Tools)
If nothing unusual happens, check the logs on the device
For Android, I’m using Logcat for checking what’s happening on the phone.
In order to use Logcat:
1.) Enable debugging mode on your Android phone
2.) You need Android Studio
3.) Connect your phone to your computer and start Logcat in Android Studio 3.1.2
4.) Check the logs while you are starting your app on the phone
It is not really a programming question. I have this app that continues to crash on my phone, but works fine for everybody else. I used to program android apps, so I have knowledge in this field.
It something on my phone probably it always crashes at the same stage. I did not program this app. How can I still get the details of the error or the trace of the exception?
I would suggest plugging the phone into your computer or laptop, opening up the Logcat tab in Android Studio and viewing the exception details as the app crashes.
This can be done separately from Android Studio using ADB but it involves more steps.
Of course, make sure that you have enabled USB debugging on your device before this.
2 days ago my chrome remote debugging of my ionic application was working perfectly. Now however with no changes my remote debugging will not display scope variables.
The Scope section of the remote debugger just says: "Not Paused". This appears always, including when the application is paused on a breakpoint.
I am guessing that the issue may be related to the fact I am debugging with source maps. I did a quick debug session vs a normal web page running in chrome on my tablet, and I could see scope variables that way. This leads me to believe it is potentially related to using source maps.
Additionally, there is an error at of the top of the debugger that says:
"Consider disabling Chrome Data Saver while debugging".
I can't say for sure if this error was always there or not, but I don't recall it being there previously.
However, data saver is off on both the PC and the tablet, which seems it should preclude that error from being shown.
I have been searching but I have only found one other thread related to this issue, and it appears it was never resolved. However, the thread matches my issue exactly:
https://github.com/google/WebFundamentals/issues/4463
Attached is a screenshot of the problem in action.
Debugger screenshot
I can still use the Watch section to see what is going on in my scope variables by typing them in (as you can see in the example screenshot).
Here is the chrome version information off chrome running on my PC:
Google Chrome 65.0.3325.181 (Official Build) (64-bit) (cohort: 65_win_181)
Revision dc3469be277cc962ba01d9c0cb5bb1a265676c36-refs/branch-heads/3325#{#725}
OS Windows
JavaScript V8 6.5.254.41
I have a Galaxy Tab A (2016) with S Pen.
The tablet is running Android version 7.
Any ideas anyone has to figure out what is going would be very appreciated.
Will
Eventually, for reasons I could not figure out, my app lost the ability to speak to my computer over WebSockets altogether.
Running this command seems to have fixed both my original problem and my new problem.
cordova plugin add cordova-plugin-websocket
I already had a websocket lib installed, but perhaps this one was better.
I hope that helps anyone else that has gotten stuck with this problem.
Will
Just started working with Ionic the other day, installed most recent version of framework and all required dependencies on my 2015 Macbook Air running El Capitan.
Everything seems to be working OK with the exception of this issue:
When trying to use the live reload option for development with my usb-connected android phone (via command "ionic run android -l"), I receive the following error message on my phone:
Webpage not available
The webpage at http://[local IP and port of my computer] could not be loaded because:
net::ERR_ADDRESS_UNREACHABLE
Note: I don't receive this message when I leave out the -l option.
I know that others have had this issue and I have read virtually all related articles that come up in a google search, but I am still at a loss for a solution.
Some have said this has to do with default restrictions imposed with Cordova whitelist plugin. I tried the changes specified in the below article but to no avail.
https://github.com/apache/cordova-plugin-whitelist
I've tried all other fixes that come up from a google search but without success. As a developer (even a relatively new one) I expect this as par for the course, but the frustration is starting to sink in.
Any help is much appreciated. Thanks.
I think you should see this link: http://blog.ionic.io/handling-cors-issues-in-ionic/
My phone cannot connect to the android ADB but I need to check its logs since it seems to be getting unique errors from an app I made. aLogcat app is outdated and getting "bug reports" from developer options is unreadable for me.
Is there any way for me to get a logcat report of my app while I'm running an application on it?
Edit: I use a droid Mini phone and it won't connect to eclipse. After installing the specific driver for the device it worked.
First of all, consider making ADB work for your device. Provided this is totally impossible, consider using ACRA. If you don't want to integrate fully with it, check their logcat collection code.