Apple supports Over The Air (OTA) installation as long as we store both the manifest and the IPA in a publicly accessible location. Then we only have to share the URL of the manifest with our stake holders. I'm trying to store iOS builds in an Artifactory repository (generic package type) and achieve the same.
Currently we are storing them in our intranet and the setup works fine. We are looking at migrating to Artifactory but so far we have been unsuccessful even with anonymous access enabled (https://www.jfrog.com/confluence/display/JFROG/Users+and+Groups).
I reached out to JFrog. They only said it is possible but haven't offered any help. The license I have is basic and it doesn't cover SLA level support.
We need more informations
Are you able to download the IPA and the manifest with curl?
Be sure that you are using the 'List Browsing'
https://www.jfrog.com/confluence/display/JFROG/Browsing+Artifacts
I have made appx file, i have tested on Windows App Certification Kit Toolkit and also installing extension in windows 10 running properly, but when I publish the extension to the Store, it gives me this error:
"App Policies: 10.1.1 Extensions
Notes To Developer
Apps that claim to be an extension must clearly identify the app for
which they are an extension"
I have given a description in the json and appx files and also in windows dev partner, but it's still giving the same error in certification.
I can see that your extension is violating the policy 10.1.1.
As per the Microsoft below is the policy 10.1.1:
All aspects of your app should accurately describe the functions, features and any important limitations of your app, including required or supported input devices. Your app may not use a name or icon similar to that of other apps, and may not claim to be from a company, government body, or other entity if you do not have permission to make that representation.
Reference: Microsoft Store Policies
So you can try to refer to to the policy and check what thing in your extension cause this error.
Try to modify that thing and create a new package and try to host again may help you to solve the issue.
We're using Visual Studio Tools for Apache Cordova to build our app for iOS (and Windows).
We have a Mac running the remote agent. This works well, except we've only been able to have the setup produce signed .ipa files.
We're now looking into being able to create an unsigned "app" that we can deliver to our customer. They will then sign it with their enterprise certificate and distribute it within their orgainization (not the App Store).
The recommended way to deliver the app to the customer seems to be to create an xcarchive (I have looked at the option to deliver an ipa signed with our develoepr cert and then have the customer resign it with iReSign, but that seems flaky).
Is there a way to do that with this setup without any manual steps on the Mac?
Any pointers in the right direction would be much appreciated.
As far as i have analyzed, the easiest way to create an xcarchive is to use cocoon cloud service. Infact, it does gives the flexibility of generating both xcarchive and IPA.
Also you have full control of your build process as it provides various config controls and it is already used by some renowned companies.Suggest to have a look at cocoon platform once.
I know you have mentioned that you cannot rely on 3rd party service but it is the easiest approach as far as i my analysis. Also it may be useful for someone who is struck with a similar issue to give it a shot.
My wife and I are currently working on a Phonegap Build app for distribution in BlackBerry World; however, whenever we try to run the app on a BlackBerry, we get the message "Error starting [TheApp]: Module ‘[TheApp]’ attempts to access a secure api."
We know that there are a lot of questions out there about this particular error and even some that pertain to Phonegap, but there don't seem to be any that answer the question from a Phonegap Build perspective or solve our particular problem. The most common answer seems to be that the application has not been signed or has not been signed properly, but this should not be case as we successfully uploaded out sigtool.csk and sigtool.db files to Phonegap Build and no error was raised when building for BlackBerry. Also the local installation of the 3 code signing files (RBB, RCR, RRT) that we did through the BlackBerry Eclipse plugin in order to obtain sigtool.csk and sigtool.db was successful. There are also a lot of answers out there pointing to the incompatibility of JDK 1.7 and Signature Tool, but we are using JDK 1.6 JRE 6, so this should not be the problem either. We also thought of requesting signing keys with access to the secure element from BlackBerry, but those keys seem to be for NFC only, and the app we made doesn't use any NFC, unless Phonegap Build causes it to call some NFC api for some reason.
Any help or suggestions would be greatly appreciated. We are using Phonegap v2.7.0 in Phonegap Build.
I am interested in developing an app for BlackBerry devices, and was wondering if they support the concept of demo or beta releases for their app developers? By this, I mean the ability to deploy a beta or demo version of my app to a limited/restricted audience, such as business partners, customers, external beta testers, etc. Nothing in their Testing and Deployment documentation indicates either way. Thanks in advance!
There isn't a built in beta process in App World for BlackBerry 10, but you can share the debug version of your app with your beta participants. When you create a debug token, you specify which PINs you want it to be valid for. The debug token will only install on a device with one of those PINs, and your app will only install on a device with your debug token on it. The token will only be valid for 30 days. You would have to deploy it with the command line tools and not App World.
This link on the BlackBerry Developer blog explains how to do it: http://devblog.blackberry.com/2012/04/debug-token/
It's for PlayBook, but the same process applies for BlackBerry 10 as well.
I actually don't know if RIM themselves have anything formal, but since I've always released BlackBerry apps on more than just the official App World store, I've used a beta testing system that is independent of RIM. Luckily, the legacy BlackBerry Java platform gives you the freedom to do this, free of charge. (Note that this answer is not about the upcoming BB10 platform!)
Over-the-Air (OTA) Installation
You can have your beta testers install your beta versions, Over-The-Air (OTA). Unlike iOS, for example, you aren't limited to a certain number of test devices, and you don't have to tell RIM what the unique identifiers of all the test devices are.
So, what I do is just put beta versions of my apps on a webserver, and send links to beta testers that allows them to download them. So, you are in control of who gets access. If you need security to limit the beta version to nobody except the official beta testers, then you are certainly free to add password protected logins to your webserver. That works the same way it would for any other secure web content.
If you do this (OTA), here are a few references:
http://www.blackberryinsight.com/2008/07/08/howto-setup-an-apache-webserver-to-deliver-blackberry-ota-applications/
Blackberry over the air installation
https://stackoverflow.com/a/10307074/119114
There are a couple steps to be aware of:
You normally just upload a .cod file to BlackBerry App World. If you want to deploy an app to your own webserver, you also need the .jad file. A JAD file is basically just a descriptor of the app, that can redirect a BlackBerry browser to the .cod file for installation. Your build process is already probably generating the .jad file for you, in the same output directory where it generates your .cod files.
You may need to configure your webserver to properly setup MIME types for files with a .jad extension. If you use Apache, then this is what you would put in your httpd.conf file:
AddType text/vnd.sun.j2me.app-descriptor jad
you may also need to add a MIME type definition for the .cod type, too
AddType application/vnd.rim.cod .cod
If you don't have access to the web server's httpd.conf file, but can place the JAD and COD in your own user directory, then you can configure the MIME types in a local .htaccess file.
Depending on your web server configuration, there may be a couple more steps necessary. Check the OTA links I provided above.
Desktop Installation
Another option is to simply email your beta versions to beta testers, and have them install on their devices using BlackBerry Desktop Software. I don't do this, but it is another way to accomplish the same thing. For this, you use the .cod file, and also the .alx file, which is also generated by the normal BlackBerry build process.
Note that some of the project properties that get put into the .alx or .jad files are things that you don't need to worry about if you only deploy the .cod file directly to BlackBerry App World. If you use one of the options (ALX for Desktop installation, or JAD for OTA), then I would recommend opening up the .alx or .jad file and just inspecting the values for correctness. They're normal text files, and most of the values should be self-explanatory. I believe all settings can be configured from inside your IDE. If you use the BlackBerry Eclipse plugin, right click on your project, select Properties and look around there.
Here are the official RIM docs on all your installation options
its not possible. When you publish your app in app world, it will be available to all users. So you cant set any special conditions like- available only to some people. Else make it in un published mode. Then only users with sandbox id can access your app.
Check the below link for BB 10 Cascades beta 3 release(Preferrable way of development in BB 10)
https://developer.blackberry.com/cascades/
For BB 10,they are plenty of ways for developing the applications ,check the below link
https://developer.blackberry.com/platforms/