From organizer window i can copy document directory data. But in some apps i noticed that
it is locked and cant access documents directory.How can i lock the application from accessing
documents directory via organizer.
I suppose you can access documents directory of applications that are signed with provisioning profile installed on your computer. Imo it is a handy feature for developer purposes. However it is disabled for applications downloaded from appstore so why should you worry about it?
Related
I've been reading and working through https://developer.apple.com/legacy/library/documentation/ToolsLanguages/Conceptual/YourFirstAppStoreSubmission/TestYourApponManyDevicesandiOSVersions/TestYourApponManyDevicesandiOSVersions.html, right up until the point where it says to drag the *.mobileprovision to iTunes, and it says, "Double-click the app archive (the file with the .ipa extension)."
I am presently unable to find a program of my own having a file with a .ipa extension, and therefore unable AFAICT to run my app on an iOS device yet.
The documentation I was reading is legacy documentation, but I didn't notice a link to anything newer.
I have several things in place now, including a Testing_.*mobileprovision dragged into iTunes, but I am having trouble identifying the last step(s) to get my app to run on my machine.
What can I do next to get the app to run on my machine?
Thank you,
You have to export the app using Xcode Organizer, Archives, Distribute, Save for Enterprise or Ad Hoc Depoloyment. Sign it with your Ad hoc profile. Then you will have an ipa to install.
I created an sqlite file[or any file] in documents directory in ios device.If i removed the app (delete) from the device this file stays or get removed?
The sandbox of an application deletes automatically when you delete the app. It happens in both your device and in iOS simulator.
Documents directory allows you to store files and subdirectories your app creates or may need, for example a database.
Your application works in a sandbox environment. When you delete the application in simulator or device, the directory that was created by application is deleted and so do the files residing in it.
When you reset your simulator you can find the deleted files in the trash.
I have created a Provisioning Profile and an .ipa for my application. I had to send this to my client who uses Windows machines. I am aware of how to add the .ipa files in MAC machines but when it comes to Windows machine, I am not able to find the App section in the left side bar of iTunes Window. SO i am not able to drag and drop the provisioning profile and the .ipa file into itunes from windows machine. Can someone please help me on how to get out of this?
Have your client download a free app off of the App Store, maybe not having any applications in the target library makes iTunes think it shouldn't show that item in the menu.
I'm also thinking that you can turn on/off individual menu items inside the iTunes preferences, so maybe check there?
I have created an ad hoc archive and a .ipa file for the application I am trying to distribute. I have also created a distributing provisioning profile with the UDIDs of the devices that I plan on distributing my application to. When I drag the .ipa and .mobileprovision files into iTunes and try to sync the application to the device, an error message on the phone pops up reading "'myapp' failed to install". By the way, I have a standard iOS developer's license ($99 per year) and am using Xcode version 4.2.1. I am pretty new to the developer program, so please try to keep your answers as simple as possible. Let me know if you need any extra information. Thank you!
I had the exact same issue. My issue was simple to fix. Check your Code Signing Identities for Project & Target in your project Build Settings. Mine were pointing to my Development Profile.
The Code Signing Identities need to point to the Ad hoc Distribution Profile that you created.
Make this change and then recreate the Archive and .ipa file. I then deleted the old App in iTunes, and then dragged the .ipa file onto the iTunes icon (Windows). Then I was able to use iTunes to install the App successfully.
My problem seemed to be Xcode. I had multiple copies of the Ad_Hoc profile with different expirations (all valid) and a few with different names from the days. I deleted them all and the app still failed to install, but I noticed all the Ad_Hoc profiles had been resurrected by iTunes. Tried it several times and including deleting them from the Organizer, but they always resurrected (reappeared installed on the device). Finally I drug out a copy of the supposedly extinct iPhone Configuration utility and used it to delete the app and all Ad_Hoc profiles. Then tried to install just the profile. That got it down to 2. Finally got all deleted and got iTunes to install the right profile. Still took 2 more attempts for iTunes to finally install my archive file!
Check this .
Don't need to drag both .ipa and Provisioning Profile.
Just Drag the .IPA File Follow Further steps as you.
Set install owner param in Xcode project / Deployment to the name you specified in apple dev license. I set both install owner and alternative install owner and Install Group and Alternative Install Group to my name which the 100% exactly as in my apple development license.
And the error was gone.
I was having a similar issue where my project was stored on a secondary NTFS drive. After moving the project over to my desktop [aka MacOS Extended (Journaled) drive], I was able to load the ipa file via itunes.
Another point: If the store version of the app installed on your device (or a version deployed another provision), you have to remove it from your device before installing the ad-hoc version.
I solved the issue by not trying to sync with iTunes but instead to sync it within Xcode (from the window->devices menu)
I've had a query about developing an app for members of an association and I can't determine from the Enterprise Deployment guide if this is an appropriate method for deploying the app.
Members own their own devices, so can an enterprise app be deployed while allowing the users to continue to use their own Appstore logins?
At any point, do the devices have to be physically connected to a machine running iTunes that is owned by the association or can a provisioning profile be distributed via the web or email? I see that profiles found in certain directories (e.g., ~/Library/MobileDevice/Provisioning Profiles/) will be automatically installed, so can the profiles and the app simply be emailed to members?
The Enterprise Deployment guide contains a lot of instructions on locking down the device. Can this be ignored?
I've had a query about developing an app for members of an association and
I can't determine from the Enterprise
Deployment guide if this is an
appropriate method for deploying the
app.
Sounds right for the type of deployment you're talking about. Just be aware if you're have the enterprise developer account you won't be able to do App store deployment with the same account.
Members own their own devices, so can
an enterprise app be deployed while
allowing the users to continue to use
their own Appstore logins?
Yes, Appstore apps and enterprise apps can coexist on the same device.
At any point, do the devices have to
be physically connected to a machine
running iTunes that is owned by the
association or can a provisioning
profile be distributed via the web or
email? I see that profiles found in
certain directories (e.g.,
~/Library/MobileDevice/Provisioning
Profiles/) will be automatically
installed, so can the profiles and the
app simply be emailed to members?
You can get the app binary and profile to the members anyway you like. Snailmail a CD... stick a USB drive on a pigeon... As long as they have access to the iTunes they sync their devices with, they'll be able to install your app.
The Enterprise Deployment guide
contains a lot of instructions on
locking down the device. Can this be
ignored?
Not sure which guide you're referring to. Please include link.
You need the devices UDID which is included in the provisioning profile for the app, that allows that device to run the app