I try download binary demo application from Kaa sandbox.
Eventually, I am faced with: BUILD FAILED
This is a "build exception" from Kaa sandbox:
Is this problem fixed with the Kaa 1.0.0 Banana Beach ?!
Thanks, Kaa IoT team.
This is because the normal kaa deployment in AWS uses a t12 micro instance. This limits the kaa usage. Once the limit is crossed this error will occur.
Creating a new instance will solve the problem. I was finding that the same thing was happening for me until I did so.
Related
I am trying to do the steps stated in https://www.eclipse.org/ditto/2018-05-02-connecting-ditto-hono.html#create-a-connection-to-hono to connect Ditto and Hono. I have tested Ditto and Hono with the steps explained "Hello World" for Ditto and "Getting Started" for Hono. I have created a tenant as explained in the Getting Started part but when I tried to do it for the example in the given link, I get Could not resolve host: hono.eclipse.org response.
What is the reason of this?
Thanks in advance
Did you see the red warning on top of the 4 years old blog post that this guide no longer works with the current versions of Eclipse Hono and Eclipse Ditto?
I would suggest to follow the link of that warning and follow the instructions of the Eclipse IoT Packages project.
I'm using Eclipse Ditto's sandbox for a university project and it has given me as result 502 Bad Gateway for days (almost a week) for each command I tried and I can't do basically anything in the dashboard. Are Eclipse Ditto's servers Down or is my problem?
If is ditto's fault are there any solution other then deploying docker and using ditto in local?
P.S: my team mate is experiencing the same issue
The Eclipse Ditto sandbox was offline - it is not maintained as "always available" instance, see also the warning disclaimer on the project site.
I would strongly recommend on running your own instance, a university surely has machines or free credits on public cloud providers to start a VM.
Whenever I am trying to publish the node.js application on Bluemix from Eclipse Neon 3 (4.6.3)` its giving me publish failure error.
An internal error occurred during: "Publishing to IBM Bluemix...".
org.eclipse.cft.server.client.v2.internal.V2CFClientProvider.supports(Ljava/lang/String;Lorg/eclipse/cft/server/core/internal/client/CFInfo;)Z
Thanks Santosh, I am able to reproduce the issue.
I can confirm this is a bug introduced in a recent version: when you attempt to publish a JavaScript application with an SSO Bluemix server from Eclipse Neon.3, you will encounter the exception listed above. The specific issue is a method signature mismatch between versions of Eclipse CFT.
We will work to fix this in our next release, however, to help you in the mean time, these are some workarounds:
If you install Eclipse Tools for Bluemix onto the latest release of Eclipse -- Eclipse Oxygen -- you will no longer see this problem. This issue only occurs with Eclipse Neon.
If you use an Eclipse Bluemix server configured without SSO, eg with a email/password, you will not encounter this issue.
Another option is to deploy your application from the console, using the CF CLI. You would use the 'cf push' command in this scenario, from the directory of your application.
Hopefully this helps!
So I have setup my Xbox One as a dev device and actually was able to run my app on my Xbox, but in order to use some new APIs to turn off scaling and what not I had to change my app target version to Build 14332. Unfortunately, after doing this, I am now not able to publish or debug my app to my Xbox and I am not getting very helpful clues as to why not.
I even reverted the target version back to Build 10240 but I am still getting this error:
Severity Code Description Project File Line Suppression State
Error DEP0700 : Registration of the app failed. Deployment Register
operation with target volume C: on Package
MyCompany.MyApp_1.1.19.0_x64__5wbv4ypmprn7c from:
(AppxManifest.xml) failed with error 0x80070002. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) MyCompany.MyApp
EDIT: I found a work around. Restart my Xbox One. Literally, every time I run my app, I have to restart my Xbox One! :(
I came across the same issue, and while restarting the console didn't help me, I did find another workaround: go to Dev Home and clicked Remove all Visual Studio pairings. I was able to deploy right after doing that.
I've ran into the really similar problem, however with running on the remote machine. The solution was the same as Pedro Pombeiro did on his Xbox One. I opened Windows Settings > Update & Security > For developers and Unpair All. Problem was solved and I could deploy and run the app on remote PC.
I am having trouble in testing a Midlet. I am using j2me sdk 3, the Midlet builds successfully, but when i try to run it, it fails and it shows the following message in the log:
Failed to connect to device {0}!
Reason:
Emulator {0} terminated while waiting for it to register!
I had the same problem. On the next system restart there where message about runMidlet crash due to DEP (Data Execution Prevention).
After turning off DEP all started to work perfect.
In case it could help, it was on Win2003, Java ME SDK 3.0.
UPDATE:
I advise to turn off DEP for all programs (it is "Turn on DEP for essential Windows programs and services only" option).
In my case turning off DEP for single runMidlet.exe had only temporary effect.
See also Java ME SDK Team blog entry on this
You probably need to increase the debugger timeout value. I work in WTK 2.5.x so I'm not sure where this setting is exposed (are you on Netbeans?) in version 3.0.
Somewhat out-of-date instructions for Eclipse and Netbeans.
Just go to tools/java platform, select the CLDC Framework blah blah blah and Click refresh.
If you are using Linux as your operating system just you need to type the command 'setenforce permissive' in the terminal.It will solve the issue.
Rishabh
Aside from the DEP issue mentioned in other answers, there is a useful list of solutions to common problems here.