Code Sign Error with Xcode4.6 on JailBroken Device - iphone

I have jail broken device and would like to build the app on the jail broken device. I followed the following links to build the application
Bypassing code sign with xcode 4.5 for iOS6
How can I deploy an iPhone application from Xcode to a real iPhone device?
Test iOS app on device without apple developer program or jailbreak
Created the self signed certificate.
Modified the file /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/SDKSettings.plist
Modified CODE_SIGNING_REQUIRED to NO, ENTITLEMENTS_REQUIRED to NO in SDKSetting.plist file.
After that tried to build the application for the device I got the following error
Code Sign error: A valid provisioning profile matching the application's Identifier could not be found
What things I need to do to build an app on Xcode4.6 jail broken device?
I am building the app on MAC OS 10.8.2 using XCode 4.6 on iOS 6.1sdk

I just used 4.6 and I didn't have any trouble at all with this tutorial http://www.youtube.com/watch?v=h0JS0D2tXGY

Related

Enable Xcode debugging on jailbroken iOS 8.4 device

I want to develop with Xcode 6.4 on iOS 8.4 devices without a developer account.
I did Taig jailbreak on my iPad mini retina 2 and followed this guide:
How to debug iOS apps in a jailbroken device with xcode 6.2
I modified the SDKSettings.plist file with the following values:
ENTITLEMENTS_REQUIRED to YES
CODE_SIGNING_REQUIRED to NO
AD_HOC_CODE_SIGNING_ALLOWED to YES
I can install the app on the device but the debug does not work (the app crash on the device when launched from Xcode).
To enable the debug I add the Entitlements.plist file (with "Can be debugged" to "YES") to my project and trying to execute I get the following message:
"App installation failed
The application could not be verified."
I missed something?
Everyone has the debug working on iOS 8.4 with Xcode 6.4?
Thanks in advance
Try to add to the Entitlements.plist:
"application-identifier" and
string value: "$(AppIdentifierPrefix)$(CFBundleIdentifier)" (both without quotes).
If it does not work you can check the log (Apple iOS Device logging)
EDIT: I am able to run my app on iOs 8.4 with this scenario

Installing a TestFlight app on iOS iPhone Simulator - Registration Failed

I'm attempting to install a TestFlight app on XCode's iOS simulator using the iPhone simulator. The link to the TestFlight app takes me to a page that says "This device will need to be registered before it can install betas."
There is a friendly Register button. When I click the register button, it says "Registering Device" and then it takes me to the iPhone's General settings page. If I navigate back to the TestFlight page, it says "Registration Failed."
Does anyone know of a way to install a TestFlight app on the iPhone Simulator? Thanks.
The app you are trying to install is an app compiled for arm architecture, which is different from the simulator (the simulator is not an emulator). The simulator only runs x86 apps compiled for it. You will need to contact the developer of the application to send you the x86 binaries, and add them directly to the application directory of the iOS simulator. The directory (on Xcode 4.5 beta 4) is /Applications/Xcode45-DP4.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator5.1.sdk/Applications. Note that the simulator's sdk version has to match the version of iOS you are trying to use the simulator with.
If you need test your Release application
you can run your on a release build go to
->Product->Scheme -> Edit scheme-> in Run change debug to Release
in this you can check your release build in simulator
If I had to guess, I would presume that since the Simulator is not a valid device, it is not able to install the TestFlight Profiles onto the device, and therefore failing registration process (when you are directed to the iPhone's Settings, it tries to install a profile on your device).
May I ask why you are trying to install the app via the iPhone Simulator? If the app's code exists on GitHub, you can use the GitHub for Mac app to checkout the code, and XCode to compile the project and build it to the iOS Simulator. There should not really be any reason to have to install TestFlight on the iOS Simulator.

iPhone shows Question mark (in place of its icon) on connecting to the Mac

I have a (dev) build for the iPhone App & I need to install it on the iPhone that has been given to me.
Now, I have added the iPhone as a device to the provisioning profile for the App.
But, When I connected the iPhone to my mac, Question mark appears in place of its icon (in XCode > Windows > Organizer). And the options under the device are limited to Device Logs and Screenshots.
And on right hand side detail appears : "The version of iOS on “iPhone” does not match any of the versions of iOS supported for development with this installation of the iOS SDK. Please restore the device to a version of the OS listed below, or update to the latest version of the iOS SDK; which is available here." Which clearly means that ihave to update my iOS SDK for the XCode that I am using.
Is there any way to do, like without updating the XCode for latest iOS SDK, I can install the App to the iPhone provided to me ???
You just build the app, and locate the .ipa file from the products. Then drag the ipa file into itunes and then sync it to your device.
If you have got the Xcode project..then you would have to update Xcode..that is the only solution..
but if you got the build in .ipa format.then you should register your device on www.testflightapp.com and then transfer that ipa from there to your device..

Verizon iPhone Provisioning Problems

I upgraded to XCode 4 and a Verizon iPhone 4. After installing I am unable to sign and run anything on device. Yes I HAVE added it to the portal (using organizer and on the website). I've downloaded the certificates, and everything checks out.
I get the message: XCode cannot run using the selected device. No provisioned iOS devices are available. Connect an iOS device or choose an iOS simulator as the destination.
Could this be due to the Verizon iphone being 4.2.8 and not 4.3?
EDIT: Also, my ipad runs fine on it. Both devices show up in organizer, have the team provisioning certificates, and show up in the portal, etc...
-d
The fact that the iPhone is from Verizon has absolutely nothing to do with provisioning.
Try removing all of the certificates that are installed on the device currently, and try again. If the device is included in the certificates, then you should be good to go. Also ensure that you are running a supported iOS version on the device as set in your Xcode project.
The foremost thing you'll want to do is make sure your app's deployment target isn't iOS 4.3 and is instead something lower. (Base SDK should remain as Latest iOS.)

Can't install app on Device 3.1.2

I can install my app with the profile in my IOS4.0 device, but the same profile can't used to install on IOS 3.1.2 device.
My Xcode is SDK 3.2.3+IOS4(SDK 4).
BTW, i set my "Base SDK" = iPhone Device 4.0, "IPhone OS Deployment Target" is "iPhone OS 3.1.2".
The error info is "A valid provisioning profile for this executable was not found."
Thanks a lot.
Are you a member of the iOS Developer Program? You are not able to test on device until you sign up.
Yeah. I ve been there. I used to face this problem when I used to try and sync up .ipa file that I created out of sdk 4.0+ with an iOS 3.1.2 based device through iTunes. Apparently, iOS 3.1.2 devices have some bug (or maybe it is in the iTunes) that the profiles don't sync up along with the .ipa file in them automatically sometimes.
But before that, you have to ensure that the iOS 3.1.2 device is provisioned with the profile in the first place. If not, thats the problem. If it is, then in such cases, I used to drag and drop only the provisioning profile first into the iTunes, then do a sync with the device (Nothing will seem to happen in this sync. This is for installing the profile into the phone.). Then drag and drop the .ipa file into the iTunes and then perform another sync. That used to work for me.
If you are facing this problem with the .app, then too you should try above. That should work.