I read that BlackBerry signing keys can be only installed on one PC.
I'm compiling my Rhomobile Rhodes app on one PC. But the BlackBerry signing keys are installed on another PC. What I need to do in order to sign the app on another PC.
PS: I've set bbsignpwd in rhobuild.yml.
As per Blackberry guideline you have to create build from the PC on which Blackberry signing keys is installed.
Well, its possible to copy signing files from other PC to your PC and use them for signing (of course as long as the users trust each other).
Related
I have a Windows Phone individual developer account and need to do a beta testing internally. I used Appaloosa and HockeyApp for this purpose. But, when I try to download the app and install it on my Windows Phone, it shows a message "Can't install company app" on both Appaloosa and HockeyApp.
I heard that one needs to have a Symantec certificate and an .aetx file in order to install Windows Phone app which costs $299.00.
I need to know if there is any other option so that I can install my developed app freely on some Windows Phone devices which are intended for testing. I might need to email my .xap file to the testers and let them download and install for testing purpose.
You can install your developed app on some Windows Phone devices from Windows Store. If you have development account, you can publish your app with limited access. You will get link on your app. Your app will access only for people, who have this link. Another people will not find your app in Windows Store.
I have a windows phone 8.1 app.
My app is generating is Appxbundle file.
Now i want to give my application to enterprise's MDM solution like Maas360.
What else do i need to do ? ...Will the MDM solution take it from here, sign it with their certificate and distribute ?
I don't have any options to sign from developer end.
Regards,
Saurav
The customer needs to register for enterprise app distribution with Microsoft. They would then get Symantec certificate and you will sign the app with it.
After that the devices enrolled with MDM solution and the relevant enrollment token should be able to get your app.
You cant insatll your windows phone 8.1 application externaly .
I code sign the IBM AppCenter client for iOS using my Enterprise Certificate. I used a unique bundle identifier and provisioning profile for the same. The OTA installation works fine in most of the iOS devices.
In few devices iPhone5S powered with iOS 7.1.1, it fails to download and install and gives the error message "Unable to Download App" - App Center could not be installed at this time". I have checked the Code Signing properties in my codebase. Every thing looks fine. Note sure why this fails in few devices and works fine in most of the devices.
There could be multiple reasons:
as Idan said already, iOS 7.1 requires SSL (https) with a real SSL certificate, that is, self signed certificates don't work. Application Center must run on a server that has a CA authorized SSL certificate that matches the server URL. Earlier versions of iOS did not have this restriction.
the app might not be provisioned for the device. This depends on your provisioning profile. Development profiles are limited to preregistered devices. If you are able to side-load the app on the same device, the provisioning profile must be correct. Typically, when the provisioning profiles is wrong, the app appears to be downloaded to ca 75% and then the failure occurs.
the Apple server to validate the provisioning profile is not reachable. This happens seldom and is normally not specific to a device. This can only explain occasional random failures to install the app, but it cannot explain when an app fails always on the same device.
there might be a connection problem between the Application Center server and the device. In this case, you don't see the download to go to 75% but it stops earlier in the download process. In Worklight 6.1, the Application Center uses resumable downloads, hence a temporary connection problem should normally get resolved automatically. But it can be a permanent connection problem on specific devices. In order to check whether it is a connection problem, you could open the Worklight AppCenter Console on the device inside Safari and try to download any app binary ... The resulting network traffic is similar to the one that occurs during installation.
I hope this helps!
I need to sign my Adobe AIR application which is a native installer. Right now I just have a Windows version, but soon I'll be porting it to other OSes including mobile OS.
My query is whether I need to get a separate code signing certificate for each one or is one enough? Also does 32-bit and 64-bit matter?
Verisign have categorized certificates for Windows (.exe) and Adobe AIR (.air and .airi) separately. So which one should I obtain?
CAs selling code signing certificates always pretend that you need different certificates to sign different kinds of applications. This is basically a scam. Most of the time the certificates are exactly the same, only the file format might differ. Even if the file format isn't supported by your code signing tool, there are ways to convert between different formats. So basically it doesn't matter which certificate you buy.
If you package your AIR app with a captive runtime, you can simply use a self-signed certificate with the adt tool. It's only important to sign the executable created with adt and your installer afterwards. If you create a native installer directly with adt, provide your certificate using the code signing options.
Under Windows, you should use Microsoft's signtool utility to sign the .exe file of your app and your installer if you want to package with a captive runtime. So I'd choose a code signing certificate for Windows. But as I said, it doesn't really matter (and there are cheaper options than Verisign).
Under Mac OS X ("Gatekeeper"), things are a little different. You can only use certificates issued by Apple. You have to enroll in the "Mac Developer Program" ($99 per year) to receive a code signing certificate for OS X. If you use a captive runtime, sign the application bundle created with adt using the codesign utility. If you create a .pkg installer, use the --sign option of the productbuild tool. There's a similar "iOS Developer Program" for iOS apps.
Under Linux, you don't sign packages with certificates issued by a CA. You simply sign them with a GPG key that you can create yourself for free. You have to publish your public GPG key so your customers can make sure that your packages are valid, though.
For Android apps, you can simply use a self-signed certificate, AFAIK.
32-bit and 64-bit apps can be signed in exactly the same way. You don't need separate certificates. But adt will only create 32-bit apps anyway.
Is their any sites available to download windows 8 metro apps for offline installation. Alternative to windows store.Because i don't have internet connection in home.
Please tell me any sites ?
You have to be connected to install Windows 8 Store apps. You cannot sideload an app that has been downloaded from the Windows Store.
Alternatively, you can get your app directly from the developer without involving the Store, in which case, installation can be offline. Apps that aren't signed by Windows Store can only be installed on sideloading-enabled devices.
Actually you can install Windows apps offline, I did it by capturing the URL windows store referring to, it was a file with .appx or .appxbundle extension. However, the URL contained some security information referring to the Windows Store session and user id. It means you cannot multi-part-download it or resume it if disconnected, very disappointing in case of games with 2 Gb or more data. After that, I installed these packages with PowerShell command
Add-AppxPackage [Disk:\File Location\File name.appx]
without brackets. It installed and worked correctly.
Waiting for a dedicated side-software (Like Cydia or smith.) that does it in one-click.
It is only a few days for Windows app store to be live and unfortunately in your case, NO option to it for now.