Recent updates
-
Failed to login to remote Database
Updated onArticleIf you have built a standalone app with syncing turned on, and you get an error something like "Failed to login to remote database - 802 - Unable to open file", it probably indicates your setup is not complete.
This can happen if you have not uploaded the gateway (interface) solution to FMS, or if any of the server settings (address, username or password) are incorrect. Check the lessons on setting up your gateway, uploading to the server, setting your fmrest permissions and make sure your Data API is turned on. Remember you must upload both the original FileMaker solution and the gateway (interface) solution to the server. Both must have passwords set, and they must match. It is also worth checking that the admin account for the original and interface gateway file matches. For example, if your account for the original file is using "myspecialadmin" as the username, and the interface file has defaulted to "admin" as the username, access will fail.
If all of this is set up correctly, check that your app is able to contact the server ie you are on a working network and no firewall is blocking access.
Knowledge Base / LCFM Native Guide / Troubleshooting
-
License definitions
Updated onArticleLCFM Native requires end user licensing. This article covers what we mean by each type of licensing and what constitutes fair use, with some examples.
You can read our complete EULA here.
Knowledge Base / LCFM Native Guide / Addendum: licensing terms
-
Android Standalone won't install on my device
Updated onArticleThis can happen because the device is set to allow installation only from apps downloaded from the Play Store. To change that, go to the device Settings and choose Allow installation of apps from unknown sources. See this lesson for step by step instructions.
Knowledge Base / LCFM Native Guide / Troubleshooting
-
My device isn't in the list of connected devices
Updated onArticleThis can happen for a number of reasons. In short, you have to make sure that Java 8 is installed, the Android SDK Tools are installed, and USB debugging is enabled in the Android device:
1. In the Android device, go to Developer Options. How to reach Developer Options depends on the device and/or Android version. Usually it is in Settings -> System -> Developer options. In the Developer Options, there is section named "Debugging". In this section, there is an option "USB Debugging - Debug mode when USB is connected". Make sure you turn this ON.
2. Make sure you have installed Android SDK Tools.
Notes:
(a) The "parent" folder containing the Android SDK should contain the following folders:
- build-tools
- platform-tools
- platforms
- tools
(b) The platform-tools folder includes a tool called "adb", which is responsible for connecting the Android device to the computer.
4. Now that you have installed the Android JDK and the Android SDK correctly, and you have enabled USB Debugging in the device, connect the device to your computer. You should see a dialog in the device asking you if you Trust this computer. Select Yes. Note that this dialog comes from the USB Debugging option, and it is not related to the Android Smart Lock. Thus the name of the computer will not appear in the list of trusted devices in the Smart Lock menu.
5. Now, if you navigate to the "Deployment" screen of LCFM Native, and the Android device is connected with USB to the computer, you should see the device identifier in the "Target Device" dropdown.
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
-
I'm getting timeout errors when running the tool
Updated onArticleIf you are running on a low specification Mac and/or you have a lot of other projects open while running LCFM Native, you may see errors like this:
Knowledge Base / LCFM Native Guide / Troubleshooting
-
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
-
Why Your App Isn't Quite What You Expected
Updated onArticleIt may sound obvious, but a mobile app isn't the same as a desktop app. If you've just taken your FileMaker solution to a mobile device for the first time, you may be surprised at the results. This article tries to cover some of the top issues you may encounter, and how you can resolve them.
Knowledge Base / LCFM Native Guide / Troubleshooting
-
Can't Find my Deploy Certificate for iOS
Updated onArticleIf you are getting a message something like "no deploy setting 'certificate' found" it might be because you created your certificate on a different machine from the one you are building on. Here is how to export your certificate and re-import it to the machine you need to use.
Knowledge Base / LCFM Native Guide / Troubleshooting
-
How to Sync a Single Customer Account from a Multi Account Database
Updated onArticleLCFM Native provides the ability to sync all your data from your FileMaker Server between your apps on desktop and mobile. But what if you only want to sync a small portion of data at a time? This lesson covers how you can sync individual tables, for example if you want to show a logged in customer only their own data and nobody else's.
Note: you will need to be using LCFM Native 1.5 Beta 4 or later for this lesson to work.
You can download the sample FileMaker Solution here.
Knowledge Base / LCFM Native Guide / Advanced