When you install the MSI Installer, mostly the license agreement dialog will pop up,
Like this one.
https://winscp.net/eng/data/media/screenshots/installer_license.png
I converted the MSI installer to MSIX package format. I used the MSIX packaging tool. However, when I install the MSIX the license agreement doesn't show.
Is there a way to show the license agreement in the MSIX package?
With the introduction of AppX(now called MSIX) packages, back in Windows 8, Microsoft released new guidelines for application configuration.
For all apps installed through an AppX/MSIX package, the user configurations will take place the first time the app is launched by the user. This means the installation UI can no longer be customized to gather user input (or display info like the EULA) and execute your own code to prepare the app before the first launch.
Microsoft recommends for all this to be done from inside your app, decoupling the install phase from the initial configuration of the app.
For enterprise deployment, were end-users usually expected their apps to be pre-configured and ready to work with, the IT departments will be able to use MSIX modification packages to include next to the app the additional configurations required (eg. a license file, default homepage in a browser, and so on etc.).
Subscribe
Related
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.
I have come across various articles explaining how you can build and archive an iOS application using the command line tools packaged with xcode.
Is it possible to use the tools to validate and distribute the application to the appstore?
Edit following comment: I am looking to avoid using the GUI as I have multiple similar apps, so I'm looking to script the update process to make it faster (less manual).
You're looking for Transporter. It's included inside Application Loader, but there's now documentation on how to use it separately: (emphasis mine)
You can now use Transporter, Apple's command-line delivery tool, to deliver localized App Store metadata in bulk, including screenshots, rights and pricing, and more. Transporter can also find metadata for your existing apps so you can see how to correctly format the XML. To learn more about using Transporter and providing metadata, download the Transporter User Guide and the App Metadata Specification from the Manage Your Apps module in iTunes Connect.
Source: Apple News and Announcements for Developers; Aug 22, 2013
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/
I am trying to install mediastreamvalidator, mediastreamsegmenter, mediafilesegmenter tools for my mac machine version 10.6.8.
As mentioned in below link about downloading required tools for development of Apple specified Http Live Server.
https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/StreamingMediaGuide/UsingHTTPLiveStreaming/UsingHTTPLiveStreaming.html
As above article says:
The tools are frequently updated, so you should download the current
version of the HTTP Live Streaming Tools from the Apple Developer
website. You can access them if you are a member of the iPhone
Developer Program. One way to navigate to the tools is to log onto
connect.apple.com, then click iPhone under the Downloads heading.
After logging in to site connect.apple.com with Mac OSX developer credentials,
under download heading there is no tab named iPhone, i am unable to find this link.
If these tools are stored else where can some one please provide me the updated link?
I need these command lines for developing HLS server.
As I read on Apple web site, Mac OSX version 10.6 and above have these applications pr-installed and we don't need to install them using dgm files, but on my max machine i have only mediastreamsegmenter command line tools not all of them.
Can some one please provide me a link to download these command line tools or provide information on how to get these applications installed on my mac.
As mentioned by Stuart, you must be a member of the iPhone Developer Program in order to access these tools via the http://connect.apple.com link provided in the official documentation. More specifically, you must be a paid member. This fact caused me to lose several hours searching for the tools as I was a member of the iPhone Developer Program, but my annual membership had lapsed and the tools were consequently no longer available to me. What really got me was that the tools were still unavailable within the first few hours of renewing my membership. It took approximately 12 - 24 hours after I paid to renew my membership for them to show up in the list. Hope this helps someone down the road!
They seem to be well-hidden for whatever reason, but after a few wild goose chases, I found them.
You can start at the public-facing streaming page: https://developer.apple.com/streaming/
There is a "Downloads" link along the side. You'll be prompted to sign in to your Developer account, and then finally you get the actual download page here:
https://developer.apple.com/download/more/?=http%20live%20streaming%20tools
Here is a copy make from lastest version of HTTP Live Streaming Tools on ADC.
https://github.com/creeveliu/HTTPLiveStreamingTools
Download:
$ git clone https://github.com/creeveliu/HTTPLiveStreamingTools
To install it, you just need to double-click the StreamingTools.pkg and follow the instructions.
Once installed you will have these tools
/usr/local/bin/mediastreamsegmenter
/usr/local/bin/mediafilesegmenter
/usr/local/bin/mediasubtitlesegmenter
/usr/local/bin/variantplaylistcreator
/usr/local/bin/mediastreamvalidator
/usr/local/bin/hlsreport.py
/usr/local/bin/id3taggenerator
I have written an application that injects some menu items in other BlackBerry applications (for example a "bookmark this page" menu item in the BlackBerry browser). I have configured the application to be run automatically at startup (of the device) so when the device starts, the menu items are installed in the other applications.
However, I would also like to have my application started directly after installation (via OTA), so the menu items are directly available to the user. Is there a way to accomplish this without having the user to reboot the device or manually start the application after installation?
Autostart applications should run
automatically after they have been
installed. What could have happened
is the application tried to autostart,
but didn't have the permissions to do
what it wanted and failed with a
ControlledAccessException. Often this
can be seen as the application failing
to start, but in fact it did start but
just wasn't allowed to do what it
tried to do.
Check the event log on the BlackBerry
(alt+lglg). You should see an entry
for your application being started
after it was installed.
Mark Sohm BlackBerry Development
Advisor www.BlackBerryDeveloper.com
BB Support Community Forums :Can we automatically run the application after install