In AWS Device farm testing, how can fetch files from iOS device Documents, Library or tmp to customer artifact, what is the format ? I have tried Documents/Logs/file.log but its doesn't work
In AWS Device farm testing, how can fetch files from iOS device Documents, Library or tmp to customer artifact, what is the format ? I have tried Documents/Logs/file.log but its doesn't work
Related
Hello everyone I have my app successfully deployed on windows device, we already have a windows developer account. Now the client needs to test the app, how can we send him the app like ( apk files Android?)
One option would be to unlock your clients device as developer device and then install it via the Application Deployment tool. You would have to send him only the XAP file which you can find in your bin folder.
If this is no option you could create a beta test, here you would need the live ID of your customer. The app would run through the certification process so it isn't quite as easy as under Android.
I have created an .ipa file using Phonegap. For testing I uploaded the developer certificates and device UDID. Its working fine. Now, I want to distribute this apps using Application Loader. For this I uploaded the apple distributor certificate and distribute mobile provision file on the phonegap cloud and generated the .ipa file. When I tried this apps with iPhone 6.3.1, its giving me error: iTunes sync apps failed to install
Please help me to get out of this problem..
Are you trying to submit the app (you mentioned Application Loader which is used for submitting apps) or install it on devices for testing? I am assuming you are trying to install it on devices for testing.
If the app fails to install, check for one of these
The mobileprovision you are using has your device's UDID. Test apps can only be installed on devices whose UDID is included in the mobileprovision (unless you are distributing for enterprises)
The mobileprovision is installed on your device (try using a service like Testflight - you'll know whether your device has the necessary setup)
I am working on an iPhone application for a customer. After the development will be finished the application will be on the Apple Store, but meanwhile during its development, on a regular basis the customer wants to see and install the application on his own phone to check the current status of the development.
-I went to the provisioning portal registered my customer's device udid and added to my application's provisioning profile.
-I downloaded the provisioning profile and installed it.
-I then built the ipa and sent it to my customer.
SHouldn't this be enough?
The customer is experimenting a sync error. He can import the ipa inside itunes but at the end of the sync he receive this error alert on his iphone.I tested this ipa file on two other iphones and is working (both registered and one is ios 5.1 and the other 5.0.1)..Where should I check for misconfigurations?
I'm running the latest xcode version 4.3.1
Make sure you build with the distribution provision. I use a new Xcode build configuration for this (called Ad Hoc) and I make sure my archive build uses this new build configuration. The customer will need a copy of this distribution provision (which he double clicks), and you send him the ipa file. He drags this into his iTunes library and he is then able to install the app to his device.
Sometimes the provisioning profile needs to be installed on the device separately. I encountered this problem once with my team member who had Windows.
Just send your customer the profile and ask to install it on the device.
You may need iPhone Configuration Utility to install the profile on the device.
What are the possible ways to host iPhone build files (.ipa files) for enterprise edition, so that members of a particular organization can download that file?
Use AdHoc.
With Ad Hoc distribution you can share your application with up to 100
other iPad, iPhone, or iPod touch users. Through email or by posting
it to a website or server, users can download and install your app.
I already have an iPhone application (version 1.0) available in the App Store and am ready to submit a newer version (version 1.1). How do I test the new upgrade to make sure that the current sqlite database and property list files on the earlier version do not get deleted/overwritten etc? The new version assumes the old data in both the sqlite database and property lists remain.
Or better yet, is there a resource I can use to walk me through what to watch for when developing an application update?
The way we tackled this when we wanted to test our database upgrade code was to use ad hoc distribution.
We had our testers download the 1.0 app from iTunes and install it on their test devices.
Then we built an Ad Hoc distribution of the app using a configuration based on the Release config, and made sure that it had the same bundle identifier. As long as the bundle identifier is the same, the new app should overwrite the previous version.
We asked our testers to install the ad hoc build as they normally would, by dragging it into itunes and then syncing the device to simulate upgrading.
As far as I know, this is identical to the user downloading and installing an upgrade via the app store on the device itself.
As you'd expect, the documents folder should be left intact, leaving your database in place, and your app should be able to run its upgrade code to modify the database in the way you need.
Hope this helps :)
Test like so:
delete app from device.
install v1.0 app (or .ipa file) into iTunes
sync to device, iTunes will install the app
launch app on device, create and save data, etc.
quit app on device
install v1.1 app (or .ipa file) into iTunes; iTunes will ask to confirm replacing older version of the app.
sync to device, iTunes will update the app
launch app on device
test using existing data with new version of the app.