8 Replies Latest reply on Jan 31, 2014 10:00 AM by philmodjunk

    Buggy, unstable, ephemeral issues in FM GO 13



      Buggy, unstable, ephemeral issues in FM GO 13


      FileMaker Go



      Operating system version

      iOS7, Windows 7

      Description of the issue

      I am posting a list of recently encountered issues in one issue report. They cannot be reliably reproduced as they seem to occur at random.

      Most have occurred in more than one completely different file. Some have been reported elsewhere in the forum. Some have not been reported to my knowledge.

      I am reporting them all in one report as there are overlapping similarities and when viewed as a whole, suggest that there are some basic stability, system refresh and window management issues in FM GO that need to be looked at by the engineers at Filemaker Inc.

      Steps to reproduce the problem

      Issue 1:
      FM GO files randomly open in a kind of "read only" mode. Fields do not retain edits. You may or may not get an error message that the record is locked because it is being edited in another window even though no other windows are open at the time.

      If you double click the Home button and flick the window for FM GO upwards to close the FM GO app, you can re-open the database and it will once again function correctly.

      This one has been reported in the FM GO forum several times but has not yet been officially acknowledged as an issue by TS personnel.

      In what may or may not be a different manifestation of this issue, I have one DB where I tap a field to perform a script. The script copies data into a set of global fields, then opens a new window with a layout that displays said global fields for editing. Periodically, this window opens with all fields blank. Closing the file down and restarting FM GO fixes the issue until the next random occurrence.

      Issue 2:
      Opening a new window can result in the current window spontaneously closing--perhaps due to layout corruption. This bug created the appearance that the DB was crashing because a script was closing the last window left open instead of the next to last window.

      After placing an unstored calculation field that used the WindowNames function to list all currently open windows on several layouts and putting some pauses in the script, I was able to determine that the script, which opened window 2, performed some tasks, opened window 3, performed more tasks then closed window 3, then Window 2 was closing Window 1, because window 2 was not open when it should have been. By replacing the layout that was current when Window 2 was opened with a new, rebuilt from scratch layout, the issue was resolved. Please note that each time I tested the script in FileMaker Pro, the script behaved as expected.

      Issue 3:
      I had a "use values from a field" value list that listed less than 100 text values in a value list. I then used a script that used Filtervalues and valuelist items to check to see if some text matched one of the values in this value list. When tested in FileMaker Pro, the script behaved normally. When I tested it in FM GO, the script failed to produce the expected result.

      My original conclusion here was that there was a bug with either this type of value list, a special calculated key used in field 2 to sort them in an arbitrary order or the valueListItems function when the script was performed in FM Go 13. But when I created a sample file for an Issue Report to post here, the sample file worked correctly in FM GO. I then defined a new value list with exactly the same features referencing exactly the same fields as the first and replaced all uses of the original value list with this new value list. The script then functioned correctly in FM GO.

      Issue 4:
      I've added a scrolling Popover feature to an upcoming release of the Known Bugs List Database as described here: http://forums.filemaker.com/posts/a568e2a481. I set up a script to open the popover automatically the first time that the user accesses the main iPhone layout. It sets a global field to 1 so that subsequent visits to the layout do not automatically open this popover. (Go To Object can open a Popover.)

      But while hosting the file from my Laptop's copy of FM 13 Advanced so I could Use FM Go to test my design, the popover would not open consistently even though I was being careful to keep the global field empty. When I tapped a control on this layout, the Popover would briefly flash and then disappear. (I have the field that fills the popover set up as a button to close it when tapped.)

      After a lot of wasted time replacing different design elements with new objects, I discovered that if I closed the file on my lap top and then re-opened it. It would function normally until I made some new design change to the layout at which point the problem recurs.

      Issue 5:
      Throughout dealing with all of the above, I periodically got an error message on the iPhone that a record could not be modified because it was being edited on the host computer. This occurred even though I made sure that the cursor was not in any field. Clicking a blank layout location to commit the record did not resolve the issue. I had to put the current layout in Layout mode to make the error message stop appearing.

      Configuration information

      The above issues have occurred in three different files. But many or similar issues have occurred in at least 2 of the three.
      Recovering files has not found any issues with the files--even when I later fixed the problem by removing and recreating a feature in the file.

      Using advanced recover options to rebuild all indexes in the file also has not produced any noticeable differences in behavior.

        • 1. Re: Buggy, unstable, ephemeral issues in FM GO 13


               Thank you for your post.

               I know these are sporadic issues, so here is what I have done.

               Issue 1 - Read Only Mode

               I have seen this appear with other customers on the forum, so I have sent the information to our Development and Testing departments for review.  They are aware this has occurred with a few users and not easily reproducible.

               Issue 2 - Open Window Closes Current Window

               This is the first instance I have heard of this, and I have been unable to replicate this issue.  Again, I have sent this information to our Development and Testing departments for review and guidance.

               Issue 3 - Value List Not Being Referenced

               There is an issue when only displaying the second field of a field value list where the value list is incomplete, but this sounds a little different.  After you replaced the original value list, it appears to be working.  I don't have enough information to act on this.  Do you have the original value list and file I can use?  Even after submitting, I might get the message that the value list was damaged.  If you can provide more information, I will submit it.

               Issue 4 - Popover Access first instance

               After reading this post and seeing the script would work after the host file was closed and reopened, my immediate thought was that the host file was opened with the global variable initially set to 1.  Then, the host set the global variable back to blank.  Closing and reopening would then set client access to the global variable as blank.  However, you then stated that any design changes to the layout would make the problem occur again.  With this said, I tried to replicate the issue, but I was unsuccessful.  Regardless, I sent your description to our Development and Testing departments for review.

               Issue 5 - iPhone cannot modify because edited on host computer.

               This sounds like it might be related to Issue #1, so I have attached it to that report.  That way, they can look for a connection that may help direct them to a possible issue, or they may split it off.


               In all cases, when I receive any type of feedback regarding these issues, I will let you know.

               FileMaker, Inc.

          • 2. Re: Buggy, unstable, ephemeral issues in FM GO 13

                 Like I said, these are not readily reproducible events. Simple single tests to try to reproduce won't do it. This doesn't even work for me. If I hadn't lost so many hours and had so many different issues on different files in a relatively short period of time, I wouldn't have bothered with reporting much of this.

                 2) please note that this only happened when a layout mysteriously "went bad". When I replaced the layout with a new version, that being the only change made, the script then worked. The layout was a blank layout with a single global text field--used with Insert from Device to capture data from a barcode scan.

                 3) I do not have the value list. But I do have the file. Hmmm, but since I keep it in Drop Box, I may be able to get an older copy. It's a long shot as I think that i created the value list, put it in place, then discovered the problem and replaced the file all in one session, but maybe I remember wrong...

                 4) I had the same thought, but I was very very careful to check that possibility. I even put the field on the layout where I could see it and checked the value from FM GO when the problem occurred. I have this file and this issue is somewhat reproducible. I can PM a download link for it to you and you can test this one in the actual file.

                 5) more on this one. Last night, in a brand new hours old file, I actually got this very frequently and I actually started getting this in both the computer and the iPhone at the same time even though there was only one record in the layout's table. I even had this error pop up on the iPhone when I had the host file in layout mode--no way that the record could be locked on the Host then! This file is the "Swipe gesture as trigger" file for which I uploaded a download link last night: https://dl.dropboxusercontent.com/u/78737945/SwipeablePictureList.fmp12

                 Another observation. Recently, including while working on the above experimental file, I would make a layout change on the host and save changes. In the past, such changes would almost instantly update the screen on the FM GO client. But I found that the layout was not updating. Only if I changed to a different layout and returned on the iPhone, did I see the layout update on the client.

                 A few other things that I will try:

                 I'll reboot the phone. I think I've tried that already, but it can't hurt...

                 I'm going to forgo my usual, "email file to computer/open file from drop box on iPhone methods of transferring files" and just transfer a brand new file I'm going to create shortly via Cable/iTunes. I'll be shocked if that avoids some of these issues, but it's another cheep fix that's easy to try out...

            • 3. Re: Buggy, unstable, ephemeral issues in FM GO 13


                   Thank you for the additional information.

                   On a side note, when I see that an issue is sporadic, I do spend quite a bit of time trying to duplicate the issue under several types of conditions, so I want to clear up any possibility that you interpret this as "Simple single tests".

                   If you have the actual file from #3 above, I'll definitely spend some time with this.  Same goes for #4.  You know how to reach me.

                   I did download the SwipeablePictureList database file.  I'll keep this open on my Mac and iPhone for an extended period of time.

                   FileMaker, Inc.

              • 4. Re: Buggy, unstable, ephemeral issues in FM GO 13


                     I'm able to get some type of replication with issue #5 by doing the following:

                     1. With the file hosted in FileMaker Pro 13.0v1, I access the file remotely with FileMaker Go 13.0v2.

                     2. If I go into Layout Mode in the hosted file, and I swipe once remotely, the fields are updated.

                     3. If I go to Browse Mode in the hosted file, I then get the message that the iOS device is modifying this record.

                     4. After tapping once on the layout in FileMaker Go, I am able to use the file in FileMaker Pro.  However, before doing anything in FileMaker Pro, when I swipe in FileMaker Go, the values do not change.  I get the same image displaying each time.

                     5. If I then tap on the layout in FileMaker Pro, then I am able to swipe to different records in FileMaker Go.

                     6. If I modify the Swipe script and add a Commit Records step at the end and return to Browse, I no longer get the iOS device modifying record message, but it still exhibits the swiping the same record continuously until the host clicks anywhere on the layout.

                     I have added this information in my original report to Development and Testing.

                     FileMaker, Inc.

                • 5. Re: Buggy, unstable, ephemeral issues in FM GO 13


                       There's an "OnRecordLoad" trigger that performs a script to select the middle slider panel and set the key fields used to initial values. That's what trips the lock error when you first access the layout, but what frustrates is that you cannot click or tap the layout background on either machine to commit records in order to prevent the lock error.

                  • 6. Re: Buggy, unstable, ephemeral issues in FM GO 13


                         Regarding issue #2 (current window sometimes closing), our Testing department is unable to replicate the issue.  Looking over your post, they suggest that you close window by name to avoid any possibility of the wrong window being closed.

                         If you encounter this issue again, write down exactly what you were doing prior to the closing of the window, as this may help point to a possible cause.

                         FileMaker, Inc.

                    • 7. Re: Buggy, unstable, ephemeral issues in FM GO 13


                           With Issue #5, the Tester says that adding a Commit Records script step to the end of the Initialize Slider script resolves the issue.  I have confirmed.

                           FileMaker, Inc.

                      • 8. Re: Buggy, unstable, ephemeral issues in FM GO 13

                             I had thought of the "by name" adjustment myself, but still reported this as an issue as such should not be needed. I fixed that one by replacing a layout so this is no longer a current issue.

                             Since starting this thread, I've uploaded a new version of the Known Bugs List database. This is the file that is exhibiting the "popover flash" issue that I reported, so you are welcome to pull down a copy and try it out with an FM  GO client to see if you get the same issue.

                             This leaves one remaining and fairly repeatable issue: An FM GO resident DB that fails to load global fields with data from the current record until I close and re-open the App. If you want to look at a copy, let me know and I'll PM you with a drop box link.