Hey im trying to do a mobile testing in JMeter, i've followed every step of this guide, and the recording works fine. The problem is that i have to record in a native app and when i try to log in i get the following error message:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
Im not sure what to do
Why you're asking us and not the author of "this guide"?
These "every steps" are not complete, there is a couple more "every steps" which you need to "follow"
In the application section of your app manifest add the following entry:
android:networkSecurityConfig="#xml/network_security_config
Add network_security_config.xml file to your application resources folder and copy the below code there:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<debug-overrides>
<trust-anchors>
<!-- Trust user added CAs while debuggable only -->
<certificates src="user" />
</trust-anchors>
</debug-overrides>
</network-security-config>
Re-compile your application in the debug mode:
gradlew assembleDebug
Replace the app you're trying to record with the debug .apk from the previous step
You should be able to record now
More information:
Android Network Security Configuration
Configure Android Devices for Proxy Recording
I publish my exe and activate auto updates.
But when I compile the exe, there is an error:
Severity Code Description Project File Line Suppression State Error An
error occurred while signing: Failed to sign
bin\Debug\app.publish\myapp.exe. SignTool Error: Invalid option: /fd
So I couldn't publish.
When I try to uncheck "Sign the ClickOnce manifest" the error is gone
but I couldn't install the package because Windows doesn't allow and the Windows Defender SmartScreen blocks my app because there's no certificate.
I have to add a certificate from "Sign the ClickOnce manifest" but now it gives the "SignTool Error: Invalid option: /fd" error.
How can I solve this problem?
I had to change the Signature Algorithm to sha1RSA from sha256RSA
I did just the opposite as Stefano - changed it from sha256RSA to sha1RSA - and then it allowed me to publish without the error.
Just changing the signature algorithm may do the trick.
I encountered the same error message when migrating an old ClickOnce project from VS2018 to VS2017. It seems my VS2018 was using an old version of SignTool.
I found (and succeeded with) a tip to change registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows to make Windows to use newer SDK (in my situation SDK v8.1A was the most recent).
The original tip can be found here: https://social.msdn.microsoft.com/Forums/en-US/a39b9f82-aaec-4bbd-8cb2-3cade50796ba/an-error-occurred-while-signing-failed-to-sign-bindebugapppublishprogramexe-signtool-error (scroll down to answer by nikidimi)
Go to the myapp.csproj file, which is the project file, and search for 'SignManifests' PropertyGroup, change the value to false, and the error disappears. This worked for me.
I install an Orthanc Server (PACS) with WebGui, and upload a few dicoms from osirix dicom sample. I have a some problem with command findscu from package dcm4che3. When I called /findscu -c TEST#127.0.0.1:4242 -m PatientName="WRIX" , I have an error:
org.dcm4che3.net.AssociationStateException: Sta1 - Idle
at org.dcm4che3.net.State.writeAReleaseRQ(State.java:223)
at org.dcm4che3.net.Association.release(Association.java:271)
at org.dcm4che3.tool.findscu.FindSCU.close(FindSCU.java:463)
at org.dcm4che3.tool.findscu.FindSCU.main(FindSCU.java:380)
in orthanc log:
E0713 16:20:51.875545 main.cpp:180] Unknown remote DICOM modality AET: "FINDSCU"
E0713 16:20:51.875589 CommandDispatcher.cpp:776] Find requests are disallowed for the AET "FINDSCU"
E0713 16:20:51.875603 CommandDispatcher.cpp:852] DIMSE failure (aborting association): DIMSE Caller passed in an illegal association
I think I need to add in orthanc.json FINDSCU how ?
You must declare your modality FINDSCUin the DicomModalitiesoption of the configuration file of Orthanc, otherwise Orthanc will refuse to answer for security reasons. More information is available in the Orthanc Book, in the section entitled "Understanding DICOM with Orthanc".
I'm getting a Jenkins error when building an Xcode project. I know many have had this issue - and I've read and tried hours worth of tips to no avail.
This is the Execute Shell command I'm telling Jenkins to run:
export DEVELOPER_DIR='/Applications/Xcode 6.app/Contents/Developer/'
cd TM
xcrun xcodebuild clean build
Here is the error message in my Jenkins output:
=== CLEAN TARGET TM OF PROJECT TM WITH THE DEFAULT CONFIGURATION (Release) ===
Check dependencies
[BEROR]Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
[BEROR]CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 8.0'
Create product structure
/bin/mkdir -p /Users/Shared/Jenkins/Home/jobs/TM/workspace/TM/build/Release-iphoneos/TM.app
Clean.Remove clean build/Release-iphoneos/TM.app
builtin-rm -rf /Users/Shared/Jenkins/Home/jobs/TM/workspace/TM/build/Release-iphoneos/TM.app
Clean.Remove clean build/Release-iphoneos/TM.app.dSYM
builtin-rm -rf /Users/Shared/Jenkins/Home/jobs/TM/workspace/TM/build/Release-iphoneos/TM.app.dSYM
Clean.Remove clean build/TM.build/Release-iphoneos/TM.build
builtin-rm -rf /Users/Shared/Jenkins/Home/jobs/TM/workspace/TM/build/TM.build/Release-iphoneos/TM.build
** CLEAN SUCCEEDED **
=== BUILD TARGET TM OF PROJECT TM WITH THE DEFAULT CONFIGURATION (Release) ===
Check dependencies
Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 8.0'
** BUILD FAILED **
The following build commands failed:
Check dependencies
(1 failure)
Build step 'Execute shell' marked build as failure
Tips I've tried with no success:
I've set my Code Signing in my Build Settings (current, Release = Don't Code Sign; Release > Any iOS SDK = iPhone Developer).
I've indicated in the Xcode plugin Configuration where my login.keychain file is.
I've uploaded my .developerprofile to Jenkins and indicated it should be imported before each build.
And more.
Not sure what else I can do. It seems significant that it says team ID “(null)” - but I can't find any answers on why that is.
I am running Xcode 6 with a target of iOS 8.0.
I wish this could be a help.
An example script.
http://blog.octo.com/wp-content/uploads/2010/11/build.txt
Just fixed this issue with Jenkins and Xcode 6.4.
Make sure that you have at least one Developer Certificate in your login keychain. Right-click on the certificate and click "Get Info" to show permissions.
Expand the "Trust" list and for the field "When using this certificate", select "Always trust".
Close the window. There should now be a blue "+" sign on the Dev certificate.
Happy Jenkins!
I create Sencha Touch Application i wont create APK file of that Application i download sencha sdk tools and configure now what step need to follow to create APK file using sencha-sdk tool
pl help me to create APK file using sencha-sdk tool
You can use Phonegap and eclipse to create native apk for andriod
http://wiki.phonegap.com/w/page/30862722/phonegap-android-eclipse-quickstart
You can also create the apk without sencha sdk tools as follows
Follow the steps
1.- Sign up in https://build.phonegap.com/
2.- In your PC create a new Folder with two new folders, "assets" and "test"
3.- In "assets" move all you sencha touch code
4.- In the root of folder, move your icon (of app), the index.html file (the same index used in sencha touch app) and the "config.xml"
5.- add your principal folder to zip and upload to phonegap
6.- Finally you obtain installers to android, windows phone, blackberry, ios, symbian and webos
config.xml https://build.phonegap.com/docs/config-xml
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns = "http://www.w3.org/ns/widgets"
xmlns:gap = "http://phonegap.com/ns/1.0"
id = "Name mobile"
version = "1.0.0">
<name>name Mobile</name>
<description>
</description>
<author href=""
email="">
cmujica
</author>
<gap:platforms>
<gap:platform name="android" minVersion="2.3" />
<gap:platform name="webos" />
<gap:platform name="symbian.wrt" />
<gap:platform name="blackberry" project="widgets"/>
</gap:platforms>
<icon src="icon.png" gap:role="default" />
<gap:splash src="assets/images/bg-blue.png" />
<feature name="http://api.phonegap.com/1.0/network"/>
<!-- sample preference specification -->
<!-- <preference name="autorotate" value="false" readonly="true"/> -->
</widget>
I would prefer to do it with command in comand prompt.
just make the key store for the app
keytool -genkey -v -keystore my-release-key.keystore -alias alias_name
-keyalg RSA -keysize 2048 -validity 10000
replace my with you application name.
make sure that where ever you create the key store copy it from there and put it inside the application then after update the packager.json and give the name for the key store which should be similar to what you hv copied.
make a build folder outside the local server and give it any name and then update the folder name in the packager.json.
Now on your comand prompt go to the app and type
sencha package build packager.json
you will get a package in your build folder.
A simple quick way from Sencha Touch to Android apk using the default app that gets generated.
Pre-req:
1) Ant: Configure ANT_HOME and append to Path as %ANT_HOME%\bin;
2) Java: Configure JAVA_HOME and append to Path as %JAVA_HOME%\bin;
3) Ruby
4) Android SDK (If Android SDK is unzipped at C:\Mobile\AdtBundle, then your sdk home is C:\Mobile\AdtBundle\sdk i.e till the sdk folder)
4.1) Append to Path as C:\Mobile\AdtBundle\sdk\tools;C:\Mobile\AdtBundle\sdk\platform-tools;
4.2) Download the required Android API by running the 'C:\Mobile\AdtBundle\SDK Manager.exe', in my case it was androidAPILevel=14 i.e. Android 4.0
5) Certificate Generation: (Run the below command from the command prompt in your JAVA_HOME\bin location. Please note its important to specify the path where the certificate will be stored, in my case its C:\myapp.keystore)
keytool -genkey -v -keystore C:\myapp.keystore -alias myapp_alias -keyalg RSA -keysize 2048 -validity 10000
Steps:
1) Generated a new app using the following command from my Touch Directory location, in my case C:\Mobile\touch-2.3.1
sencha generate app MyApp ../MyApp
2) Go to your 'Generated App folder' and open packager.json file. Modify the file as follows.(Please note, I have simply modified this file, haven't removed any attributes that are specific to iPhone, it doesn't really matter whether you remove them or not. Even few params like outputPath wont matter wrt the apk output location. Also update your icon as required by android)
{
"applicationName":"MyApp",
"applicationId":"com.mycompany.myapp",
"bundleSeedId":"KPXFEPZ6EF",
"versionString":"1.0",
"versionCode":"1",
"icon": {
"36":"resources/icons/Icon_Android36.png",
"48":"resources/icons/Icon_Android48.png",
"57":"resources/icons/Icon.png",
"72":"resources/icons/Icon~ipad.png",
"114":"resources/icons/Icon#2x.png",
"144":"resources/icons/Icon~ipad#2x.png"
},
"inputPath":"./",
"outputPath":"C:\Mobile",
"configuration":"Debug",
"platform":"Android",
"deviceType":"Universal",
"certificatePath":"C:\Mobile\myapp.keystore",
"certificateAlias":"myapp_alias",
"certificatePassword":"android",
"provisionProfile":"",
"notificationConfiguration":"",
"sdkPath":"C:\Mobile\AdtBundle\sdk",
"androidAPILevel":"14",
"permissions":[
"INTERNET",
"ACCESS_NETWORK_STATE",
"CAMERA",
"VIBRATE",
"ACCESS_FINE_LOCATION",
"ACCESS_COARSE_LOCATION",
"CALL_PHONE"
],
"orientations": [
"portrait",
"landscapeLeft",
"landscapeRight",
"portraitUpsideDown"
]
}
3) Go to your generated app on the command prompt and run the following command
sencha app build native
4) Congrats, ur MyApp.apk is avl at 'Generated App folder'\native-package-mobile\MyApp\packager.json\MyApp.apk
From the command line you enter
sencha app build native
But before you need to work through packager.json