New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add build instructions #146

Merged
merged 3 commits into from Jan 9, 2019

Conversation

Projects
None yet
2 participants
@electroly
Copy link
Member

electroly commented Jan 4, 2019

I got it building and running in the simulator on Macincloud but I'm not sure I did it totally right.

  • Is there some way to do this without paying the $99 for a developer account? It complained about not having permission for the iCloud and push notifications capabilities.

  • Can I avoid changing the bundle identifier and team? It gave me all kinds of red errors until I did that.

  • I had to add my real iPhone to my developer account. Can this be done without owning an Apple device?

@electroly electroly requested a review from patch-e Jan 4, 2019

@patch-e

This comment has been minimized.

Copy link
Collaborator

patch-e commented Jan 5, 2019

You can do iOS development without a paid account now at this point. You still need an Apple developer account, but it does not need to be of the paid $99 type. You can develop and deploy to devices/simulators without issue but I do not think you would be able to test any development against stuff that needs entitlements, like push notifications. You do not need to own an iOS device to do development, you are just limited to simulators. If you do own a device, you do not need to manually add it to your developer account via that URL, the first time you try to deploy to it, Xcode will prompt you to add it to your developer account.

I have never actually done any of the above with a free account, I just know Apple made these improvements several years ago. You must have a paid developer account to distribute the app of course.

I believe the project in the repo has my team's identifier checked in. I should probably remove so that there is no team set by default in project settings. It doesn't really hurt anything having my team identifier there because no one but me can actually access it, but I guess it's kind of annoying to see an identifier that you can't actually use.

I wouldn't have thought you would need to change the bundle identifier at all. You aren't distributing the app, so I don't see why it's an issue. I don't recall ever having to change the bundle identifier when Squeegy's account still owned the app but I was doing most of the changes.

@electroly

This comment has been minimized.

Copy link
Member

electroly commented Jan 6, 2019

Ok I tried it again with a new Apple account without the paid membership. I got it to work and fixed the instructions. The key was that the error messages in red in the signing section of the project info don't matter.

@patch-e patch-e merged commit 44a9408 into master Jan 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment