To begin, you’ll need to install Particle Auth through your Podfile; specifically, you’ll need (at a minimum) the following libraries:

• ParticleAuthCore
• ParticleMPCCore
• Thresh
• Optionally, ParticleWalletAPI for transaction construction.
• Optionally, ParticleWallerGUI to enable an embedded wallet interface.

Below is a snippet representing the installation of the aforementioned libraries.

pod `ParticleAuthCore`
pod 'ParticleMPCCore'
pod 'Thresh'

pod 'ParticleWalletAPI' # Optional
pod `ParticleWalletGUI` # Optional

Once installed, you’re ready to configure Particle Auth and initialize the SDK.

To do this, you’ll need three key values from the Particle dashboard: your project ID, client key, and app ID. These are used to authenticate your instance of Particle Auth and connect your project to the dashboard; these are required to properly initialize the SDK.

To retrieve these keys, follow the steps outlined below:

Access the Particle Dashboard

Sign up or Log in into the Particle dashboard

Create a new project or enter an existing project

Create a new iOS application, or skip this step if you already have one

Retrieve the project ID, client key, and application ID

For more information on the Particle dashboard, take a look at the dashboard quickstart.

With your project ID, client key, and app ID retrieved, you’ll need to add a file named ParticleNetwork-Info.plist to your project, then insert the aforementioned keys as is exemplified below.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PROJECT_UUID</key>
	<string>YOUR_PROJECT_UUID</string> <!-- Replace this with your project ID -->
	<key>PROJECT_CLIENT_KEY</key>
	<string>YOUR_PROJECT_CLIENT_KEY</string> <!-- Replace this with your client key -->
	<key>PROJECT_APP_UUID</key>
	<string>YOUR_PROJECT_APP_UUID</string> <!-- Replace this with your app ID -->
</dict>
</plist>

At this point, you’ve installed and configured Particle Auth; the only step remaining before the SDK can be used is initialization.

Particle Auth can be initialized by simply calling the initialize method on ParticleNetwork. This takes the following parameters:

• config, which takes:
  • chainInfo, representing the primary chain you intend to use (for example, .ethereum, .polygon).
  • devEnv, affecting the information logged within your environment (.debug, .production, or .staging).

The snippet below is an example of this.

// You can retrieve chainInfo from ChainInfo, the initialize works for the first time open.
// If you support more than one chain, you can use ParticleNetwork.setChainInfo to switch.
ParticleNetwork.initialize(config: .init(chainInfo: .ethereum, devEnv: .debug))

You’re ready to facilitate social login and interacting with the resulting accounts.

As shown below, you’ll need to call auth.connect to initiate social login, passing in the specific login type you’d like the user to use (.google, .twitter, .discord, etc.) alongside, if applicable, the type of account prompt used by the OAuth provider (.selectAccount, .consent, .none).

let userInfo = try await auth.connect(type: .google, socialLoginPrompt: .selectAccount)

// Additionally, you can implement custom authentication through JWT.
// Learn more: https://developers.particle.network/guides/configuration/auth/jwt
let userInfo = try await auth.connect(type: .jwt, account: "the JWT")