I am trying this program called Monaca to replace phonegap, and I am getting some errors I need help on. I am getting two errors: 1.) Certificate not Registered, and 2.) Provisioning Profile not registered. How do I fix these?
It may be because iOS Build Setings is not set up.
Please check the following documentation
Configure iOS Build Settings
https://docs.monaca.io/en/products_guide/monaca_ide/build/ios/build_ios/#configure-ios-build-settings
Related
For almost a week i'm getting this weird error when i'm trying to run the app on my idevice.
the error is that:
error launching remote program: failed to get the task for process 10492
It's important to say that I get this message on Xcode, the app quites on the idevice, but right after I can run it by clicking on the app icon and it works just fine with the latest updates.
what seems to be the problem?
Thanks alot!
The problem is that you have set the build configuration in Release mode, and installing the application in device through Xcode. If you want to debug the app, then you should go to Edit scheme, and choose Debug mode. Also, make sure, you have a developer profile, and that you are building with that developer profile. Then, when you try to install the app through Xcode, you will see the app getting installed. Hope that helps!
GDB is having trouble attaching to the device process. Have you tried restarting the device?
If this is a permanent issue and you have an Entitlements.plist file have a look at this.
Please check your certificates. If you are signing with distribution certificate then you will not able to debug. To debug you have to have provision certificate
Hope this will help
When I am installing my app on device this error is coming..
I am searching on net since yesterday found many tips and also applied but it fruitless.
Please guide me what to do ?
Give the valid code sign identity of your corresponding device in your xcode project(i.e) valid provisioning profile.
Verify the following things,
1.Login to your developer account, and in the provisioning portal confirm that the corresponding device is added.
2.Have you install the provisional file into your device?
3.Check your build settings that you have choose the correct code sign identity.
My development machine suddenly decided to stop installing to my device this morning, with the codesign process giving the error "no identify found".
I checked my keychain and my developer certificate is there, valid until 2012.
The only links I've found in google talk about developing on a jailbroken phone, which I don't have.
Does anyone know how to fix this issue?
In the build settings for the "target" try reselecting the code signing identity. This often happens when working with more than one developer or if you recently added devices to the provisioning profile.
If any of your Provisioning Profiles expired, update them. If this is not the case, go to your project settings, there you should be able to find the codesign and a bunch of other useful stuff. Change it to the correct one, not the "iphonedeveloper" - the one that has your name in it!
I am trying to use iPhoneDistribution...
When I do Build, I get the error Code Sign error: Provisioning profile 'XX-YY-ZZ' can't be found ...
How do I fix this?
What/ WHere is that XX-YY-ZZ ?
From my side, I have verified the App ID and used it in Info.plist as well as under Configuration > Identifier
What should I do now?
Please help me...I have tried all possible fixes on this and referred the Apple docs as well...I am totally confused and feel helpless now.
In your Project settings for the Build, make sure that the Release configuration is using the (correct) Distribution profile and that the Debug configuration is using the (correct) Developer profile.
I know this has been asked before but tried everything and no luck. Trying to upload my binaries using Application Loader and getting the above error.
Some interesting things for my case:
I accidentally have a space in my App name. Would this cause the code signing to fail?
Looked in the build log and the last entry is * Warning: Defaulting to the standard codesign tool. Could this be the issue causing the problem? If so how do I solve it.
Behind a corporate firewall. I have access to the net but certain ports may be closed. Could this affect it?
Tried everything except revoking all the certificates mainly because I've just created them a few hours ago.
EDIT: OK, I've recreated the entire project, I've revoked all my certificates and recreated them and installed them, I've exported the last version from subversion to make sure subversion is not affecting it, used command line tool to compress it, made the target codesign the correct profile, made the project codesign both default and the distribution profile, tried a different net connection to make sure its not the firewall.
As you can see I've tried everything I can find and the stupid thing still wont work.
Any help?
Cheers
K, This is incredibly annoying. After doing everything as I said in the question and doing some things twice decided to try the Application Loader on someone else's computer. Worked first time, didn't skip a beat.
Strange thing is I have the current Xcode (which I assume is where Application Loader comes from) and the other computer is running an old one. Perhaps the current one is broken?
I had the same issue using XCode4. Turns out I needed to Edit the Scheme and specify that the Build Configuration for Archive was to the be the one for the one associated with the Distribution Provisioning Profile - in my case "App Store".
If you're having the same problem, that may be something to check.
At the project level you want to set your code signing identity, BUT LEAVE THE PROVISIONING PROFILE TO DEFAULT.
Then at the target level you have to set both the code signing identity and the provisioning profile.
If you fail to do that the package will be signed but not interpreted correctly by itunes connect.
I too had this problem, until I realized there's a different way to upload the apps now.
My 'release' Apps build as Archives
If you open the organizer and select 'Archives' at the top, there are 'Validate', 'Share', and 'Submit' buttons in the header info for your app.
Clicking on 'Validate' added my code signing information to the app (after logging in with the appropriate developer login)
Clicking on 'Submit' ran me through the same questions the Application Loader used to ask and uploaded the app without problems. (again after signing in with the appropriate developer information)
Apparently when I updated to xcode 4, it just didn't remove the old application loader.
Rudiger has worked around his problem by updating to the latest version of Xcode, but for others experiencing the error "Application failed codesign verification", see Apple's published list of potential causes at the following URL "How do I resolve the error: Application failed codesign verification?"