I developed an app for iPad that is being used by one person (never posted to the app store) it was delivered an ad hoc.
It's for personal, non-commercial use. The person is getting (of course) a 'certificate expiration' warning as the cert expires in a few weeks. Is there a way to get around that for an ad hoc app - without using using an enterprise developer account? We only have 1 user - but its important that the app continue working for him. Do we need to create a new cert, rebuild the app and send him a new IPA? Any good ideas to get around this?
You don't need to rebuild the app, just create a new IPA from your existing archive using the new certificate.
I would imagine asking Apple would be a good place to start. At least you will know if you can do so legitimately before trying other work arounds
https://developer.apple.com/contact/#technical
Related
My iOS app (registered with 'Apple Enterprise Development Program) certificate is expired yesterday.
I've renewed it today but still my existing app is not working in iPhone device.
I've gone through several questions/answers on Stackover Flow and I found this (iOS Enterprise Deployment / Expiration) useful but it's three years old. And there so many changes have been made by Apple Inc.
My question is:
Do I need to create a new build (IPA) and share it to all users again?
or Is there any way to reactivate existing app without updating?
(Un)fortunately - There is no way to swap the code signature on the fly since it could have been heavily exploited.
I guess you do not need to make any new build, just resign the existing IPA with a renewed certificate.
If updating the app for all the users is a bigger issue for you, you can check if MDM-based solution can be applied - https://support.apple.com/business
Using MDM you can manage multiple devices at once, so reinstalling the app shouldn't take much time.
im having a big doubt here, and i couldn't find any answer over the internet.
We develop multiple ios apps, under phonegap build, apps are similiar, just logo image change and some internal parameters.
In the process of publish one app, we generate an ios certificate for distribution, then generate the mp , and register the app on pushwoosh.
Now we get adviced than no more certificates are avaible to distribution for ios, so the only way to continue doing this is to use a same distribution certificate for multiple apps.
Is this possible, considering we are using pushwoosh for pushes?
Thanks in advance
A push certificate cannot be used for more than one app.
Every app has a unique app id and push certificates are for one specific app id only.
Distribution certificates are not linked to an app, there is one per Apple account, why are you even trying to generate and use more than one?
Maybe you are confusing a distribution certificate with a distribution profile, a distribution profile is linked to a specific app.You should defiantly have multiple distribution profiles.
I'm looking for some clarification on developing for a single iPad. I have an app in the app store, however I want to make my own app for personal use that won't be submitted to the app store.
Is it possible for me to develop the app and get a certificate to "test" the app on my iPad, and just keep it on? I don't want to have to pay $299 for an enterprise account to publish private apps for a single iPad to use the app!
I've had a read about and I'm probably more confused now than I was before!
Any help appreciated.
Thanks,
Gary
If you enter the iOS Developer Program (99$ a year), you will be able to do what you mention: you will be able to generate a certificate and a provisioning profile and install the app on your device (actually, up to 100 devices).
The only thing is that you will need to create a new certificate/provisioning profile and rebuild/reinstall your app when the certificate expries.
No matter how you do it, you will always have to sign your app to be able to run it on a device.
All Provisioning Profiles expire, except the ones for the App Store (which you can't use without publishing your App in the App Store). So paying $299 for an Enterprise Account wouldn't even help you in this case.
However, if you want to run the App only on this single device, you could consider jailbreaking it. This would allow unsigned apps to run.
So I took over an existing iOS app from a client, that is currently available for public use through the App Store. When I was given the project in xcode, I noticed that all provisioning profiles associated with the app had expired and all were under the name of the previous developer.
So, I added myself as a developer and joined the team and code signed the development copy under my credentials. I created a new ad hoc provisioning profile for testing, and released a version through TestFlight to some registered devices. No problems. The app is greenlighted to go live.
Can someone please help me out with the release process from this point on? Do I create a third new provisioning profile for App Store release, and tie it to the code signing in XCode? Is this going to be problematic considering the version that is live now is under completely different (expired) profiles from a different developer? Is there some alternative way I need to do it through Apple? I'm trying to be super cautious here... if for some reason I release the app and its crashing because of some step I didnt take by accident, the poop will hit the fan.
You're going to have to release it under a new name on the App Store and forfeit all the ratings and reviews. Apple won't let you swap developer profiles on an existing app.
Other developers may disagree, but it looks like a huge PITA. See here
Transferring ownership of an iPhone app on the app store
The official answer seems to be NO
I didn't interpret the question as regarding change of ownership of an app.
I read the question as: I've inherited maintenance of an app and we'll want to submit an update as the same seller.
In this case, you can generate your own certificates and distribution profiles, and you can then build and submit the app.
I have done this numerous times. That is, I have inherited responsibility for an app that I did not necessarily craft originally. I easily created new signing and provisioning credentials, appropriate for the app the be submitted as the seller (not me) on their behalf.
And for what it's worth, the App Store Distribution profile is necessary, but only used when the app is submitted, so Apple can ensure that it is coming from a developer that has the right to submit it. (Remember, these profiles are signed with the same certificates used to sign your app package.) If that Distribution profile should expire or change, it has no bearing on an app already in the App Store.
I have been working on a productivity app for 5 members of a company. I installed the app onto the iPads myself before sending them out. Now how do I send updated versions of the app to them?
The Apple site says ad hoc distribution can be done by email or from a web server but so far I can't find anything that explains HOW the app gets installed onto the iPad. Has anyone done this or knows how it is done? I figure some action on the part of the end user is needed which maybe a sticking point...
I'm correct in thinking that the app will run until the provisioning profile on the device expires and then be useless right?
Thanks,
Steve
Normally when you distribute applications via the ad hoc method, no application artwork is displayed when the user looks at your application inside the iTunes interface. However, if you place a copy of the 512×512-pixel PNG of your icon in your application bundle and name it iTunesArtwork without any file extension, this will be used by iTunes.
To deploy your application to your users via the ad hoc method, you need to create a distribution certificate, register any devices you plan to use, and create an ad hoc provisioning profile in the iPhone Developer Program Portal.
I haven't tried this yet, but bookmarked it because it looks interesting: http://www.readwriteweb.com/mobile/2010/12/apple-best-kept-secret-how-to-do-ad-hoc-installs.php
Hope this helps!
You can distribute the ad hoc build along with the provisioning profile that contains the users UDID via email, website, however you want. The tester simply drops the certificate and app onto iTunes and syncs.
If the provisioning profile expires for the user, simply generate a new one and distribute it along with the new build of the app.
If you're using a CI server, I have a quick slide deck and some supporting files for my system, which uses Hudson to automate the build process, as well as deploy the app for OTA intallation. End result is when I commit something to SVN, my clients get an email a few minutes later with a link that directly installs the new app on their phone.
If you don't have that infrastructure set up (or aren't looking to take it on as a project), I've been hearing great things about http://testflightapp.com/, although I can't say I've used them myself.