We are building an app that is deployed on a range of Customer iPads via AdHoc. Testflight works great with that, however our latest release refuses to install on iPads that have the latest version of iOS (5.1) installed - we previously deployed successfully to these iPads and their UDIDs are definitely in the mobile provisioning profile. Also the same build installs fine on an iPad that has an older version of iOS.
I already suggested to re-register the device as per the TestFlight FAQ article, but that didn't help. It seems to be a problem with iOS 5.1 - the user is asked to 'Contact the Developer' as the device does not have permissions.
Has something changed with iOS 5.1 re: the requirements for AdHoc deployment? We are building using the distribution profile, signing with the distribution certificate - and as I said, the app installs fine on iPads runnin older versions of iOS.
After installing iOS 5.1 I suddenly had similar problems with some of our testers.
Occasionally Mobile Safari's cache and cookies will become corrupted. Clearing them should resolve the issue.
Related
I'm working on a Xamarin iOS app.
I do not understand why, but using the same signing configuration (Automatic developer identity/Automatic provisioning profile), the app is deployed by VS and launches fine on my iPhone SE (2nd Gen) running iOS 16.1.1.
However it is deployed but is not trusted on my iPhone 13 running iOS 16.2.
Here is a screen capture that shows the infamous icon and app prefix with cloud and row pointing below.
If I try to run the app if tells me that it can't be verified (sorry this is in French):
I doubt that this problem comes from the app itself because it runs fine in the simulator and on one device with the same major OS version.
What is wrong here?
There are several ways to provision the iOS device,
Free provisioning for Xamarin.iOS apps through XCode. If you do not have a paid Apple developer account, you could use this way.
Manual provisioning for Xamarin.iOS. When generating a new provisioning file, remember to also include the device you want to deplay.
For more info, you could refer to Device provisioning for Xamarin.iOS.
I met a strange problem for iOS app, created in VS with Xamarin. When I created mobile provision in Apple developer account for testing app on real devices (AdHoc type, like Xamarin tutorial shows), I tried to install app to devices, added to provision. Installation was successful. After that I tried to install app to devices not added to provision. Installation was fault. But when I deleted all devices except 1 from provision and updated provision on my Mac nothing changed. I still can install app to devices, was in provision before.
Can anybody help with this problem?
I am developing IOS app for more than a year now. I have got apps in appstore which was built with xcode 4.6 and ios 6.1. They were doing well untill today when I need to submit an update to one of my app. While submitting the app,
I received:
This bundle is invalid . New app and app updates submitted to the app store must be build with xcode 5 and ios 7 sdk
After some research I found out that app make this compulsory to use xcode 5 for submission. My question is how should I properly upgrade the machine so that my keychain will remain intact(so are my certificates), I can still build apps for IOS 6 and work with my projects which were built using xcode 4.6.
My main concerns is certificates, I heard that xcode 5.0 needs Mountain Lion 10.8, if I will upgrade the os, keychain will be removed, how will recover the certificate signing requests, private key which identifies the certificates.
Upgrade only xCode 5 and set deployment target as ios 6.0 or 5.0 and develop app for compatible for iOS 7.
Apple, Inc. recently announced changes to its iOS application developer guidelines, requiring all mobile app submissions from iPad and iPhone app developers to be optimised for the iOS 7 operating system. All apps submitted to the iTunes App Store for review on or after February 1, 2014 must comply with the new guidelines, or they will be automatically rejected and denied distribution through Apple’s app marketplace.
source
We are currently adding some mobile applications built using Xamarin.iOS to our AirWatch MDM entreprise store. Unfortunately it doesn't behave as it should: we trigger the download on the device, it downloads the app but it doesn't install on the device. We checked the device logs and we seem to have an issue with profile or code signing.
Have other persons already used Xamarin.iOS with AirWatch MDM?
If yes, then how do you build your ipa file? Currently we build them for armv7+armv7s, with all assemblies linked, using LLVM and we build using AppStore mode.
When we build the app in AdHoc mode with UDIDs in the provisioning profile and add it through iTunes then it is installing and running fine.
Maybe it is necessary to go the AdHoc way, with this ipa file, with all UDIDs referenced, or, we should go the InHouse way? https://developer.apple.com/programs/ios/enterprise/
I haven't used AirWatch but I do currently use the Enterprise program (with ad-hoc builds) for internal company apps. I had the same issue when I tried using the wrong provisioning profile when signing the application.
Yes I have been using Xamarin with Airwatch for two years. I have no problem deploying applications to the field. I routinely provide updates for the programs and in most cases they are 100% deployed in a matter of a couple of days. The majority of the last forced deployment completed in less than 8 hours.
It sounds like it might be the way you are uploading the application into Airwatch. Are you requiring something that is not on the user's device such as a passcode?
I have about 240 IOS devices deployed with a mixture of OS (6.0 - 8). I do not build the apps for the AppStore. I can see where that could be an issue with the deployment methodology. When you deploy via IPA in Airwatch, it is assuming you are deploying enterprise applications. When I deploy an AppStore program I use the catalog and they install via the AppStore.
Our IPA's work either via iTunes or through Airwatch. Let me know if I can be of any further assistance.
Previously, I've been able to push my apps to my iPad from Xcode 4.2. I was building with Phonegap. The process is: register my App ID with the dev center, create a provision profile, and download it into my Xcode. Then from the drop down beside the play button in Xcode, I will see iPad as an option.
Now I'm building an iPhone app with Objective-C for the first time. I repeated the process above, but I don't see my iPad listed beside the play button. What is wrong?
Some ideas: i don't think my iPad has iOS 5. i think it still might be running iOS 4.x. Is that a possible reason?
If possible,
Update everything to the latest version (Mac, Xcode, iPad, etc.)
Provision a Device
If you are a team administrator, or if your team administrator has already configured the necessary credentials for you and your device, you can use the devices organizer to automatically download and apply the provisioning profile.
Alleviate the need to go to the iOS Provisioning Portal every time you want to add a device to your provisioning profile by using automatic provisioning.
To provision a device automatically for development . . .
Open the devices organizer.
Plug in your device.
Select the device, and click Use for Development.
Developing apps requires a provisioned device. The provisioning process sets up the required certificates and configuration data that Xcode needs to install your apps on your device.
Xcode 4 User Guide
It’s OK to support only the newest version of the OS.
Matt Gemmell - Latest Version