We've successfully been distributing our app to beta testers via Wireless Ad-Hoc (using BetaBuilder) for some time now. However, some users (whose UDIDs are correct and added to the provisioning profile) get a "Unable To Download" "Done/Retry" error. We've got the process working for some - what could be causing these users to have this problem? iOS version & time-added-to-the-provisioning-profile don't appear to be relevant variables...
Are they using iPhone 3G and you built your app for armv7 only, perhaps?
We ended up solving the problem (without figuring out why it worked), by using BetaBuilder. We automated the process by using the ruby version, which we had to modify to get it all to work. The automated, shinier version is available at https://github.com/dts/betabuilder .
Related
I believe this is a duplicate question, but examining the others I could not find my problem exactly.
I have developed a flutter app and I intend to publish it. So I rented a virtual Mac, loaded the project in XCode and tested it on a simulator. Everything worked fine.
I have an Apple Developer Account, Certificates, registered an iPhone, etc., but it seems that I have to physically connect the device to the computer to be able to run it on the iPhone. No way to do that remotely (I'm in Brazil and the virtual Machine in NY).
XCode tells me to plug in the device so it can register it (but I have registered it already in the developer's site).
I thought it would be possible to generate some kind of executable to download to my iPhone, but it appears that is note the case.
Is there any other way I can do that?
Maybe I can skip this step and try to publish the app, because it is the same project as an Android app already tested and published in Play Store.
The answer is yes, the modern answer is probably TestFlight. But this has always been possible using OTA downloads. To do this, archive your app, create an OTA manifest and put this on a web server somewhere. Then you can download the app straight to your phone (assuming it's signed with the correct provisioning profile and all that). We used to do this a lot before TestFlight came along.
This question and
this article are somewhat related to what you want to do
I was having trouble to test without an iphone what I did is register this device on my account https://messapps.com/wp-content/uploads/2016/08/udid.png and so far I could build the app for iOS.
Some days back i had few problems regarding the version updates from iOS 4.0 to 6.0 . The entire database was cleaned when the new version was installed .
Is there any way I can test version update before submitting to apple ?
I tested version updates via
Hockey
AdHoc build installed via iPhone configuration utility.
Is there any other way i can test the things so i can be sure that the update will not have any problems?
You can test it via TestFlight service. It's a great tool and I use it often to test my updates.
On a fresh phone (or a phone that does not have your app on it), download the current version of the app from the App Store. Setup all the necessary data, create values in your database, etc. Then update your app in the phone via adhoc release or TestFlight. The key point is to have the most up-to-date public version of your app first.
Try out Crashlytics. It provides instant and detailed crash reports, right down the line # at which a problem occurred.
It negligible in size (a few hundred KB), but even works on release distributions! That means even if you miss a few bugs, you will be notified instantly the moment a crash occurs, rather than having to wait for the useless Apple Crash Reports to be published.
Hope that helps you out a bit.
today my app update it has been released in the store, when updated or downloaded for the first time the app immediately crash on start.
I've tested the app on simulator and on device (the same where I've installed the update from the store) and I never experienced this problem.
My update it has been submitted with Organizer after the archiving, in the Distribute section.
Apple do not perform these types of controls before to release an app?
Anyone experienced a similar problem? I have no idea what could be the cause..
Thank you, Stefano.
Here's the best way to test a production build without deploying to the store:
Set your build Scheme to "iOS Device"
Do an Archive build
Select your archive and click Distribute
Choose "Save for Enterprise or Ad-Hoc Deployment"
Pick your code signing cert
After saving the ipa file, use Apple's iPhone Configuration Utility(*) to install it on your device
You should always perform two tests:
installing on a blank device after uninstalling your app *and any profiles in Settings -> General -> Profiles"
installing over the top of the previous version of your app, to make sure any files/preferences/etc are properly converted to the new format
(*) the iPhone Configuration Utility is mostly used for enterprise app deployment, but it's also useful for developers and is available as a free download for mac and windows at support.apple.com. You can also use iTunes instead, but it's convoluted.
As for why your app is crashing? No idea... it could be anything. Standard debugging advice applies.
The issue is related to the Framework. I had this exact error. It wasn't a case of logic as it was crashing before the AppDelegate was even called and my usage of NSMetadataQuery was much later in the life cycle than that.
It turns out that weak linking the Foundation framework was required.
Problem was solved by changing (under the Project Info in Xcode) the dependency option of the Foundation.framework from required to optional. Check for any such frameworks.
Try deleting any old versions of the app you have on your device, and reinstall. Also try on a different device, maybe with a different apple id to your developer account.
This happened to our app also, and apparently, other apps too.
Apple is aware of the problem and is currently working on a solution.
see this article:
http://techcrunch.com/2012/07/05/apple-responds-to-app-crashing-issues-has-a-dedicated-team-working-on-a-fix/
If you are using core data & you have updated database in your latest version without versioning core data in that case app crashes on launch after update.
I am developing an application and i want to distribute it via over the air (which is introduced in iOS4 for enterprise apps).
I am able to send my app via OTA successfully, but i am facing a problem while upgrading the app.
I am using the same bundle identifier for the app upgradation and i am just changing the version of the app before building the application.
But, if I install the updated app on the device using OTA, it is upgrading the application but it is not retaining the data. [my app contains some downloaded pdf files which i am storing in NSCachedDirectory]. I am able to see the archived data in upgaraded app but the files which i have written to NSCachedDirectory i am not able to see.
I have tried using NSDocumentsDirectory as well, but i am getting the same result.
can anyone please help me in this.
Why don't you use the amazing www.testflightapp.com to help you?
It works pretty well, keeps data for upgrades, and you can use it together with iVersion, so you don't need to send emails to update your users.
Does anyone have any idea on how to perform over-the-air, deployment of an iPhone app?
Apple's document say that enterprise applications can be distributed OTA, but don't describe , how to go about it.
Any ideas??
Thanks in advance.
I guess when I asked this question, wireless app distribution was not supported. But it is supported since iOS 4.0. In case anyone stumbles upon this question...check out http://developer.apple.com/library/ios/#featuredarticles/FA_Wireless_Enterprise_App_Distribution/Introduction/Introduction.html
Also you can do testing of this feature using http://www.diawi.com/
I didn't even know Over the Air was official for so long now! Anyway, first OTA service I've met was TestFlight, which is very much like that diawi you've pointed.
And here I'll quote this great guide I've found about AdHoc OTA with XCode:
If you’ve been through the distribution process of an Ad Hoc application, you can appreciate the challenges of getting a build installed on someone’s device. From the differences of working with users on Windows versus Mac machines, to explaining how to import an Ad Hoc provisioning file and the associated build into iTunes, this process is anything but a walk in the park.
(...) deploying Ad Hoc builds over-the-air, where users simply point the Safari web-browser (on their iPhone) to a link and tap to install the provisioning file and associated application.
Just to highlight the distinct advantage of deploying over the air.