Sideloading ipa using ideviceinstaller - linux

I tried to install ipa using linux machine. I never done this before and got this error.
SIdeloading ipa

The application you are trying to install does not have a digital signature. iOS will only install applications which a valid digital signature on your phone. That's why you get the error message "No code signature found".
You can sign the application yourself if you have an iOS development account. Once the application is signed, you can install it using ideviceinstaller.
Alternatively, you can jailbreak your phone, which will cause iOS to no longer validate the digital signature of applications you are trying to install.

Related

Code signing systems for software in Linux like Authenticode in Windows

SO!
We're developing a desktop app for Windows and using *.pfx Code Signing certificate from GlobalSign for signing code after compiling.
Now we have also started developing and building this app in Linux for Linux-based systems.
Does Linux have the similar trust systems for apps as Authenticode for Windows? Are there any CA such as GlobalSign?
From my search i only found that Linux devs either use self-signed certs (assuming themselves as CA), or trying push their apps to large soft repos such as HomeBrew., that signed them automatically.
From there: Code Signing for Linux.
And from there: Authenticode or other code signing for Mac and Linux.
That's Linux authenticate code by validation binaries once while installing the package. The package (e.g. RPM) contains a cryptographic signature that must match the contents of the files or the installer will refuse to install. But what is exactly this crypto signature and how to take this sign?
Thanks in advance!

How to send a Unity HoloLens 2 project for immediate testing by a remote colleague (without certification from Microsoft Store)

I am developing for HoloLens 2 and I don't have the device (I am using the Emulator to test).
I want to build the project with Unity and send the built package to a colleague that is not a developer - meaning, he is not good with Visual Studio - and who wants to test the app.
I tried using Microsoft Store and this worked for the initial P.O.C., but after the second submission I thought that it was going to be faster, but always takes up to 3 business days, which is not acceptable as a good workflow.
I know that, in ideal conditions, I should have the HoloLens, but this is not possible for now.
Do you have any idea on how to send packages to a non-developer person so that he can test the app in another country and so that it doesn't require a certification process like Microsoft Store?
You can take a look at the Sideloading feature provided by HoloLens Device Portal. Please follow this guide to connect the HoloLens over Wi-Fi or USB and manage your device from a web browser on your PC: Installing an app. In this way, you can directly send the app package to your colleague, and he can install it without using VS.

I get warning that "Invalid Code Signing Entitlements" with Apple Distribution Profile

I have an app which is on AppStore. It is signed as ios distrubution.
After a while my certificates are expired on apple developer account. I revoked these and created again. And I started seeing two certificates (iOS Distribution and Distribution). I saw a warning that is "Distribution for use in Xcode 11 or later".
Now I will update my app on appstore but I can't sign it with "iOS Distrubution". Because my xcode version is 11.5.
When I choose "iOS Distrubition" on my provisioning profile I can't sign my app.
When I choose "Distrubition" on my provisioning profile I can sign my app. But in this case while I try to upload app to appstore, I get a warning that:
ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'Development' for key 'com.apple.developer.icloud-container-environment' in 'Payload/...' is not supported."
How can I fix that?
I solved my problem by changing app publish method. Previously I used to get ipa on my windows device and send it to app store with transporter from my mac. Now I created xcarchive file on mac. After I clicked this xcarchive and send it with xcode app publish tool. I signed my app there (xcode tool). And I didn't get any error with this way.
I didn't do anything on my provisioning profile. I used "Distrubition (for xcode 11)". And it worked with xcarchive. I don't know why it doesn't work with ipa.

Unverified Publisher Warning still occurs after Code Signing

I am new to code signing. My goal is to be able to sign a setup.exe generated by Visual Studio and install it on my Windows 7 PC and my friends' Windows PCs without triggering unverified publisher or other warnings. The following approach did not work. What other steps do I need to take to achieve this?
On Windows 7, I followed the Original Answer at
How do I create a self-signed certificate for code signing on Windows? by completing following steps.
- created & imported CA
- created SPC & converted to PFX
- used first signtool command to sign a setup.exe generated by Visual Studio 2015.
The Digital Signatures General tab now says the "The digital signature is OK". But running the setup.exe on my Windows 7 PC triggers an Application Install Security Warning which says "The publisher cannot be verified. Are you sure you want to install this application?".

Running a signed midlet on the emulator produces a SecurityException

I have a signed midlet (VeriSign Class 3), which runs perfectly in several Nokia devices.
When I try to run it on the JME SDK 3.0 emulator it produces a java.lang.SecurityException: Application not authorized to access the restricted API.
It has all the permission it needs, otherwise wouldn't work on the devices.
It worked perfectly without the signing, but it's a pain in the neck to click an unclick everytime I compile, depending if I'm running the midlet on the device or on the emulator.
And well, I had to install the VeriSign CA Class 3 certificate on the emulator, in order to recognize the signature. I don't know if the problem is about this certificate, but without it the emulator wouldn't even start the application cause the CA was unknown.
Has anybody some experience with signatures and this JME SDK emulator?
Solved by using a newer version of the emulator (Java Wirelesss Tollkit 2.5.2)

Resources