To rule out other possible causes, Use FMP 14 to recover a copy of this file to see if it might be damaged. Once in a while, a damaged file will function with no obvious problems. Then the OS is updated or the FM software is updated and the file starts misbehaving.
Plus the crashes themselves might have damaged the file.
And test the recovered copy even if the recover reports "no problems found". Some parts of the recovered file (such as indexes) are restored to "factor spec" without checking the current values for possible problems so sometimes a recovered file works even though nothing is reported as having been corrected.
All tested. As mentioned: I can't have Pro to crash with the very same solution. Only Go - and not every time. I tried yesterday morning to get a crash for more than a hour - nothing... It crashed again in the afternoon...
I know that it's hard to have it marked as bug..
Just because it doesn't crash in Pro but does crash in Go does not mean that the file is undamaged.
In fact, just because recover can't find the problem does not mean the file is undamaged.
You might try seeing if you can reproduce this in a brand new test file
seems to be solved. Another one that profits from a pause-scriptstep...
There must something be wrong in Go14
As I mentioned before: It's a couple of commit, pause/resume, refresh Window tasks and that dead chicken buried in your backyard that solves such kind of issues
Thank you for your posts.
Even though a pause script step appears to fix the issue, you shouldn't have to do that. Therefore, please send us a clone of the file so we can determine why the solution is crashing in FileMaker Go 14 but not FileMaker Go 13. Check your Inbox at the top of this page for instructions where to send the file.
not sure if this is related:
- tab into a text-field
- no access?!
Solution hosted with FMPA14.0.1 in 64-bit mode and connected with iPhone 5S and FMGo14
Your video doesn't show what are the exact steps taken to reproduce the crash. I still have your original file, so let me know the steps to take.
Hmmm, was testing some modifications using FMP 13 for development but testing in FM GO 14 as a client of FMP 13. This demo file uses OnLayoutSizeChange to trip a script that changes layouts when the device orientation changes. Both rotating the phone and manually changing layouts was crashing FM GO 14 but when testing in FM GO 13 there were no crashes.
The test was on layouts duplicated from two other layouts where the crashes were not happening.
But then, after opening closing files switching between FM GO 13 and FM GO 14, the crashes stopped...
So if this is typical of this issue, isolating it will be difficult as no layout change was made to make the crashing stop...
seems to be the same issue. Although, I did not switch from 13 to 14 (and vice versa). When a crash occurs, I was not able to force another crash... but a few hours later, it crashed again
As mentioned earlier, our solution runs fine now - after adding script-pauses in the layout-/navigation-scripts. Problem now: I have to fix some other methods (ie the orientation switch script (via script trigger) was missing the pause scriptstep) There might be others as well. It could be some special (but legal) characters in the base layout, it could be the number of popovers, hidden objects,
I prepared a demo file for the TS stuff - but it's still not ready for sending in
Yes. the key points that I am bringing up are that the crash was not consistently reproducible and in my case, this was while using FM GO 14 as a client of FileMaker Pro 13.--just in case others note the same pattern of behavior.
my problems are with a local file, no hosts involved
Should have done this a long time ago.
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
I have an file built fresh in 14 and it crashes sometimes on go 14 when running a navigation script. No crashes running in pro.
Did you get to the bottom of this ? Is there a bug? I haven't seen much on it if so. I have recovered the file and nothing was wrong.
I don't have a lot going on on the target layout. Just some hide object and conditional formatting on a button bar.