cordova blackberry 10 can't deploy to device - macos

I followed instructions from the phonegap platform guides to create a hello world app and deploy to BB10. Had no problems with Android or iOS, but when I try to run the app on a BB10 I get this output:
$ platforms/blackberry10/cordova/run --device --keystorepass passhere --devicepass devicepasshere
[INFO] Target Z30-2ba65880 selected
[INFO] The existing debug token is valid
[INFO] Deploying debug token to target "Z30-2ba65880"
[INFO] Sending request: INSTALL_DEBUG_TOKEN
[INFO] Action: Install Debug Token
[INFO] File size: 2645
[INFO] result::success
[INFO] Populating application source
[INFO] Parsing config.xml
[INFO] Generating output files
[INFO] Package created: /Users/adriaan/Documents/phonegap/hello/platforms/blackberry10/build/simulator/bb10app.bar
[INFO] Package created: /Users/adriaan/Documents/phonegap/hello/platforms/blackberry10/build/device/bb10app.bar
[INFO] BAR packaging complete
[INFO] Sending request: INSTALL_AND_LAUNCH
[INFO] Action: Install and Launch
[INFO] File size: 78983
[INFO] Installing com.example.hello.testDev_ample_hellodf4765a1...
[INFO] Processing 78983 bytes
[INFO] actual_dname::actual_id::
[INFO] actual_version::result::failure 500 'ascii' codec can't decode byte 0xe2 in position 120: ordinal not in range(128)
I've tried this on Mountain Lion and Mavericks. On Mountain Lion I had the native and webworks sdks installed, on Mavericks only the Web Works.

Somewhere in your project some data is not correctly encoded as UTF-8. Check your filenames and file content for non UTF-8 characters and make sure you escape or replace them.

I face same issue please follow below step i resolve this issue by change the author name from bar-descriptor.xml
solution 1)
changed the author simply to "Julian Buss", recreated the debug token, cleaned the project and then I could run it on the device. Problem solved. click here
solution 2)
Remove debug token from your device or simulator please follow below step
1) goto Setting->Security and Privacy->Development Mode-> click on remove debug token button(This button is display if and only if you have install any debug token )
2) if you have not install debug token then regenerate debug token and install it.
I hope this will work This solution is work for me.

Related

install4j giving "install4j: compilation failed. Reason: Password might be wrong. (Windows)"

We are using install4j 7.0.12 with JDK 1.8 and when building in linux giving below error (--win-keystore-password' password is wrong ) , whereas password of the keystore is correct . and we are passing the password from pom.xml only . same build is ruuning fine in local (windows ) .
Please advise
15:12:58 The ' characters around the executable and arguments are
15:12:58 not part of the command.
15:12:59 [INFO] install4j version 7.0.12 (build 7368), built on 2019-06-25
15:12:59 [INFO] Using Java 1.8.0_181 from /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-7.b13.el7.x86_64/jre
15:12:59 [INFO] Registered to
15:12:59 [INFO] 15:12:59 [INFO] Loading config file /home/jdk_install/compl/target/installer/my-setup.install4j
15:13:01 [INFO] install4j: compilation failed. Reason: Password might be wrong. (Windows)
Please advise
one update , just found that this failing at this plugin
install4j-maven-plugin:1.1.1:compile (compile-installers)

Appcelerator Studio apps does not run after El Capitan Update. Invalid Request on compile

As the title says, After I have updated my OS to El Capitan all my apps on Appcelerator Studio does not build successfully anymore. Even newly created sample apps does not build. I only get a very generic error message from the console.
My app is targeted for iOS and Android and it does not work for both. I get the same error message as below.
[INFO] : ----- OPTIMIZING -----
[INFO] : - android/alloy.js
[INFO] : - android/alloy/sync/localStorage.js
[INFO] : - android/alloy/sync/properties.js
[INFO] : - android/alloy/sync/sql.js
[INFO] :
[INFO] : Alloy compiled in 1.48612s
[INFO] : Alloy compiler completed successfully
[ERROR] : invalid request
How to resolve this? I already tried to project clean multiple times.
That has nothing to deal with the operating system.
Solution;
Open terminal
appc logout
appc login
Ta dah! - solved :-)

Are there any jenkins variables for maven builds?

I am in need of accessing data that is produced through a maven build during a run on Jenkins which is then used in a curl command. This ultimately sends a message to a bot to post in a chat room. Plugins are not an option for this particular chat client unless I would be the one to make them. Any other plugins that would be able to execute curl or hit url are fine given I can get to the data.
Currently when I run the command
mvn surefire-report:report
I am able to see output like this from the job:
...
Results :
Failed tests:
passwordLengthRequirement(test.java.com.company.appium.suites.RegistrationTest): expected:<P[assword must be 6 characters or longer].> but was:<P[lease accept the Terms of Service].>
...
Tests in error:
SendText(test.java.com.company.appium.suites.ChatTest): Timed out after 10 seconds waiting for presence of element located by: By.xpath: //window[2]/UIAKeyboard[1]/UIAKey[5]
...
Tests run: 40, Failures: 3, Errors: 2, Skipped: 4
[ERROR] There are test failures.
Please refer to .../target/surefire-reports for the individual test results.
[INFO]
[INFO] <<< maven-surefire-report-plugin:2.16:report (default-cli) # ios_junit <<<
[INFO]
[INFO] --- maven-surefire-report-plugin:2.16:report (default-cli) # ios_junit ---
[WARNING] Unable to locate Test Source XRef to link to - DISABLED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:26.412s
[INFO] Finished at: Mon Jan 13 11:19:25 EST 2014
[INFO] Final Memory: 16M/81M
[INFO] ------------------------------------------------------------------------
Recording test results
If there are variables that can be used to get the data that would be a huge help but I don't know what they are if they even exist. My latest attempt has been to use the Post Build Task plugin to access the build.xml or log files with completed output. When trying to grep the build.xml that is created and extract the data I need grep is not working for some reason
XML:
`<failCount>72</failCount>`
`<skipCount>4</skipCount>`
`<totalCount>76</totalCount>`
Command:
$FAIL_COUNT=grep "failCount" ../../builds/$BUILD_NUMBER/build.xml | cut -d">" -f2,2 | cut -d"<" -f1,1
Output:
+ =grep failCount ../../builds/25/build.xml
/var/folders/2b/jv3l9cys1sqbbk6l2hxx_n1000007c/T/hudson6366869578068337646.sh: line 3: =grep: command not found
This page has been helpful with getting other variables but does not list what could be available during a maven run
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables
The message I am ultimately trying to send would be something like
Finished with status '$BUILD_STATUS'. Total tests run '$TOTAL_COUNT'. Total failed tests '$FAIL_COUNT'.
Thanks in advance for any suggestions.

Heroku app not recognized as a play application

I'm using heroku, play framework (v 2.2.1)
and IntelliJ IDEA as IDE.
Everything has already worked but when I added maven as framework support in IntelliJ, when I pushed again, my application wasn't recognized as a play app.
Here is my log when I push:
-----> Java app detected
-----> Installing OpenJDK 1.7... done
-----> Installing settings.xml... done
-----> executing /app/tmp/cache/.maven/bin/mvn -B -Duser.home=/tmp/build_78991f
d-32f6-43df-856c-f9059e8fa59d -Dmaven.repo.local=/app/tmp/cache/.m2/repository
s /app/tmp/cache/.m2/settings.xml -DskipTests=true clean install
[....]
[INFO] ------------------------------------------------------------------
------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------
------
[INFO] Total time: 2.387s
[INFO] Finished at: Tue Jan 07 14:57:19 UTC 2014
[INFO] Final Memory: 8M/514M
[INFO] ------------------------------------------------------------------
------
-----> Discovering process types
Procfile declares types -> web
-----> Compressing... done, 74.7MB
-----> Launching... done, v8
http://javaepidroid.herokuapp.com deployed to Heroku
To git#heroku.com:javaepidroid.git
f809301..b319499 master -> master
My app directory is in the root directory's repository.
Had anyone already has this kind of issue with heroku ?
As describe in this buildpack from github/heroku (for play2 apps) :
You need that your application is :
a sbt application, ie, one file matching one of these pathes :
root-app/*.sbt
root-app/project/*.scala
root-app/.sbt/*.scala
root-app/project/build.properties
a play application, ie. has this file : root-app/conf/application.conf
But you may also specify the buildpack of your heroku app :
$ heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-scala.git
As said in heroku documentation

sonar-maven3-plugin Javascript not respecting -Dsonar.source

I have a project that contains javascript files in src/main/webapp/js. In order to analyze these, I am executing the following:
mvn install org.codehaus.sonar:sonar-maven-plugin:3.5:sonar -Dsonar.branch=js -Dsonar.language=js -Dsonar.sources=src/main/webapp/js -Dsonar.login=sonar -Dsonar.password=sonar
I have also attempting this with: -Dsonar.importSources=true
When I execute this, I get a build success. However, when I look at the js project I created, it contains no data. When I look at the logs, I see this which leads me to believe that the sonar.sources property is not being read.
[INFO] [17:38:42.273] Base dir: /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace
[INFO] [17:38:42.273] Working dir: /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace/target/sonar
[INFO] [17:38:42.273] Source dirs: /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace/src/main/java, /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace/target/generated-sources/wsimport
[INFO] [17:38:42.273] Test dirs: /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace/src/test/java
[INFO] [17:38:42.273] Binary dirs: /home/mw-sandbox/.jenkins/jobs/ssi-wdf-re/workspace/target/classes
[INFO] [17:38:42.273] Source encoding: UTF-8, default locale: en_US
Can anyone suggest a solution for this?
For now, it is not possible to use properties such as "sonar.sources" when the analysis is triggered with Maven. See http://docs.codehaus.org/display/SONAR/Analysis+Parameters. But it should be soon. See http://jira.codehaus.org/browse/SONAR-4536.
So, you can work with Maven profiles to override source directories.
A work-around have been found in this post :
Empty metrics in sonar for web and javascript projects
It is a bit messy with the maven profiles, but I tried it, it does the job...

Resources