The Viro Developer Hub

Welcome to the Viro developer hub. You'll find comprehensive guides and sample code to help you start working with Viro as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started

Enable ARKit 1.5 (Beta) Features

Prerequisites

❗️

Xcode Beta and a Paid Apple Developer account is required to use ARKit 1.5 Features

Due to App Store restrictions, we can not release a Testbed application with ARKit 1.5 Features, as a result, to use ARKit 1.5 Features, you'll need to follow the instructions below to setup your device and Xcode Beta to build your application.

🚧

Have you already set up Xcode?

Run through all the steps in the Set up Xcode with ViroReact guide before running through this one.

1. Install Xcode Beta

Go to this link and install Xcode 9.3 Beta: https://developer.apple.com/xcode/downloads/

2. Install iOS 11.3 Beta on your Device

❗️

If you do this, you can no longer install to the device using previous versions of Xcode (non-Beta).

On your iOS device, navigate to this page: https://developer.apple.com/download/ and install the Configuration Profile for iOS 11.3 Beta

3. Update the Podfile

Open <your_project>/ios/Podfile and change the following line:

'

to:

'

Then navigate to <your_project>/ios/ in the Terminal and run:

l

4. Open the workspace in Xcode Beta

Open <your_project>/ios/<your_project>.xcworkspace in Xcode Beta and you should be set!

5. Distribution

ARKit 1.5 is not publicly available so apps built using ARKit 1.5/Xcode Beta can not be submitted to the App Store and released until Apple officially releases Xcode 9.3 and iOS 11.3 w/ ARKit 1.5.

If you need to release your application, simply undo step 3 above and open/rebuild your application using a non-beta version of Xcode. The Viro React components using ARKit 1.5 features will simply not appear, but no crashes should occur.

Updated less than a minute ago

Enable ARKit 1.5 (Beta) Features


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.