in-house-distribution

background: we are getting iOS apps ( .ipa ) from external developers ( their apps may be submitted in the appstore ), and they want submit their apps in our internal store just by sending their .ipa to us we are installing apps using ota, by sending plist to our endusers, itms-services://?action=download-manifest&url=[PLIST_URL] i was using some GUI signing tools such as iResign, iOS App Resigner and AppResigner, injecting custom entitlements, injection App Transport Security into info.plist. and when i tried to install apps which are signed by these tools, install popup is shown correctly,

I want to inject my library into an existing enterprise app (ipa file). I found mach_inject, but thats only for MacOSX. Its possible because https://www.mocana.com is doing so. Please help. Any ideas, suggestion would be really helpful. It is not clear what you want to do but mach_inject is a way for user apps to interface with the MAC OS kernel using the Mach ports it is not relevant at all to IPAs which are essentially an archive - similar to zip or Tar. I suspect that based on what you are describing that you have a library that you want link edited / included in a user app but you don't

We have an iOS "In-House" app (distributed OTA) with a Distribution Provisioning Profile that, as you may know, expires in 1 year. We have gone through upgrading the profile and distribution pains last year, so we are familiar with the process of distributing the app with a new profile, but I want to ask some questions just for clarity. (We are currently 29 days away from expiration, so users are getting notified) Last year we thought that creating a NEW distribution provisioning profile with the same name as the expiring profile would overwrite the expiring profile. We were incorrect, it does

I put together a test app simply to test In-House distribution through our Enterprise Developer Account. Before archiving I checked that all signing settings looked good. Debug and Release show the correct provisioning profile and certificate. Then I ARCHIVE the app. The prompts show this: The correct cert and provisioning profile are shown. As the archive route continues I get to this screen: I am trying to understand why it says: Certificate "Unknown" and Profile "None" As I then try to distribute this through our MDM solution it never installs. My question is: when distributing in-house

I am trying to generate a Enterprise provisioning profile from an wildcard AppID but I am required to set a explicit AppID to generate the provisioning profile. One mobileprovision with a wildcard appID would be enough for our users to install our different applications and they are not forced to install a mobileprovision for each .ipa we develop. I am pretty sure this was possible in the past (around 2014) How could achieve this? Edit (Some more information added) I am able to create wildcard appIDs and with those appIDs I can generate development or ad-hoc provision profiles but not In House