The last thing you need to set on the checklist screen is whether or not you verify your SSL connection.
In most live situations you would set this to Yes, as you will usually be using a secure (https) connection in order to protect the data you are transferring.
The FileMaker Server Data API uses SSL to secure the connection. If there is an issue with the SSL certificate installed on the server a verification error will occur.
In order to resolve SSL certificate verification errors follow the instructions in the Configuring Security for FileMaker 17 and 18 support article from FileMaker. We recommend not using a Let's Encrypt certificate because they are only valid for 90 days.
LCFM Native includes an option to not verify the SSL certificate when connecting to FileMaker Server. Using this option exposes the connection to man-in-the-middle attacks, however, there are there are times where it is a useful option. For example, if your project does not sync but extracts data from the solution which is installed on a server on the local network. The LCFM Native tool offers two places to set this property.
The first is on the Syncing Checklist at step 5. Set the `Verify FileMaker Server SSL Certificate` switch to `No`.
You can also set this option on the deployment profile editor. Uncheck the `Verify FileMaker Server SSL Certificate` checkbox.
You should now have worked through the Syncing Checklist screen, and you are ready to click "Next".
LCFM will now run through extracting your data and setting up your app profile. You can select your device orientations and permissions as for the Fast Start option, and you will arrive on the deployment screen. We'll look at building an actual Android app (rather than testing) in the next section.