Recent updates
-
Named users: Add the Licensing Script Step
Updated onArticleIf your app is going to be deployed to named users, you need to add the script step that allows LCFM Native to license it correctly and collect your users names.
Warning! If you are deploying with a named user license pack, and you do not add this script step, you will not be able to deploy the app.
You can put this script step wherever seems best for your app. A natural place for it is on a login screen, but depending on how your app is structured you might want it to be somewhere else. As long as it is present and collecting user names, it is not important for the functioning of LCFM Native where it is put.
You can see how the script step is used in this very simple sample app.
Knowledge Base LCFM Native Guide Preparing to Deploy Android Apps
-
Syncing Checklist Steps 2 and 3. Open and Set Password and Permissions for Gateway
Updated onArticleLCFM Native has created a gateway solution for your app. This allows it to communicate with the original FileMaker solution, and pass data back and forth between your new Native app and your original solution. Both the Gateway, and your original solution, must be hosted on your FileMaker Server.
Knowledge Base LCFM Native Guide Regular Start - Adding Syncing
-
Edit Your Project to Add Syncing
Updated onArticleWe're now going to add syncing to an existing project, created via the "Fast Start" process. Alternatively, you can start a new project choosing "Regular Start" and go through the initial compile steps to reach the syncing screens. Before you start this section, ensure you have covered the "Preparing to Sync" chapter and have added the necessary fields to your solution, got a FileMaker Server to deploy to, turned on Accessibility and the Data API and checked your keyboard is a Qwerty one.
Knowledge Base LCFM Native Guide Regular Start - Adding Syncing
-
Deploying for iOS
Updated onArticleLet's get your compiled FileMaker solution onto iOS. Before you start this lesson - if you haven't already, you need to install Xcode and set up a development profile. If you're all ready with your Apple Identifiers, Certificates and Xcode, let's go!
Knowledge Base LCFM Native Guide Deploying to iOS
-
Fine Tuning - Setting the Override Values
Updated onArticleThe Override screen allows you to select what device layout you want, and whether you have any features that require a specific version of FileMaker. You can also change some functions from your FileMaker solution here.
Knowledge Base LCFM Native Guide Deploying Apps
-
Fine Tuning - Application Details
Updated onArticleTo make sure your app is fully ready to deploy you can customize many details from your Deployment Profile settings. To get to this area, click on "Edit Deployment Profile" at the top right of the deployment screen.
Knowledge Base LCFM Native Guide Deploying Apps
-
Running the tool
Updated onArticleFor your first run through, we recommend you try out the Fast Start option. This has a number of default options set, and does not require you to install any SDKs to deploy your app. You can deploy to Android or Mac using Fast Start, if you want to deploy to iOS you can add this later or go through a Regular Start. You will also not be setting up syncing on this run through, this can be added later.
Knowledge Base LCFM Native Guide Fast Start
-
Build for Mac
Updated onArticleSometimes it is useful to do a build of your app for Mac first, and during the development of your solution. It's the fastest way to see your functionality running as a native app, so you can test new features and changes quickly. If your solution doesn't work in a Mac app, its also unlikely to work on an iOS or Android device.
Knowledge Base LCFM Native Guide Fast Start
-
My app crashes when running specific script steps
Updated onArticleThe script step you are using may require device permissions or hardware. For example, Insert From Device Camera will require Camera hardware and permissions; the Location and LocationValues functions will require Location Services permissions. Ensure these are checked a appropriate in the relevant platform's Requirements pane of the Standalone Deployment screen.
Certain Android devices require permissions to be accepted by the user on a per-application basis prior to using the feature.
Knowledge Base LCFM Native Guide Troubleshooting
-
The deployed app is just a blank screen
Updated onArticleThis can happen when the initial app sync is either syncing a lot of data (in which case waiting should resolve the issue) or it is failing to connect. Ensure your server config settings are correct on the Deploy Server screen. In particular, localhost will work as the server address for macOS and iOS apps, but not for Android. Your FMS console should show you the actual IP address.
Knowledge Base LCFM Native Guide Troubleshooting