why my Mac app fails to launch, signing issue? - xcode

I'm developing a Mac app that will be released outside the Mac App Store.
So, basically I just automated the build process: it builds the app and signs the .app file with a Mac Dev ID.
If I sign this app with my credentials it works as expected. Either in my machine or my peers machine.
But, if my peer signs it with his credentials (using the same scripts), the app crashes either in his machine or mine. This is the error from the Console:
6/27/14 3:04:39.647 PM taskgated[1807]: none of the 1 applicable provisioning profile(s) apply
6/27/14 3:04:39.647 PM taskgated[1807]: killed com.myCompany.myApp[pid 2255] because its use of the com.apple.developer.team-identifier entitlement is not allowed
6/27/14 3:04:39.648 PM com.apple.launchd.peruser.501[286]: ([0x0-0x117117].com.myCompany.myApp[2255]) Exited: Killed: 9
6/27/14 3:04:39.719 PM CoreServicesUIAgent[2258]: Error: qtn_file_apply_to_path error: Read-only file system
6/27/14 3:04:42.021 PM CoreServicesUIAgent[2258]: Unable to continue stopped application -- error -600
What are we doing wrong? and how can we solve it?

Related

Jenkins Agent can't reconnect

I've been attempting to setup a Windows agent for our Jenkins on Linux to use. Mostly using the instructions from https://www.gdcorner.com/2019/12/30/JenkinsHomeLab-P3-WindowsAgents.html
Only mostly, as those (like EVERY OTHER SET I've found) don't match the current Jenkins screens.)
I got to the point where I ran the curl/java -jar commands on the Agent machine in an Administrator Command window.
It worked, and connected to Jenkins, showed up as running. Though this means it was still running as a normal program in a command window.
While attempting to figure out what was meant by "Click the Launch agent from browser. " - which showed a small window that should then be displayed - which would allow you to install it as a service, I closed the Command window.
I never figured out how to "click the launch agent from browser", so I opened a new admin command window and re-ran the commands. They no longer work. It gets this error every time: (note that "WinDInstaller" is really "Win%2DInstaller")
Sep 28, 2022 10:15:40 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using C:\Enterprise\Agent\remoting as a remoting work directory
Sep 28, 2022 10:15:40 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to C:\Enterprise\Agent\remoting
Failed to obtain http://metrixbld1:8080/computer/WinDInstaller/jenkins-agent.jnlp?encrypt=true
java.io.IOException: Failed to load http://metrixbld1:8080/computer/WinDInstaller/jenkins-agent.jnlp?encrypt=true: 404 Not Found
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:514)
at hudson.remoting.Launcher.run(Launcher.java:346)
at hudson.remoting.Launcher.main(Launcher.java:297)
Waiting 10 seconds before retry
It seems like it should be possible to get an Agent running on windows as a Service - but so far I've not found a set of instructions that work.
EDIT: Since that agent definition no longer worked, I created a new one and had it just copy the settings from the old one.
Then ran the new java/agent command - and it worked.
Apparently you can only launch a new agent once. If it ever stops you have to re-create it????

Could not launch “Runner” Domain: IDEDebugSessionErrorDomain Code: 3

Could not launch “Runner”
Domain: IDEDebugSessionErrorDomain
Code: 3
Failure Reason: failed to get the task for process 1189
User Info
DVTRadarComponentKey = 855031;
RawLLDBErrorMessage = "failed to get the task for process 1189";
I resolved this error by Trusting my developer account on the iPhone. This particular setting can be found at.
Settings > General > Device Management
The problem is in Code signing. Your App is signed with wrong provisioning profile and Xcode isn't allowed to attach debugger to app. For example if you wanna to attach debugger to app that's is signed with AdHoc provisioning profile, you can install&run your app on your device but you can't debug it (attach debugger). If you wanna to attach debugger to your app, you need to use App signed with Development provisioning profile. Check your Signing setting for your project and be sure you are using development Provisioning profile to signing the app.
Enabling WiFi/Cellular on my iPhone fixed the problem for me.
run the following command in terminal
sudo DevToolsSecurity -enable
ref :- https://developer.apple.com/forums/thread/120282

Nativescript Sidekick Publish to App Store

I'm running Sidekick on my Windows 10 machine (64b).
I'm trying to publish my app to the Apple AppStore.
Certificate, provision is all ok.
When I publish, build is made, I can log in when asked and fill in the verication code.
But then I get error 'Spawn Failed'. Googled this error, but didn't find anything.
Erros in the log are:
[19-03-08 10:52:20.711] (CLI) Build machine host name:
administrators-Mac-16.local
[19-03-08 10:52:58.349] Spawn failed.
, Error: Spawn failed.
at CloudPublishService.getiOSError (C:\Users\bartad\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:79:21)
at CloudPublishService.
(C:\Users\bartad\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:96:29)
at Generator.next ()
at fulfilled
(C:\Users\bartad\AppData\Roaming.nativescript-cli\extensions\node_modules\nativescript-cloud\lib\services\cloud-publish-service.js:4:58)
at
Does anyone have an idea what's wrong here ?
Thanks
Bart
Issues I encountered:
1) Provisioning was not right. Went back through and checked that each step is for a Distribution certificate and profile, not a development profile.
2) I assumed that tns resources generate would create my icons and splashes. It did, but Sidekick ignores them. You must recreate them in Sidekick.

Docker "hello-world" is giving "process cannot access the file because it is being used by another process"

We have just uninstalled Docker Community Edition and installed Enterprise Edition on a Windows Server 2016 System as per these steps.
On reaching the last step which is to test a hello-world container we are receiving the following error:
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec
error: exit status 1: output: ProcessUtilityVMImage
\?\C:\ProgramData\Docker\windowsfilter\e345ad40cc8f7d073f62501b7445d42d677889c04b2c6fe0963ea6e092b52f95\UtilityVM:
The process cannot access the file because it is being used by another
process.
We are seeing lots of examples on SO related to other types of applications giving this error but not Docker.
How might we fix this?
This turned out to be an issue related to Symantec Endpoint Protection(SEP) clashing with Docker.
SEP needs to be upgraded to version 14 RU1 and several files need execution privileges.
Symantec posted a fix here: https://support.symantec.com/en_US/article.TECH246815.html which we have tried and worked.

Discover why GoDC won't start on Mac

I'm trying to run GoCD on MacOS (10.12) for testing purposes. When I run both the server and the client apps, they do not provide any GUI output (they should show progress bars or a host configuration) and they quit a couple of seconds after starting.
When I try to run the apps from Terminal as:
/Applications/Go\ Server.app/Contents/MacOS/go-server
I get the following output:
Got directory: /Users/taatyyu1/Library/Application Support/Go Server [It exists]
and then the app quits.
How can I discover what is the issue of the apps not starting properly?
The logs of the apps are available in
~/Library/Application\ Support/Go\ Server/osx-app.log
and
~/Library/Application\ Support/Go\ Agent/osx-app.log
They contain the information from apps starting up and you can use them to figure out what goes wrong

Resources