The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
This happens if you forgot to change your build settings to Simulator. Unless you want to build to a device, in which case you should see the other answers.
ReplyDeleteI 'tripped' across my solution after 2 days...XCODE 4.0
ReplyDeleteI've just upgraded to XCode 4.0 and this code signing issue has been a stunning frustrastion. And I've been doing this for over a year various versions...so if you are having problems, you are not alone.
I have recertified, reprovisioned, drag and dropped, manually edit the project file, deleted PROVISIIONING paths, stopped/started XCODE, stopped started keychain, checked spelling, checked bundle ID's, check my birth certificate, the phase of the moon, and taught my dog morse code...none of it worked!!!!
--bottom line---
1. Goto Targets...Build Settings tab
2. Go to the Code Signing identity block
- Check Debug AND Distribution have the same code signing information
..in my case "IPhone Distribution:, dont let DEBUG be blank or not filled in.
If the Debug mode was not the same, it failed the Distribution mode as well...go figure. Hope that helps someone...
Check if you are building for device instead of simulator. Go to Xcode menu 'Project' -> 'Set Active SDK' change from 'Device' to 'Simulator'
ReplyDeleteUnder Xcode 4.1
Check your build settings for the project and your targets. For each check under 'Code Signing' check 'Code Signing Identity' and change over to 'Don't Code Sign'
This usually happens to me when I forget to change the company to match mine.
ReplyDeleteSelect the target under Groups & Files
Click the Get Info button
Choose the Properties tab
Under Identifier, make sure it says com.YOURREALCOMPANYNAME.APPNAME
When you create a new app, it usually says, "com.yourcompany". Change it to whatever you registered with, in my case com.DavidKanarek
I had the same problem. I'm very new to iphone development and it was my first time trying to load my program onto my iphone. The message is correct, you need to create a certificate in the keychain. The best walkthrough is here:
ReplyDeletehttp://developer.apple.com/ios/manage/overview/index.action
You of course need to have a developer account (need to have paid the $100 yearly fee).
I hope this helps.
In XCode 4.0 main workspace, at the top left side & just after the "Stop Button", there is scheme selector, click on it and change your scheme to IPhone Simulator. That's it
ReplyDeleteif you are just using the simulator and just upgraded then this solved the issue for me:
ReplyDeletego to menu->project-edit project setting.
find code signing section (you can type 'code' in the quick search)
in the code signing identity select 'any sdk' and set the value to 'Don't Code Sign'
When I had this problem, the issue was I did not have the private key necessary for the developer certificate to be valid.
ReplyDeleteThe solution was:
Have the developer who created the certificate export their private
key matching the iOS developer public key. see
http://developer.apple.com/ios/manage/certificates/team/howto.action
Open this file (Certificates.p12) on your machine (with KeyChain),
and enter the password the other developer used when exporting. It
is now imported into your KeyChain.
Now connect iOS device and rebuild targeting the iOS device.