This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
doesn't build due to account issues? #2
Comments
Could you try signing in to your own team? You can select a team by clicking on where it says "None" to the right of "Team" and selecting a team. |
Tried that before none.
…Sent from my iPhone
On Aug 13, 2021, at 6:10 PM, Ryan ***@***.***> wrote:
Could you try signing in to your own team? You can select a team by clicking on where it says "None" to the right of "Team" and selecting a team.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Well "None" definatley won't work. Do you have any xcode development teams? if so, try selecting it. If not, then you can try clicking on "None", selecting "Add an account" and follow the appropriate instructions there. Apple will not let you build and run an xcode project without a development account (It doesn't have to be paid, free development accounts work just fine here 😄 ). |
I’ve already tried with two different paid developer accounts :) I tried none just in case.
…Sent from my iPhone
On Aug 13, 2021, at 7:21 PM, Ryan ***@***.***> wrote:
Well "None" definatley won't work. Do you have any xcode development teams? if so, try selecting it. If not, then you can try clicking on "None", selecting "Add an account" and follow the appropriate instructions there. Apple will not let you build and run an xcode project without a development account (It doesn't have to be paid, free development accounts work just fine here 😄 ).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Oh hmm, could you try Cmd + K to clean your build, restarting xcode, and/or cleaning your derived data? What is the error message when you use a developer account instead of none? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: