This question is locked. New answers and comments are not allowed.
running on Win7 (64b)
I have uploaded and installed valid Developer and Provisioning files that 1) work at build.phonegap.com and 2) are validated by Graphite.
Howver I can not run on device inside the Graphite app.
I looked at my options and do not see any items in my iOS provisioning dropdown.
I am running on Windows but am not sure if this is the reason I can not compile and debug on local device.
Please see the attached image for additional information.
Thanks-
Don
I have uploaded and installed valid Developer and Provisioning files that 1) work at build.phonegap.com and 2) are validated by Graphite.
Howver I can not run on device inside the Graphite app.
I looked at my options and do not see any items in my iOS provisioning dropdown.
I am running on Windows but am not sure if this is the reason I can not compile and debug on local device.
Please see the attached image for additional information.
Thanks-
Don
4 Answers, 1 is accepted
0
Yavor
Top achievements
Rank 1
Rank 1
answered on 04 Jul 2012, 09:29 AM
Hi Don,
It appears that you have imported a password-protected developer profile, which is currently not supported in this release. Could you please try importing your developer profile again, but without a password?
It appears that you have imported a password-protected developer profile, which is currently not supported in this release. Could you please try importing your developer profile again, but without a password?
0
Don
Top achievements
Rank 2
Rank 2
answered on 05 Jul 2012, 05:04 PM
I did see that in your documentation and was afraid that was the problem.
Unfortunately this is a pre-existing certificate and Apple only allows a single Dev. Cert.
I would have to revoke and thereby invalidate all my provisioning files for any other applications in the process.
not a comforting thought.
Unfortunately this is a pre-existing certificate and Apple only allows a single Dev. Cert.
I would have to revoke and thereby invalidate all my provisioning files for any other applications in the process.
not a comforting thought.
0
Don
Top achievements
Rank 2
Rank 2
answered on 05 Jul 2012, 06:37 PM
yes - easily replaced and does not break any existing applications.
If the device already has access to the (existing) deployment package, it will continue to install.
new packages can then use this newly created Dev. Certificate (and associated ProvisioningProfile) without a problem.
Thank You.
If the device already has access to the (existing) deployment package, it will continue to install.
new packages can then use this newly created Dev. Certificate (and associated ProvisioningProfile) without a problem.
Thank You.
0
Yavor
Top achievements
Rank 1
Rank 1
answered on 05 Jul 2012, 06:46 PM
Don,
You shouldn't need to issue a new certificate - all you need to do is to export your certificate and private key from the Mac OS Keychain without specifying a password for the exported .p12 file.
You shouldn't need to issue a new certificate - all you need to do is to export your certificate and private key from the Mac OS Keychain without specifying a password for the exported .p12 file.