Ever seen this message before? "putpkt: write failed: Broken pipe."
I haven't had much luck with the submission process. I have made two versions of my game (one Lite version and one full version). Both were submitted one week ago. On Tuesday, I got a reply back that I needed to change the Lite version and that the full version crashed. This was strange, because both programs were tested before I sent them to the App Store and there's only one line of code that differs between them.
I resubmitted both programs on Wednesday and received an answer yesterday. Both program crashed this time. I was really careful when compiling and I made sure to check the build results as suggested by the documentation.
I then saw that the program sometimes pointed to 2.2 SDK and sometimes to 2.1 SDK, so I decided to start over with a new project and copy all the code to make sure I didn't have any discrepancies.
This time, everything made sense. Everything, including Frameworks, pointed to 2.2 and not 2.1. But then I got some really strange errors. In order to test that the distribution processed worked, I decided to make an ad hoc version of the program first. I then got this error:
putpkt: write failed: Broken pipe.
After some tweaking here and there, I finally changed the name of the game from "RaS" to "RollaStone". Then, it suddenly worked. I tried again to change it back to "RaS" and it failed. The Lite version is at the same time called "RaS Lite" and it works ok. I also tried to change the name to "Roll a Stone", but then it crashes again.
i've seen this message when i accidently unplug my iPhone while I am installing a program from XCode.... after I do this, the message appears everytime I try to build and run..
To fix it, I usually have to delete the program from the iphone, restart the iphone, and probably do a clean all targets from xcode...
Ever seen this message before? "putpkt: write failed: Broken pipe."
I haven't had much luck with the submission process. I have made two versions of my game (one Lite version and one full version). Both were submitted one week ago. On Tuesday, I got a reply back that I needed to change the Lite version and that the full version crashed. This was strange, because both programs were tested before I sent them to the App Store and there's only one line of code that differs between them.
I resubmitted both programs on Wednesday and received an answer yesterday. Both program crashed this time. I was really careful when compiling and I made sure to check the build results as suggested by the documentation.
I then saw that the program sometimes pointed to 2.2 SDK and sometimes to 2.1 SDK, so I decided to start over with a new project and copy all the code to make sure I didn't have any discrepancies.
This time, everything made sense. Everything, including Frameworks, pointed to 2.2 and not 2.1. But then I got some really strange errors. In order to test that the distribution processed worked, I decided to make an ad hoc version of the program first. I then got this error:
putpkt: write failed: Broken pipe.
After some tweaking here and there, I finally changed the name of the game from "RaS" to "RollaStone". Then, it suddenly worked. I tried again to change it back to "RaS" and it failed. The Lite version is at the same time called "RaS Lite" and it works ok. I also tried to change the name to "Roll a Stone", but then it crashes again.
Has anyone seen this error message before?
Hey wynodir...Did you manage to solve this ? I'm having the same problem...
Did anyone find a fix for this problem? for myself it started right after my Distribution certificate expired. I fixed all the certificate problems, then the app work in both Debug and ad-hoc configs, then all of a sudden started crashing each time i tried teh ad-hoc config, it installs fine but when the app start i get the : putpkt: write failed: Broken pipe. error
I cannot change the name of the app, as my app is already on app store and this is an update that i am testing out.
I was having this same problem, and the following solution worked for me. Some subsets of it did not work, but there may be less that is required.
a) quit Xcode (and therefor the GDB it is running)
b) unplug device
c) delete app from device (hold icon till x appears)
d) turn off device
e) turn on device
f) plug in device (if itunes wants to sync, let it finish)
g) launch Xcode
Solved! I have been able to reliably avoid this error completely:
1. Before doing a new build, always stop the debugger first.
2. Then stop the app on the device.
3. Only after doing the above 2 steps, then build and go.
That’s all you need. (No need to restart Xcode, restart device, delete app from device, etc.)
I had this issue while using internet at a public library.
They have a TOS screen you need to accept before using the internet. Since I had done it for my mac, but not for the iPhone, I had a tough time figuring out the reason.
Had a look at the console at the time of the crash and realized that it is some issue with the internet connection.
Accepted the TOS on the iPhone (through Safari) and joined the library network.
--> problem solved!!!!
Hope this helps!
(I wish I had taken care of notifying the user about lack of network connectivity, I guess thats the first thing I'll do for the app now
I had this issue while using internet at a public library.
They have a TOS screen you need to accept before using the internet. Since I had done it for my mac, but not for the iPhone, I had a tough time figuring out the reason.
Had a look at the console at the time of the crash and realized that it is some issue with the internet connection.
Accepted the TOS on the iPhone (through Safari) and joined the library network.
--> problem solved!!!!
Hope this helps!
(I wish I had taken care of notifying the user about lack of network connectivity, I guess thats the first thing I'll do for the app now
How do i this?(Accept TOS)? when I open safari i didn't see any acceptation page! I exam all of ablve step, but didn't solve
If you are able to access internet on your device (if you can go to a website on safari) then you wont come across a ToS screen.
My issue was very specific to my location and type of internet access. If you are testing it at home/office (with internet) then you are facing the problem for some other reason.
Solved! I have been able to reliably avoid this error completely:
1. Before doing a new build, always stop the debugger first.
2. Then stop the app on the device.
3. Only after doing the above 2 steps, then build and go.
That’s all you need. (No need to restart Xcode, restart device, delete app from device, etc.)
Forrest
PS. This is a bug in XCode.
your solution and upper solution didn't work, i can't install my with distribution or debugger, what i must do?
Ever seen this message before? "putpkt: write failed: Broken pipe."
I haven't had much luck with the submission process. I have made two versions of my game (one Lite version and one full version). Both were submitted one week ago. On Tuesday, I got a reply back that I needed to change the Lite version and that the full version crashed. This was strange, because both programs were tested before I sent them to the App Store and there's only one line of code that differs between them.
I resubmitted both programs on Wednesday and received an answer yesterday. Both program crashed this time. I was really careful when compiling and I made sure to check the build results as suggested by the documentation.
I then saw that the program sometimes pointed to 2.2 SDK and sometimes to 2.1 SDK, so I decided to start over with a new project and copy all the code to make sure I didn't have any discrepancies.
This time, everything made sense. Everything, including Frameworks, pointed to 2.2 and not 2.1. But then I got some really strange errors. In order to test that the distribution processed worked, I decided to make an ad hoc version of the program first. I then got this error:
putpkt: write failed: Broken pipe.
After some tweaking here and there, I finally changed the name of the game from "RaS" to "RollaStone". Then, it suddenly worked. I tried again to change it back to "RaS" and it failed. The Lite version is at the same time called "RaS Lite" and it works ok. I also tried to change the name to "Roll a Stone", but then it crashes again.
Has anyone seen this error message before?
the only time I see this is when I forget my app is debugging on the iPhone I unplugged it. other then that I never had a problem. The other thing is when strange error happens, I found it helpful to do a clean of the project and reset the simulator.