Post not yet marked as solved
Never mind; when I added .frame to the table it displays.
Post not yet marked as solved
When I repeatd the exact same process this afternoon (Saturday June 10) the Sonoma beta installed successfully.
Post not yet marked as solved
This problem has plagued me for a bunch of years also. Recently I found the following "workaround":
I would get the error if the config file for the project had a URL of the form:
url = ssh:userid@//hostname/path-to-project
however if I remove the userid from this string then Xcode will prompt me for the userid/password:
url = ssh://hostname/path-to-project
This also will work for cloning the project from within Xcode, just enter the string:
ssh://hostname/path-to-project
It might cause problems with issuing git commands from a command shell because it will use the current userid added to the string.
problem seems to be fixed now. Can download.
Post not yet marked as solved
thanks for the response! I did get it to work after adding a few more constraints - the main one being a trailing constraint on the bordered scroll view (containing the table view).
I tried a solution similar to that outlined by mattie; when logged in as the userid that shows the -1 error I edited a project's .git/config file and replaced the hostname for the "remote" server with its ip address (for me this was easy because the git server is in the same local network as my development machines). When I then opened the project in Xcode the git repository functions worked without errors. I then edited the config file again and changed the ip address back to the hostname and the Xcode git functions still worked!
I've had some success using the notes provided by guyton (thank you). I have 2 machines which were both exhibiting this problem. I followed the same procedure on both:
created key pair and exported the public key to the remote server successfully
verified that I can access remote using command line git clone
With Xcode not running:
(1) delete the IDESourceControlKnownSSHHostsDefaultsKey using defaults utility:
defaults delete com.apple.dt.xcode IDESourceControlKnownSSHHostsDefaultsKey
(2) REBOOT machine
(3) start Xcode and attempt to clone a project
On one machine this worked perfectly - Xcode showed the dialog for picking ssh key pair to use and then cloned the remote project as expected. All other projects again allow remote push, pull, etc.
However on the other machine, I still get the -1 error. I suspect it has something to do with ssh environment but do not really know how to troubleshoot the problem. Any suggestions would be appreciated.
I also tried with deleting the entire plist from preferences and rebooting but that also did not fix the problem.
One last thing I did was to create (on the machine that has the problem) a new user account. In that account:
create rsa key pair
export public key to server
start Xcode and clone project - this worked without any problems
Post not yet marked as solved
I've had some success using the notes provided by guyton. I have 2 machines which were both exhibiting this problem. I followed the same procedure on both:
created key pair and exported the public key to the remote server successfully
verified that I can access remote using command line git clone
With Xcode not running:
(1) delete the IDESourceControlKnownSSHHostsDefaultsKey using defaults utility:
defaults delete com.apple.dt.xcode IDESourceControlKnownSSHHostsDefaultsKey
(2) REBOOT machine
(3) start Xcode and attempt to clone a project
On one machine this worked perfectly - Xcode showed the dialog for picking ssh key pair to use and then cloned the remote project as expected. All other projects again allow remote push, pull, etc.
However on the other machine, I still get the -1 error. I suspect it has something to do with ssh environment but do not really know how to troubleshoot the problem. Any suggestions would be appreciated.
Still have problem with recently released Xcode 12.3
problem still occurs with Xcode 12.1;
I tried fix suggested by curtly42 (changing default branch name to master) but this had no effect on the problem for me.
to ehmjaysee: can you elaborate on what you did? What area of the Xcode preferences are you referring to? Not sure where to look for source control account information in the preferences (it's not in the source control general or git)?
thanks for any help
Post not yet marked as solved
Just an update; I was able to access a machine with Xcode 11 and performed the suggestions (copy class code from Xcode 11 and then disable ML Class code generation); it did build without error messages and worked properly.
However this still seems to me to be a bug in the Xcode 12 compiler for it to generate class wrapper code that has errors.
Post not yet marked as solved
thanks for the response with potential workaround. Unfortunately I do not have Xcode 11 around anymore as it was updated by install of Xcode 12. I guess I could re-download and install it alongside Xcode 12.
My own workaround was to simply access the external model file and compile and load it rather than including it in project. This seems to work fine. I did file a bug for this and received the following analysis in my feedback report:
"Investigation complete - Works as currently designed"
Extremely non-helpful.
(Also, I looked at project settings but do not see one for auto-generation of Core ML models)
Post not yet marked as solved
update on this issue: if I access the model by compiling and then loading it in the application that works; however getting prediction from compiled model is cumbersome because there is no wrapper class.
I guess I'll file a bug and see what happens.
For me it is easy to replicate the problem:
(1) Generate an image classifier with create ML tool in Xcode 12
(2) Create a simple Xcode project (such as a command line tool Swift project)
The project will compile and run
(3) Add the ML Model class from output of model generated in step (1) to the project
(4) Project now fails build process with the error given above
Post not yet marked as solved
thanks for the response; I had done the clean and updated recommended settings. In fact I created a new project and a new ML model and had the same problem. It seems that just including the model output from create ML without any references to it at all in the project code will cause the problem.
