I just cloned this repo from github and would like to have a play with it. However, in XCode, I keep getting the following error:
The identity '3rd Party Mac Developer Application' doesn't match any valid, non-expired certificate/private key pair in your keychains
It's worth noting that in my Build Settings, I've set the Code Signing Identity property to Don't Code Sign, but I'm still getting this error.
Has anyone ever encountered this, and if so, what did you do to fix it?
Thanks!
I have downloaded the project and noticed that there are 2 Xcode projects:
SpectttatorTest.xcodeproj,
Spectttator.xcodeproj.
The first one has set "Code Signing Identity" to "Don't Code Sign", but the second project (which is embedded in the first as a dependency) has set "Code Signing Identity" to "3rd Party Mac Developer Application".
After setting "Don't Code Sign" for the second project no code signing error occurred anymore.
Ater changing the setting, if you notice the same thing happening with your own projects, it may be time to get a new certificate. It's what I had to do last July.
EDIT:
If indeed that's what you have to do, this SO link contains an answer describing the procedure for moving forward.
Related
I'm following the instructions here: https://www.itwinjs.org/learning/tutorials/develop-web-viewer/ to create a sample web viewer app. The doc says to update variable IMJS_CONTEXT_ID which is not in the .env file and doesn't appear with "Show IDs" for my iModel (I have created a github issue for the doc already). I've tried updating the variable IMJS_ITWIN_ID instead with the "iTwin ID" from my iModel. When I start the app I get an error page "An Error Has Occurred: The user is unauthorized. Please provide valid authentication credentials". I have checked the variables IMJS_AUTH_CLIENT_CLIENT_ID, IMJS_AUTH_CLIENT_REDIRECT_URI, IMJS_AUTH_CLIENT_SCOPES, IMJS_ITWIN_ID, IMJS_IMODEL_ID and all appear to be correct. Is there something else I need to configure?
Sorry, the tutorial you're referring to is a bit outdated now. Have you taken a look at https://developer.bentley.com/tutorials/web-application-quick-start/?
In the new #itwin/web-viewer-react templates we renamed IMJS_CONTEXT_ID to IMJS_ITWIN_ID. We also made some changes to the required scopes, you'll need namely imodelaccess:read, imodels:read, and realitydata:read. Please make sure your auth client has the above scopes and you have access to the model. If you still have trouble, feel free to continue the discussion over at https://github.com/iTwin/itwinjs-core/discussions
I have my safari extension in the gallery.
Now I made few minor changes in my code and then resubmitted it for review (it takes a month to review, :( that is really a long time)
After almost a month, I received an email from safari , that my extension is rejected because of this Issue
Please strip the extended attributes (xattr -c path/to/extension.safariextension) and rebuild your Safari Extension package using the latest version of Safari.
I tried the above command but every time I face the same issue.
and also I am confused that if every time I update my code, I need to resubmit extension for review, then what is the use of this link:
https://developer.apple.com/library/archive/documentation/Tools/Conceptual/SafariExtensionGuide/UpdatingExtensions/UpdatingExtensions.html
also, when I was going through all this, I got an email from safari that my certificate (which is used in extension builder to create .extz file) is going to expire in a month
I created a new certificate and created a new extz file.
but don't know that do I need to resubmit my extension or just update it on webserver.
so basically I have 3 issues/ confusions
Do I need to resubmit extension everytime I update code or just updating extz on web server will work
what do I have to do for this:
"extension description within the Safari extension preference pane appears to be a placeholder"
Safari Extension certificate expires in a year, everyYear I need to resubmit extension or can update extz with new certificate on web server will work
Thanks in Advance
================update======================================
Submitting Extension removing extended attributes is actually resolved
by just running this command from MAC xattr -c path/to/extension.safariextension, and then rebuild and submit.
So, Question 2 is resolved , now I just want to clarify about other 2 parts of my question 1st and 3rd.
Had same issue with this placeholder -issue, fixed by adding/modifying proper Description in Information -section of Extension Builder.
I'm developing an open-source extension for Safari. In the future, I might disengage and hand the project off to someone else. How would that work, given that the extension is signed using my personal Apple ID?
So let's say that I develop and sign version 1, and that Alice develops version 2. Would I need to sign Alice's version 2 (and her version 3, 4, etc.)? Is there a way for me to say "Alice is allowed to sign her own updates to this extension"?
Or maybe it's not that complicated: Does Safari even check to see if the new version is signed by the same Apple ID that signed the previous version?
Apple's documentation for updating extensions just says that the update manifest needs to include a developer ID, but it says nothing about whether the new version's developer ID is compared against the old version's.
If your project has a domain name, create an email address on that domain, and an Apple ID attached to it.
When you want to hand off the project, hand off the email/apple id altogether.
Or just create now a 2nd Apple Id and see if you can sign your extension with it.
Hey I have a new machine on which I am installing my provisioning certificate and provisioning profile. When I set the code sing is show that No identities from the profile. I am doing it first time. I do not know why it is not showing the signing identity. Is it developer account issue or any thing else.
Thanks
Your question is a little bit unspecific, for people to help you. But lets give it a shot.
1.) Make sure the profisioning profiles are valid for your App (especiall look at the bundle identifier - the must match, or the profile must end with a '.*')
2.) In Xcode 5 goto Preferences / Accounts / View-Details and press the Sync button. If your profiles show up there it should work and they show up in the build settings. (Attention if you are still with Xcode 4, the profiles dialog is somewhre in the Organizer window)
If this brings you one step further, please mark question solved. IF further problems exist, create a more specific question.
I'm trying to put a simple app on windows store. I made a fail attempt once, I submitted an app which failed to pass WACK, eventually it failed on submission too. Even then, when I try to package an app with my developer account logged in, I get a performance launch error.
Even on a blank app. also right after I create package logged in, my app's package name and provider fields on appmanifest are changes too. app's package name changes to the first app I submitted, and the provider changes to I guess my developer account's key.
I deleted my failed submission on dashboard, deleted all the names I reserved, including the failed one. But even when I reserve a new name and package my app with that name, my package name still changes to the very first one and fails on wack.
BUT, when I create package of my app WITHOUT logging in, I mean without associate with windows store, I can package my app with the name I want and pass the WACK. I hope anyone can help me with this.
Edit: C# application.
I had this happen too, it seems like WACK got confused and kept trying to verify the wrong version. The following steps resolved it for me:
Uninstall the app from your development PC (as in, go to start page,
right click on the app and select uninstall).
Reboot the dev PC.
Select "Local Machine" and "Release".
Start debugging wait for it to
have started up completely and then stop debugging.
Pretty sure that only one or two of those steps are actually needed, but not sure which ones.
I'm not completely sure I understand your issue, but let me try...
First, what is the failure that you got when you submitted to the Store and when you ran the WACK? You mentioned a "performance launch error". If you are failing the performance test, check out this article for tips to help. Some examples:
Package content locally (or cache it) when possible, so you don’t have to pull resources from a network during launch.
Load and do only what you need on launch. You can load other data and do other work asynchronously in the background or when you actually need it.
Use a "dirty bit" when saving data on suspend, so you only save data that has changed. (Rather than re-serializing your app’s state if that data hasn’t changed, create a Boolean flag variable (or “dirty bit”) which signals that your data has been modified, and only re-serialize when the data has changed.)
Use bytecode caching if you are developing in JavaScript, so each JS file has bytecode created once and not every time the app launches. To enable this, make sure all JavaScript files are UTF8 encoded with a byte-order mark (BOM) and are statically referenced in the root of your HTML start page.
If this is not the error that the WACK and your Store certification is failing with, please see this blog post and the related blog posts that it links to, to see if your failure is covered there.
Secondly, your issue with associating your code with your reserved name in the Windows Store:
also right after I create package logged in, my app's package name and
provider fields on appmanifest are changes too.
This behavior is expected. When you associate your app package with the Windows Store, it will change the "Package name" and the publisher in your appxmanifest. But that's okay! The "Package name" is just what the Windows Store uses as an internal identifier for your app package, and the "Package display name" (right below it in the appxmanifest) is what your end users will see. Set the "Package display name" to what you want.