Is there any way I can distribute a "privileged" app prior to marketplace approval?
It's kinda hassle for me to "push" app to the device using Firefox OS Simulator every time I need to test it. Would it be great if I can just point my browser to app's html file and then it will automatically re-install the app? Just like what android *.apk does.
You cannot install a privileged app on a real device without the simulator dashboard (or app manager) if you didn't submit it to the marketplace first (and was approved). For security reasons, the application needs to be signed, so it's why you need to publish it to the marketplace.
Related
I am trying to transfer an app of mine into my company iTunesConnect account but are getting the error:
You can't transfer this app because of the following reasons:
Sandboxed Group Container
You can only transfer sandboxed apps that are not sharing a group container.
the thing is, my app isn't using the group container any more, it was in an older version but not the currently shipping version in the Mac App Store.
does anyone have any experience with how to go about transferring the app?
Even though my app wasn't currently using a group container (it had in the past) I couldn't transfer it. I had to re-upload as a new app losing all my reviews.. :(
It appears to be impossible. I got the following response from iTunes Connect Support (September 15, 2017):
I have reviewed your enquiry and found that once the app has the
entitlement included, an app transfer will not be possible, even if
you submit a new version without the entitlement. However, you can
transfer the app via the binary reassigned process.
By completing this process (a "binary transfer"), the app will effectively be a new and separate app on the Mac App Store. This might of course be very inconvenient, but there's not really anything to do about it, unless Apple changes the rules.
Is there a way to target Xbox device family specifically when creating a new UWP application? Thus making that application package unavailable for the other platforms, while potentially have a different package for other platforms?
Currently I'm trying to create a package for Xbox only by adding
<TargetDeviceFamily Name="Windows.Xbox" MinVersion="10.0.14000.0" MaxVersionTested="10.0.14000.0" />
to the package.appxmanifest. Unfortunately this gives permission error on uploading via the dev center:
Package acceptance validation error: The package *.appx targets the following Windows 10 device families for which you don't have permission(s): Windows.Xbox
I think this is the correct way to do it and that the permissions might be granted somewhen after the anniversary update? When will publishing be possible? Or is there another program you have to sign up to for being allowed to publish an Xbox only application / get the required permission?
Currently, Windows Store is not ready to accept XBOX app. As pnp0a03 mentioned, Microsoft will publish the new Dev Center feature and publish more details about publishing XBOX target app in Store, maybe later this month
Setting TargetDeviceFamily dependency is the right direction, the current available device families are Windows.Universal, Windows.Mobile, Windows.Desktop. Please waiting for the updates from Windows Store side.
I am building a SharePoint 2013 provider-hosted app using the high-trust model. This allows a customer to deploy the .app to their App Catalog and make it available to all SharePoint Sites. The provider-hosted portion of the app runs in an IIS box (cluster) which the customer also deploys (on-premise) with setup instructions and automated tools.
The .app file structure includes the application manifest - which specifies the precise endpoint where the provider-hosted portion resides, and also specifies whitelisted endpoints which the add-in can call. These are all specified by entering in URLs, hostnames, and port numbers into edit fields in Visual Studio in the 'Deploy App' form just before the .app file is built and digitally signed.
This seems to work just fine for a single app built by IT folks internally, if the org is small enough... but I really want to be able to distribute this solution to more than one customer. In order to do so, I would have to ask the customer for their respective endpoints, enter them into my build tools, and rebuild the .app for them. This just doesn't seem right... no customer wants to talk to the developer first and have a custom-built app. And why should they? No code is changing...
Upon investigation into the .app file format, it turns out it is really just a simple .zip file - and inside (voila!) there is the app manifest! Unfortunately, if you edit the app manifest and re-zip the file, the digital signature is broken, and the .app no longer works. (grrrr...)
What I want to do is simply reconfigure the app manifest to match the environment where it is deployed. This can happen programmatically during setup/installation time, or perhaps even just prior to download, but cannot be a process that involves developers typing into visual studio and pressing Rebuild. That simply won't scale.
Is there a tool that exists that can help with this problem? If not, does anyone have experience with the signing of .app files programmatically? I'm open to skinning this cat in any way possible.
This is a wild idea and not maybe even possible.
Create web ui, where clients enter their endpoints.
Have internal process that invokes MSBUILD/TFS to package app with endpoint
change app manifest with pre-build powershell
Then provide app via email or download?
http://www.sharepointconfig.com/2013/10/building-sharepoint-2013-apps-with-tfs-2013/
This is more of a workaround than a true answer - but would work:
For on-premise deployments of high-trust SharePoint 2013 apps - build the application with "known endpoints" - essentially hard-coded endpoints that can be deployed locally. Then instruct the customer to redirect those endpoints using DNS records or hosts file entries. In addition, the client would need to generate a local wildcard certificate signed by their own trusted root in order to satisfy the SharePoint 2013 app model requirements for appdomain and server-to-server communication.
This is by no means ideal, but for certain environments it might be the most practical approach. This also allows scaling for the IIS WebApp to occur at the customer-site, where it realistically belongs for a high-trust app.
This approach avoids the need to automate build tools and also avoids building a separate instance for every customer - both of which are somewhat undesirable. It might, for those reasons, be slightly less costly - but it also pushes some responsibility to the customer. Namely - hard-coding a DNS entry locally for machines in the topology.
I need a service application in Firefox OS which should start at boot time. I searched several sites but didn't get anything useful. Also I would like to know what all changes should be made in the manifest file and js file. Also the requirement of index.html file.
There is the Background Services, but it's not available yet, and tagged a certified app right now. So it's not possible at the moment.
The most relevant API that could act as 'service' is alarm API, which allow app to trigger itself periodically and do some stat checking. Calendar/Email App use that technique to pull new event/mail from internet.
Ref: http://tech.mozilla.com.tw/posts/2223
I'm investigating the possibility of utilizing my web host as a cruise control.net build server. If I have access to MsBuild or can deploy msBuild and run it, it would be great. I can not however find any resources that would tell me if cruise control supports being run as a web service or web app.
Is this type of deployment possible? If not could the UI (it's web-based I believe) control section sit on the web server and send requests to the actual build server?
CruiseControl requires it's own Windows service running in the background. Unless you can install services (not web services, but actual Windows services) on your host (which is unlikely unless you have a dedicated server), or just keep the EXE running until the end of time in debug mode, you won't be able to use CC.Net in this way.
It's better to keep this as part of your dev environment, anyway. You don't want the security risk involved with having that level of control available to anyone that manages to log in to the server.
I figured it out. This was very doable, just copying the web directory from Cc.net's install and editing a few config files.