[Help Wanted]: I have a Copilot subscription but can't get it running in Xcode #394
Comments
|
I looked at the instructions and saw that I hadn't completed the Github Copilot stage, even though I'm using Github Copilot in another editor (Cursor), so I completed these steps...
And tried again. It is still after my API key, which as I say, I have ready and waiting - I just need to know where to stick it 😉 |
|
The chat and prompt to code feature are not provided by GitHub Copilot, please read the next section in the README.md to setup a chat model. |
|
Hello! Thanks for the reply. I've read though that section and added my new Chat GPT API Key...
Unfortunately, I am still getting the same error when I try hit the Test button!
What am I doing wrong? This is so frustrating! |
|
It's not the same error. You just don't have access to GPT-4 yet. Please check the link in the error message https://help.openai.com/en/articles/7102672-how-can-i-access-gpt-4 for details |
|
This is from
Now do you understand why I am finding the error messages and comments like "You just don't have access to GPT-4 yet" very frustrating! Could you also tell me which of the Editor -> Copilot menu options I should use to access the Github Copilot facilities? |
|
ChatGPT Plus and the API thing are using different payment systems. From what I can see from the link, you have to use at least 1 USD before you can access GPT-4. GitHub Copilot fetches suggestions automatically when you type, you can use the accept suggestion command to accept it. You can find the meanings of the other commands in the README.md in the Feature section. |
|
I've just added $10 to my Chat GPT API account. And after having to delete my existing API key and adding a new one, I'm now getting somewhere in terms of the
However, I am still getting the error in the Chat facility...
Any ideas? |
|
Change the chat model in Feature - Chat to the new one. |
|
Thank you! I've got the Chat working now 😃 For the record, I've got a thirty year development career behind, so I don't think I am a stupid man, but I have to say that that process of getting it set up was much more difficult than it needed to be, with too many stages of the process relying on the user knowing things about Chat GPT in advance, that the docs don't tell you! To be fair, I would say that This afternoon, I will try to get the Github Copilot suggestions working. You may hear from me again 😉 |
|
I have same headache! To be able to use that Copilot for Xcode's chat and suggestions and get rid of that 'You didn't provide an API key ...' thing I have to buy separate Chat GPT API service in addition to my current Chat GPT 4 subscription? |
|
@emrdgrmnci Yes |
|
Thank you! So, I couldn't find the place for buying that additional ChatGPT API subscription. Can you guide me? |
|
@emrdgrmnci you can create a key in the the user settings page on openai.com |
|
@intitni I have already created and pasted API key into the Copilot for Xcode but still getting error "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys." |
|
@emrdgrmnci Please make sure that
If the issue persists, please post the screenshots of the two pages here. |
|
I'm a Chat GPT Plus subscriber and I'm able to use Chat GPT-4, but I tried with all Model Names (gpt-4, gpt-3,5 and so on..) but still getting that You didn't provide an API key... error 
|
|
@emrdgrmnci It looks like the error message is about insufficient quota, from the second screenshot. Chat GPT Plus and the API key are two different products using different billing system, please check that your billing information is correct on openai.com. |
|
Yes, I understood they are different and I have only Chat GPT Plus subscription for now. And, I'm still not able to find their another subscription and paying page for the API key. But, it's ridiculous to already setting API key through Chat GPT Plus subscription as well. In that case, what I understand is, I need to buy Chat GPT API subscription for getting it's API key which is other than Chat GPT Plus API key. |
|
I bought 6$ Chat GPT API subscription but still there's no luck! Also, I updated to Copilot for Xcode to version 0.27.1 and when I selected gpt-4-vision-preview as a Model Name, app is crashed at all. 
|
|
ok. finally, it worked! I was also added Codeium, and now I removed Codeium at all and Copilot started to work on. |
|
@emrdgrmnci Glad to hear that. Please send me the crash log if possible. You can find it from the Console.app. |
|
@intitni any idea on this? API Key added & test is a success in the host app settings. /run commands work but anything else does not work in the chat and gives this SSL error |
|
@varyP Sorry I have no idea if the test in the host app is a success.. Can you show me the chat model settings? |
|
|
@varyP I have updated the app to dump more information about the chat error. Please send a message in the chat panel and post the detailed error message here. https://drive.google.com/file/d/1jfsm1yzoiNTtcDL9ftXiH8JryrdDCmSC/view?usp=share_link |
|
Never mind, I figured it out. |
@wnykuang Actually there is a possible solution now, but not validated yet. Please keep an eye on this issue #380 You can also find a workaround solution at the very bottom of the issue. |
Before Reporting
Describe your issue
I have an active Github Copilot subscription and have been using it in VS Code and Cursor ( a VS Code clone). I've installed the Copilot for Xcode extension and the extra option appears at the foot of the
Editormenu in Xcode. So far, so good!When I try to use the extension I get this error...
I've been to the openai website and have generated a new API key, but I don't know how to add it to
Copilot for Xcode!Please can you or anyone reading this explain what I need to do? Thx!
I promise I've checked the issues (both open and closed) and the FAQs 😉
The text was updated successfully, but these errors were encountered: