You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use parse, head on over to the [releases][releases] page, and download the latest build.
41
-
And you're off!. Take a look at the public [documentation][docs] & [API][api] and start building.
42
-
43
-
Notice the API docs aren't totally up to date when it comes to latest Swift signature of the methods and more importantly regarding [Push Notifications](http://blog.parse.com/learn/engineering/the-dangerous-world-of-client-push/) which are **no longer supported by Parse server**, keep an eye on [its repo](https://github.com/ParsePlatform/parse-server)
44
-
45
-
### Other Installation Options
46
-
47
39
#### Swift Package Manager
48
40
49
41
1. Open Xcode > File > Add packages...
@@ -52,37 +44,17 @@ Notice the API docs aren't totally up to date when it comes to latest Swift sign
Take a look at the public [documentation][docs] & [API][api] and start building.
58
50
59
-
Add the following line to your Podfile:
60
-
```ruby
61
-
pod 'ParseCore'
62
-
```
63
-
64
-
Run `pod install`, and you should now have the latest parse release.
51
+
### Alternative Installation Options
65
52
66
-
If you wish to use the Facebook or Twitter utils or ParseUI,
67
-
you can now leverage Cocoapods 'subspecs'
53
+
#### Download Builds
68
54
69
-
```ruby
70
-
pod 'Parse/FacebookUtils'
71
-
pod 'Parse/TwitterUtils'
72
-
pod 'Parse/UI'
73
-
```
74
-
75
-
Note that in this case, the Parse framework will contain all headers and classes, so you just have to use:
76
-
77
-
```swift
78
-
importParseCore
79
-
```
80
-
81
-
```objc
82
-
@import ParseCore;
83
-
```
55
+
Dowload the compiled builds from the asset section in the [releases][releases] page.
84
56
85
-
#### Compiling for yourself
57
+
#### Compile Source
86
58
87
59
If you want to manually compile the SDK, clone it locally, and run the following commands in the root directory of the repository:
88
60
@@ -110,7 +82,7 @@ Compiled frameworks will be in multiple archives inside the `build/release` fold
110
82
-`ParseTwitterUtils-iOS.zip`
111
83
-`ParseUI.zip`
112
84
113
-
#### Using Parse as a sub-project
85
+
#### Add Sub-Project
114
86
115
87
You can also include parse as a subproject inside of your application if you'd prefer, although we do not recommend this, as it will increase your indexing time significantly. To do so, just drag and drop the Parse.xcodeproj file into your workspace. Note that unit tests will be unavailable if you use Parse like this, as OCMock will be unable to be found.
0 commit comments