I have iOS developer team and all of they want to install their app into the real device and I want to give them all a single provisioning profile so they need not to change the bundle id of the app. For example, there are two apps say helloWorld and myFirstApp and I want that both these app should use the same profile (without replacing each other).
I know we can create a developer profile having * bundle id which has this same features whatever I'm looking for. Now my question is how to create that profile? Please explain me in little bit more detail.
I know we can never submit an app with such profile i.e. we have to use separate profile for all the app but it can be done for development purpose.
There are two options.
First, if you have a limited set of devices that you need to install to that are known ahead of time, you can use the standard Ad Hoc distribution profile. This allows you to build on your local Mac to up to 100 devices that have to be defined in the profile ahead of time. This does not require an Enterprise account - so any Apple developer account can do this.
Second, if you need to distribute your test apps outside of your team, and the devices will change, Apple has an Enterprise Program (your company must have a DUNS number, I believe), that will allow you to create enterprise distributions that can be deployed on any device. Those builds still have a limited expiration on the provisioning profile and certificate, so they must be re-built / reinstalled occasionally. In general, this is the method used for broad distribution / beta tests.
For a single team to use a single provisioning profile, I would choose option 1, create the provisioning profile on Apples developer site with all of your devices, and then add all your developers to the team in the dev portal. Xcode 5/6 will take care of the rest for you if you go into preferences, and add their accounts to the "Accounts" tab.
In older versions of Xcode (4.x and before), you could have one developer create the provisioning profile, and certificates, then export out a .developerprofile from Organizer that would package up the certificate and .mobileprovision files needed to build to your team's devices.
Related
I am using Maximo anywhere 7.6.3 and wanted to know if we need an apple account to customize (i.e add new fields) to existing application. The customization guide of 7.6.2 says it is needed for building iphone applications, but then not sure if it is required for the latest version. The modifications that i made in dev. work as expected though.
in order to compile to IOS, you don't need a developer account, just XCODE and a MAC. In order to distribute the app via the app store, you would need a developer account.
IBM publishes out of the box Anywhere applications to both the Google Play and Apple app stores, so you can point them at your Anywhere server and deploy a lot of changes that way without the need for an Apple account.
If you want to make changes to the iOS apps like custom app icons, custom app names or baking in the server url and then distribute the app either publicly or within your organisation, then you will need an Apple developer/enterprise account.
I am BA and want to know what things a developer needs to have to build a website in Microsoft (it will be fully customized / partially customized online service selling a website, have price calculator based on N no. of various option user select and lot of other things around it and the admin panel to change rate, tax, etc. in it)
The website will have automated email, payment, forms, reporting, role & access, a different type of end users & a lot of calculation logic as well.
I am listing the thing we need to install as i can find the cost (especially hidden cost to develop a website).
I am representing Non-IT company (not in India), then do we need to buy the licence for all the Microsoft tools developer needs? If yes please mention tools we need to buy a licence for along with the tools list
Thanks in advance for replying.
This is a pretty broad question, but for the functionality that you are describing, here is a very basic web development setup:
Windows server to host the website (x2 for dev)
Database server and software (SQL goes well with .net) (x2 for dev)
Microsoft Visual Studio to install on a desktop device to build the actual website, assuming you are building in C#.NET or VB.NET
Of course, your second paragraph lists additional functionality that may require more hardware, software, and integrations(email servers, payment systems, etc.) depending on what you have or don't have.
All of this can be hosted in a cloud platform like azure, aws, or it can be done internally
We already have 2 Test Manager extension licenses which are assigned to Basic users who develop tests. We need to have an ability to run solely browser based testing in the VSTS by, let's say 10 users.
What is the cheapest option to accomplish that?
Can those users be Stakeholders or they have to have at least Basic access license?
Basic access level is required, so you need to buy basic access license for each user, also Test Manager extension license is required too.
I checked and only the Basic/VS access level is required for the users to be able to test the tests which were authored by somebody else. There is no need Test Extension in order to be able to test.
Team,
Can anyone clarify about "Development distribution profile" mentioned in Appium Site? Is it Developer Profile or Distribution Profile or it works on both profile?
PROVISIONING PROFILE
A valid iOS Development Distribution Certificate and Provisioning Profile are necessary to test on a real device. Your app will also need to be signed. You can find information about this in the Apple documentation.
http://appium.io/slate/en/master/?ruby#appium-on-real-ios-devices
Please refer the below link,
https://groups.google.com/forum/#!topic/appium-discuss/9GA4XdsnM4A
Comment by Anil Kumar on 29/11/2013
Build has to be signed with developer certificate/ profile (not distribution profile),
Thanks,
Ramesh
According to Apple (https://developer.apple.com/library/ios/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/UsingtheAutomationInstrument/UsingtheAutomationInstrument.html) you need to have your application signed with a development provisioning profile in order to be able to exercise your app via UIAutomation.
Since Appium uses UIAutomation, I understand that you need to have your app signed with a development provisioning profile to be able to write automated tests for it in Appium.
I am building a marketplace Meteor app but I am confused about the app architecture. I want to build front end user interface for marketplace, Customer dashboard, Vendor dashboard, admin user interface and meteor mobile apps for customers and vendors. I know Meteor bundle everything in client folder and send it to the client. My question is do I need to use same hosted Mongodb database and create separate Meteor apps for
App 1 Marketplace user interface and Customer dashboard.
APP 2 Vendor dashboard.
APP 3 Admin user interface
App 4 Meteor Mobile App for Customers
APP 5 Meteor Mobile App for Vendors
OR
Create a single Meteor App for everyone. but in that case app size will increase.
OR
Create separate Meteor apps and connect all other apps to APP 1 (Marketplace App) through DDP to share publications and methods.
Please help me decide best architecture.
Option 1:
I've done so using a single MongoDb instance. I currently have four apps connected to it. It works really well.
Make sure you use the oplog for instant updates across all the apps.
Some of the security benefits of this approach were unexpectedly nice. For example, allow and deny rules being created with only one type of user in mind for each app. If someone has access to admin.yoursite.com for example, the permissions allow all sort of things for admins, but for the client facing app, the permissions can be locked down to only allow editing of the few things that are required.
You can get pretty far with this approach, I recommend it.
Option 2:
I wouldn't recommend making a large app that does everything.
Option 3:
Not to say there is no benefit to that sort of approach, but "APP1" in this case should probably be some sort of event log, which each app can subscribe to the events of and write events to, and update their own databases. This is the most complex (and expensive) solution, and I wouldn't recommend it until you are trying to scale really large. If you are interested in this type of approach I recommend looking into Event Sourcing/CQRS.