I have an app using CloudKit. After upgrading to iOS 9 it continued to work as it did previously with no issues. However, a couple days ago, I upgraded from Xcode 6 to 7. Xcode 7 broke some things visually...alignments, collectionview cell edge insets were changed, etc...definitely annoying, but it's probably some autolayout issues I needed to fix anyway. The real issue is beyond anything I've ever seen before. All of the sudden, my CK data will not get returned unless I'm connected to wifi AND a power source. At first I thought it had to be connected to the laptop and running from Xcode to the device. I tested it by disconnecting from the laptop and plugging into the wall and CK data was returned and CV cells got rendered. And whether or not it's connected to a power source, if I'm on cellular connection I just get the spinner (data loading) and it just sits there. And if it's running from Xcode, I don't see any logging happening either. But if i switch to wifi even while the app is running, then I see the logging of the CK results returned followed by the custom cell views being trigged and finally the cells get rendered on the device.
Just to be clear, I didn't make any coding changes around this happening...just upgraded to Xcode 7 (not the GM version). I did notice the below difference in info.plist when comparing in source control.
xcode 7:
CFBundleIdentifier
$(PRODUCT_BUNDLE_IDENTIFIER)
xcode 6:
CFBundleIdentifier
com.drivethruu.${PRODUCT_NAME:xxxxxxxxx}
I replaced the actual product name with the "xxxx..." just for this post in case it's something I shouldn't be showing publicly. I did use the xcode 6 value just to see if that was the issue and got the exact same behavior. Didn't make it worse, but didn't make it any better. Also, I've changed the deployment target to everything between iOS 7.1 - 9.0 and no differences.
Anyone experiencing anything like this? Any idea on how to solve this?
UPDATE: Downloaded Xcode 6.4, discarded changes in the storyboard and info.plist files and recompiled and all issues resolved, so it's definitely some issue with Xcode 7. Still running iOS 9...will need to find out why the issue is happening on with Xcode 7 since I'll need to have the app iOS 9 certified before submitting. May need to open a ticket with Apple.
Thank you!
Apple has changed the behavior of the qualityOfService setting and the way data is fetched. In my opinion this is a CloudKit bug. For more information see:
iOS 9 CloudKit: query does not return anything while connected to cellular network
Please also make a bug report of this at http://bugreport.apple.com
In Xcode 6.3, I got this error when trying to run an iOS project written in Swift on a real device.
App installation failed
could not write to the device.
I tried to clean the project and run again, but the same error occurs.
How can I fix this error?
Deleting the app on the device and running the project again works for me.
I did a Clean and installed my app successfully.
Product->Clean(Shift-Cmd-K)
I turned off the device and turned it on again after which I did not get such error.
OK, few things you should consider that could guide us to the problem, please check and post the answers:
is your project using capabilities? are they set correctly (should be all green)
did you try with a different project (something really simple)?
are you able to install apps from the App Store?
did you check the amount of free space left in the device?
if not, another suggestion will be using exception breakpoint, there is someone that posted an explanation how to setup it, do it and post the logs
App installation failed
I hope it helps you
Got this problem twice in one week on complete different devices.
One device had no more storage left, after deleting some apps the project installed perfectly.
The other device was fixed after rebooting the device
If you are using a free developer account you may need to uninstall some other apps you have signed.
For me it was the provisioning profile - I used distribution instead of development
My issue was an embedded framework.
Go to "Build Phases" -> "Embed Frameworks" -> Check "Copy only when installing", and it got rid of the issue for me.
For me the following did not work on iOS 11 beta 10, XCode 9 beta 6:
Restart the device
Deleting the app from the device
No symlinks were in the project
There was plenty of storage available
Deleted Derived Data and voilá, it worked again
in my project this problem happened because there was a folder with symbolic link. I removed that folder and it worked properly.
This error has many potential root causes, as can be seen by the large variety of suggested answers. The best approach to troubleshooting app installation issues like this one is usually to inspect the console of the iOS device itself, as that'll often provide much more specific error messages. In Xcode open the 'Devices and Simulators' window and take a peek at the logs of the device where your app is being installed.
In my case, the "Could not write to the device" error was being caused by this:
Feb 27 10:54:58 iPhone-7-110 installd(MobileSystemServices)[46] : 0x16f92f000 -[MIBundle _validateWithError:]: 38: Failed to load Info.plist from bundle at path /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ebmR6U/extracted/SampleApp.app/Frameworks/SomeFramework.framework
Which clearly hints at what's actually going on. I had forgotten to set an Info.plist file for my dynamic framework target (used by the app).
I had a symlink in my project to a file outside of the project. When I deleted this symlink the install worked fine.
I was having the same error, i just deleted the project and fixed!
Go to Window -> Project and right click, and remove from projects!
In the case of your device have an app with the same bundle identifier, Xcode will throw this error.
Try to delete potential app with the same bundle identifier.
Check your provision profile, maybe you are using the app store provision profile like me. I had to change the app store provision profile to development, now it's working.
Tried all of the above answers: Deleting the app, clearing storage space, cleaning the project...
What finally worked was bumping the build number in info.plist (General > Build)
For anyone still facing this Issue:
There are so many reasons and this is one of them as it happened to me.
I've faced the same problem and I was connected wirelessly and If you are trying to install the application in wireless connecting mode (connected through same network), this might probably because of poor internet connection. Check your internet connection and try again, it works fine...
Get rid of embedded libraries, dont' just throw it in there make sure it is embedded indeed.
If you use your iPhone for debug, maybe, because your iPhone's storage space is less than your debug App.
Clean your iPhone --- Real machine
Clean your Mac --- Simulator
This looks like another time waster courtesy of Apple's amazingly high class development team. On iOS11 Xcode9 (pick your beta, any one works) this will happen randomly. Appears to be more frequent if you dare to switch apps while compiling. Just build again and stare at xcode - it'll work the second time without fail in my experience.
Apparently this message can also appear if the system clock of device where the app is being installed is too far away from the current time.
I was doing some tests with date formatters by changing my iPhone's system clock and eventually forgot to reset it to the current time. Afterwards it always displayed the same message ("could not write to the device.") whenever I attempted to run the app. Simply resetting the clock in Settings fixed the issue.
Nothing helped me. I followed the below steps,
Clean derived data folder
Quit Xcode and disconnect device
Restart Macbook
Restart Device
Open Xcode
Clean and run the project
Finally I got it working!!
I am facing same issue then solved out follow this step and now its working.
Deleting the app from the device
Try to install another application
Remove derived data in X-code.
Restart X-Code then clean and build the project then run.
It's still not working then
Remove un-used application
Restart the device and check the Available and capacity in settings
Again app run in device
I hope its worked, enjoy it.
My problem was I had initially installed the app using a different set of developer credentials on the device. Deleting the app from the device fixed it.
Maybe it can be due to the following error App installation failed. No code signature found. In my case after a project clean the description of the error switched to "No code signature found".
In my case I created two frameworks but they had the same bundle identifier.
This caused the installation to fail, so double check the frameworks bundle identifiers and make sure that each of them have a unique bundle identifier.
Environment: Xcode 10
sometime this error occurs due to wrong certificate.Please make sure your certificate.
Also this the error shown if your machine running Xcode is low on space.
Once I had to load an App Container for debugging purposes into an iPad, said operation failed because the container was too big (18 GB) for this device (16 GB minus the OS), so that I desisted the task and completly forgot about it, leaving the failed installation in the device. Later, when trying to install a different application this error appeared, once I got rid of the failed app installation, everything got back to normal.
Basically, your Ipad might be low in storage.
One reason this can happen is if your app bundle contains broken symlinks.
Any ideas? It was working an hour ago, now everything is dead and the status page says all is good
try disconnecting any devices you have connected.
I just tried everything SO suggested, reboots, wifi restart, iphone hotspot, nothing helped, so I unplugged my device and suddenly xcode connected and teams were fetched.
Just to say, I've had this issue a few times in the past week.
I'm using Xcode 6.4 with OS X Yosemite (v10.10.2), and from time to time, it just hangs on the "Fetching list of teams" message.
Most of the time, it works fine, but then it'll start to time-out, or throw an error like this:
The solution: reboot my MacBook. It fixes the issue every time.
It's odd. All other applications can happily access the internet, but for just this one part of Xcode, it seems unable to fetch the data it needs, and only a reboot sorts it out. I didn't have this issue before.
And it's hard to identify if this is an issue with Xcode 6.4 or OS X Yosemite, and Xcode demanded that I upgrade to the latest OS before it'd let me update to 6.4 (so I could actually debug an issue with iOS 8.2) so both updates happened on the same 1-2 days.
Bug ? Bug ? Did I say "bug" ? Course not. It's an undocumented feature.
(Sigh.)
Five hours later
I've just had the same issue again...
However, this time, I turned off WiFi on my MacBook, then turned Wifi back on again.
And the problem went away.
It (almost instantly) managed to load the list of (two) teams that I belong to.
Hope this helps.
I know that is late for answer but maybe my solution could help others.
IT ALWAYS WORKS FOR ME:
Step 1:
Go to Xcode --> preferences --> accounts
Step 2:
Select your team name and click in view details
Step 3:
Click in
Final step:
Go to Window --> Organizer and try to upload again your app :D
i resolved this by deleting my accounts and setting them up again. none of the solutions above worked.
This worked for me by disconnecting from my WiFi then reconnecting.
Quit xcode and simulator. Open organizer and click on Upload again. This worked for me.
I tried adding the account again and also reconnected the wifi but it did not work for me but quitting xcode did.
Actually I think it is an issue at Apples server.
I just got through once 30 minutes ago but had set the wrong build version and now I get the same error again. I think we have to wait.
i had same issue when i had changed my account's password.
first time, i just authorized it through new passoword. (it's not working)
and then.
remove all appstore accounts on xcode
add same account with new password.
it work.
Just keep retrying, I suspect the issue is on apple's server side and retry attempts will eventually get through.
You should get the list back within a second or two, so you can cancel the attempt and retry quickly rather than wait for the timeout.
Restarting wifi seems to help some people but not others.
Check your internet connection.
Upgrade XCode, 7.2 fixed this for me.
I noticed that I had some connection problems.
The ethernet cable was not fully plugged in.
On wifi, make sure you have a good signal.
I had same issue, and I resolved it.
I got hint from #jab11
I have external storage for TimeMachine. Around a week ago TimeMachine start to fail backup my disk.
I plugged out external storage not properly When it happens.
So, try like below.
Plug in your external storage if you have one.
Check your partition's health. (In my case, I erased partition which is causing fail to backup)
open Xcode Organiser, then upload your binary.
I hope this help.
For me, I removed all accounts in XCode -> Preference -> Accounts and ADD account again, then it's working well.
I'm getting "Archive Submission Failed with Errors" and I have ran out of ideas on how to upload my app to the App Store successfully. Note that this isn't a new app. I'm just uploading a new version and this is the first time I've ever gotten these errors.
See link for screenshot: http://postimg.org/image/hesdsr167/
Using:
Xcode 6.1
OSX Yosemite
Application Loader 3.0
Titanium SDK 3.4.1
Have tried these but none of them helped:
Opened all the ports and IP Addresses
Used Wireless Hotspots, Ethernet and Wifi
Took down firewalls
Searched around the Apple Developer Member Center for anything I needed to do
I googled
I just need to know at least one of these:
A temporary or permanent solution
A workaround
What causes this issue?
Try telnet sgr203.apple.com 44001 to make sure if this issue from XCode or your MAC.
if this issue from your mac try to use VPN may help.
If telnet worked, try to remove XCode cache.
I am developing an ios app that doesn't need an internet connection. I'm using phonegap and jquery-mobile. I'd like to develop offline, but XCode gets stuck with a status saying 'Attaching to iosproj' (iosproj is my project name). After that I cannot stop the stuck task, and have to force-quit XCode. With an internet connection however, everything works just fine. Grateful for any clues.
Edit: XCode seems to install the app fine without a network, but it gets stuck before/durimg receiving the deviceready event.
Update 1: The app runs fine on the simulator with or without the n/w. It is purely the XCode-iOS simulator interaction.
Update 2: When using phonegap (Apache cordova), there's an easy work-around to work offline. Once the project has been built and installed (with a n/w), all subsequent updates to html/js/css/img can be made directly to the www directory in the simulator's Library (under your app folder, in ~/Library/Application Support/iPhone Simulator/6.0/Applications).
The Simulator itself attempts to make an Internet connection to Apple as it launches. In particular, the itunesstored process attempts to connect to ax.init.itunes.apple.com and phobos.apple.com.
[That information comes from LittleSnitch. You would be well advised to install LittleSnitch so that you can be sure of exactly what connection is being attempted here. No one - certainly no developer - should be without it.]
If you find this troublesome (that is, if the connection failure is causing you to be unable to run your app in the Simulator at all) you should file a bug report with Apple. However, I've had no difficulty with this, so perhaps this an Xcode bug. I'd suggest first updating to Xcode 4.5.2 in case it is fixed there.