iOS 10 Enterprise Deployment Failing - Authentication Required - ios

I have been working to solve this issue for about a month now and I'm finally turning to the good people of Stack Overflow for some assistance.
To make a long story short, our enterprise app provisioning profile expired, so I created a new profile, recompiled the app, and put the IPA and manifest.plist on our server. The issue is that the app refuses to actually download now. After the user clicks "Install" in the dialog on our website, they are bombarded with "Authentication Required" alerts, and no matter what is done, the app WILL NOT install. Per Apple's suggestion, I installed the IPA through Configurator 2 and it installs perfectly, so according to the documentation, this means the issue is not in the signing of the app. I have triple-checked to make sure everything in the manifest is 100% accurate, and the link to the manifest matches the example given in Apple's documentation. It fails in iOS 9 and iOS 10. It fails on my iPhone and iPad. IIS has the mime types setup correctly, and the server can ping Apple's servers required for Enterprise installations. I am no closer to solving this than I was a month ago. Has anybody had any issues with something similar to this? Any input at all will help tremendously. Thanks!

Related

Is it possible to distribute old app for ad-hoc use?

A friend commissioned an app to be developed some years ago but the developers went out of business. It was removed from the AppStore in 2015 but she still has it running on 4 devices (she's a university professor and uses it for her research). She now wants to put the app onto other devices and as an app developer myself I'm trying to help.
Is this possible? If so, how?
We've tried to contact the original developers but they are unable to find the source code. Rewriting is out of the question as she can't get funding for this until she can prove her results - for which she needs the app on more devices.
We have managed to get the original .ipa file off one of the existing devices. When I try to put it onto my iPhone using XCode Devices it does it, but when I try to run it it pops up asking for an appstore user name & password and won't go any further, even if I enter my own valid id. Perhaps it's contacting the appstore, finding that the app isn't on there any more and bombing out?
I've tried resigning the .app with an ad-hoc development one using my own developer id but when I try to install that on my iphone it starts doing it then says "The application could not be verified". I've also tried creating a dummy app with the same name and version number and following these instructions Resign IPA from development to enterprise but that doesn't work either. I've researched the error message to no avail. I am deleting the previous app each time I try to put a new one on.
Is there anything else I can try?

iOS certificate issue, invalid binary in application loader

My previous attempt to get some help on this topic, failed, so I'm retrying again.
I've built my PhoneGap application without any problems until our Apple Development subscription expired (I guess, all the certificates expired as well).
While renewing our Apple dev program at our company, my boss made me a new account and added me as admin to the company.
I tried remaking the certificates, and while all my builds worked over at PhoneGap Build (means, that the certificates are valid), while trying to submit our app via the Application Loader, I get a binary error, and can't go any further.
Upon browsing the forums I've found out that this could be an issue with the certificates, so I came here to ask, what could be wrong with my setup.
I have to specify, that before this expiration happened, all our builds were submitted by using a Macbook, that is no longer available, so I can't access the old keychain information.
Also, another important information: while struggling with this issue, I remade all the certificates and profiles. (the App ID remains the same, since i don't need to change anything there)
Another note: our application supports push notifications, so I added that to the App ID, and created 2 certificates: Apple Development iOS Push Services and Apple Push Services. (I don't know if I need both, but I followed a tutorial, and it worked perfectly until the recent happenings)
We couldn't release our app for weeks now, which is a huge problem right now, so any help would be appreciated.

IOS 10.1.1 Untrusted Enterprise Developer error

I downloaded a few apps from a third party website, and the apps are perfectly functional for the first couple days and then I get the Untrusted Enterprise Developer error again. I go into my General->Device management and attempt to trust the apps once more, but there is only an option to delete or verify apps. I notice that all of the apps are unverified, so when I attempt to verify the apps, it acts like its about verify-but nothing gets verified. By this point I can either press Verify apps again, or press Delete apps. If I press verify apps again same result. How do I get my apps running again?! Please help.!
I found that deleting the app via settings>general>device management>APP, then reinstalling, fixed the issue for me.

Offline iOS Enterprise App Deployment and provisioning

I have posted this question on SO since I think it is the most logical place to find people with a lot of experience with the iOS Enterprise program.
For my company, we are developing an in-house app. We would like to deploy this app with the minimum effort required on the user's side <1>, as it should be possible to quickly install it for incoming colleagues. Additionally, we can't always guarantee an up and running internet connection at install time <2>. The in-house app is to be downloaded on our premises from a webserver through wifi.
We are currently not enrolled in the enterprise program, as we're investigating whether or not our goals can be realized.
As for <1>, what we've found is that UDIDs are not necessary to include in the provisioning profile for enterprise deployment. What is needed, is a provisioning profile. Now, here are my first concrete questions:
are any additional steps necessary before a provisioning profile can be installed?
can the provisioning profile be embedded within the app as can be done for OTA betas? This would save a user the step of installing the profile.
For <2>, the following issues come to mind:
here it states that access is needed to ax.init.itunes.apple.com and ocsp.apple.com. The former for querying the max allowable GPRS app file size. It doesn't sound relevant when your goal is to distribute over wifi, but the page says "If this site isn’t reachable, installation may fail." so it does concern me a bit. The latter one seems less severe as it is stated that "Inability to contact or get a response from the OCSP server isn’t interpreted as a revocation", which means that it should be possible to not contact this server right away.
I'm assuming that I can use any URL scheme to point to a local server that provides the app bundle and that there are no restrictions on server configuration.
Summarizing the two: is it possible to install an in-house app from a local server without a functioning internet connection?
Thanks for the help; it's greatly appreciated. As I have no prior experience with Enterprise deployment, it is tough to be confident that I'm not missing out on the nitty gritty details in Apple's documentation.
Provisioning profile can be embedded.
Your employee's devices requires internet connection when they are downloading the app, so that the device can contact Apple servers you mentioned.

exporting your iOS app [duplicate]

This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How do you beta test an iphone app?
In Android you can export your app and get the .apk file that can be installed on any phone for testing. Is this possible with Xcode and iOS? I mean, I got assigned a job and I want to send my first demo.
My questions are the following:
1) What should I send? is there something similar with .apk file?
2) I know the procedure of publishing an app. If i just want to send it fro testing do I have to create a distribution profile and all that staff? The thing is the final app will not be published from my developer account but from the employee's. Is that a problem?
3) Does the person that I will send my file needs Xcode to run the app or something? I do not want to send him my code before he pays me.
You can send demo files of your apps by building them as "ADHOC" versions, but to do this you'll need the device identifiers (UUID's) of all the devices that you want to run your demo app on (in other words, this is the "distribution profile" you're asking about; you need to create a provisioning profile that gets included in the distributable app package). Here's some instructions that can help you get started.
The person can install your ADHOC app either through iTunes (syncing) or directly downloading & installing the ".ipa" file via their device's Safari browser. They don't need to use Xcode.
If your client has an iPhone, then use TestFlight - it makes the whole process of building for ad-hoc distribution much easier and a lot more efficient if you plan on sending multiple builds during development.
You can check them out on http://www.testflightapp.com - They have great getting-started docs and it only takes a few minutes to start the whole process - also, you don't need to install their SDK if you're just sending a pre-release build to somone.
To answer your questions more specifically:
The file that gets exported for iOS development is an .ipa
The .ipa must indeed be signed by an ad-hoc distribution certificate
If you use TestFlight, your client will be able to install your app
from an email - super simple!
Oh, and did I mention that it's completely free? :)
EDIT:
As mmc pointed out, you should check out the basics of Ad-Hoc distribution before using TestFlight, just for your own peace of mind. mmc recommended looking at How do you beta test an iphone app?, and an intro to TestFlight can be found in their tutorial base, here.

Resources